[JBoss JIRA] (WFLY-6958) Use more intuitive values for consistent-hash-strategy
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-6958?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-6958:
-------------------------------
Fix Version/s: 11.0.0.CR2
(was: 11.0.0.CR1)
> Use more intuitive values for consistent-hash-strategy
> ------------------------------------------------------
>
> Key: WFLY-6958
> URL: https://issues.jboss.org/browse/WFLY-6958
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 11.0.0.CR2
>
>
> Currently consistent-hash-strategy can have on of 2 values: INTRA_CACHE vs INTER_CACHE.
> This was initially meant to describe a consistent hash that would be consistent within a cache vs across multiple caches within a cache container. In retrospect, these value are not very descriptive.
> Better would be consistent-hash-strategy="AGE|ADDRESS" or "AGE|NAME", where the strategy uses the cache view sorted by either age, or name/address.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFLY-7304) Compensations subsystem
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-7304?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-7304:
-------------------------------
Fix Version/s: 11.0.0.CR2
(was: 11.0.0.CR1)
> Compensations subsystem
> -----------------------
>
> Key: WFLY-7304
> URL: https://issues.jboss.org/browse/WFLY-7304
> Project: WildFly
> Issue Type: Task
> Components: Transactions
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Priority: Minor
> Fix For: 11.0.0.CR2
>
>
> Currently compensations bootstrap happens in the transactions subsystem. It registers deployment processor to scan the annotations and add the dependencies if necessary. This is not expensive and doesn't cause any issues other than adding the dependencies to the transactions subsystem. However, I'm currently finishing off the recovery implementation and more bootstrap logic will be needed. In addition, two more recovery modules will have to be registered: one for the participant (a new one) and one for the coordinator (from XTS). This will require to add XTS dependency too.
> The whole compensations bootstrapping will not need a lot of code. However, I'm thinking maybe it would be good to pull it out to the separate subsystem in order to maintain the separation of concerns.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFLY-7119) Introduce new web session granularity for consistent fine granularity replication
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-7119?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-7119:
-------------------------------
Fix Version/s: 11.0.0.CR2
(was: 11.0.0.CR1)
> Introduce new web session granularity for consistent fine granularity replication
> ---------------------------------------------------------------------------------
>
> Key: WFLY-7119
> URL: https://issues.jboss.org/browse/WFLY-7119
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 11.0.0.CR2
>
>
> Currently, ATTRIBUTE granularity sessions are vulnerable to partial stale reads, where some session attributes might have current data, and some are stale. For some use cases, this might be intolerable. For these use cases, we should introduce a new session granularity that tracks a version or checksum per attribute, that we can use to detect stale attribute cache entries.
> This new granularity would retain the performance benefits of ATTRIBUTE granularity replication while maintaining the attribute consistency guarantees of SESSION granularity replication.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months