issue-628 Changes to handle failure during clustered write-behind #3142
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chrisdennis
requested changes
May 8, 2023
...ava/org/ehcache/clustered/client/internal/loaderwriter/writebehind/ClusteredWriteBehind.java
Outdated
Show resolved
Hide resolved
...tion-test/src/test/java/org/ehcache/clustered/writebehind/BasicClusteredWriteBehindTest.java
Outdated
Show resolved
Hide resolved
...tion-test/src/test/java/org/ehcache/clustered/writebehind/BasicClusteredWriteBehindTest.java
Outdated
Show resolved
Hide resolved
...ed/integration-test/src/test/java/org/ehcache/clustered/writebehind/WriteBehindTestBase.java
Show resolved
Hide resolved
Hirensinh-Chavda
force-pushed
the
issue-628-clustered-fix
branch
3 times, most recently
from
96f745f to
2900ea8
Compare
bump versions Cleanup unused Jackson stuff Use platform-layout instead of platform-kit since platform 5.10.17 Jackson => Gson Switch to gradle nexus publish plugin platform version bump up issue-628 Changes to handle failure during clustered write-behind issue-628 Changed test case to use hamcrest libraries instead of junit issue-628 Minor formatting changes issue-628 Incorporated review comments by Chris issue-628 Incorporated review comments issue-628 Incorporated review comments issue-628 fix for current issue for handling failures of clustered write-behind issue-628 Reverting previous change issue-628 Another approach to handle the failures in clustered write behind issue-628 Reverting previous change issue-628 Increases test case timeout issue-628 Increased test case timeout issue-628 Increased test case timeout issue-628 Increased test case timeout issue-628 Increases test case timeout issue-628 Increases test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout issue-628 Changed test case timeout
Hirensinh-Chavda
force-pushed
the
issue-628-clustered-fix
branch
from
2900ea8 to
5b27a2a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue-628 Changes for handle failure during clustered write-behind
New EvenNumberLoaderWriter is added to tests to avoid touching any changes to existing clustered tests.