-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[10.x] WFLY-6969 Intermittent failures in Concurrent*WebFailoverTestCase following change to default consistent hash #9133
Conversation
Linux Build 33 outcome was FAILURE using a merge of 4360846 Failed tests
|
That test failure is unrelated to this change and will be addressed in a subsequent PR. |
Linux Build 35 outcome was FAILURE using a merge of 4360846 Failed tests
|
Linux Build 34 outcome was FAILURE using a merge of 4360846 Failed tests
|
Windows Build 34 outcome was FAILURE using a merge of 4360846 Failed tests
|
this.deploymentName = deploymentName; | ||
this.nonOwnerTask = () -> { | ||
// If the cache is non-transactional, we need to wait for that replication to finish, otherwise the read can be stale | ||
if (mode.isTransactional()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing negation.
Linux Build 36 outcome was FAILURE using a merge of 1d68631 Failed tests
|
OK - this should be good to go now. |
…lowing change to default consistent hash
defaults for existing schemas.
https://issues.jboss.org/browse/WFLY-6969
Also, Rollback 4.1 xsd introduced for WFLY-6926 fix.
Instead modify xsd defaults for existing schemas.