-
Notifications
You must be signed in to change notification settings - Fork 684
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
GEODE-8394: Rewind the message Part on command failure #5424
Conversation
import org.apache.geode.test.junit.categories.ClientServerTest; | ||
|
||
@Category({ClientServerTest.class}) | ||
public class ClientServerCacheOperationDUnitTest implements Serializable { |
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.
The DUnitTest passes even without the fix in Part.java. I expect the DUnitTest will fail and reproduce GEODE-8394 without the fixes in Part.java. Maybe I am missing something.
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.
It was the test used to reproduce the original issue and test the fix. If you can see it has dependency on environment and shows flaky-ness...With adjusting the time; it is more of becoming a test for large object.
GEODE-8394: Rewind the message Part on failure Co-authored-by: anilkumar gingade <anil@anilg.local> (cherry picked from commit 83d1e28)
GEODE-8394: Rewind the message Part on failure Co-authored-by: anilkumar gingade <anil@anilg.local> (cherry picked from commit 83d1e28)
GEODE-8394: Rewind the message Part on failure Co-authored-by: anilkumar gingade <anil@anilg.local> (cherry picked from commit 83d1e28)
GEODE-8394: Rewind the message Part on failure Co-authored-by: anilkumar gingade <anil@anilg.local>
This change rewinds the message part on command failure. Without this during retry on failure, the message (Part) is sent from the place where it was previously failed, instead of starting from the beginning, causing it to transmit partial data.
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
[Y] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
[Y] Has your PR been rebased against the latest commit within the target branch (typically
develop
)?[Y] Is your initial contribution a single, squashed commit?
[Y] Does
gradlew build
run cleanly?[Y] Have you written or updated unit tests to verify your changes?
[NA] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.