Skip to content

Conversation

@mahanteshwar-git
Copy link

This attempts to fix the flaky test case: testSnapshotChunks by serializing the calls to the handlers.

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mahanteshwar-git
Once this PR has been reviewed and has the lgtm label, please assign vorburger for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mahanteshwar-git mahanteshwar-git force-pushed the fix/1537_serialize_chunk_updates branch from 6de3a2e to fe9dd02 Compare November 12, 2025 07:40
@mahanteshwar-git mahanteshwar-git force-pushed the fix/1537_serialize_chunk_updates branch from fe9dd02 to 00ab589 Compare November 12, 2025 07:42
@mahanteshwar-git mahanteshwar-git changed the title 1537: serialize the chunk update (Work in progress) 1537: serialize the chunk update Nov 12, 2025
@mahanteshwar-git
Copy link
Author

@lburgazzoli , could you please review the code.

final Long bytes = maintenance.snapshot(NullOutputStream.INSTANCE).get();
final AtomicLong count = new AtomicLong();
final CountDownLatch latcht = new CountDownLatch(1);
ReentrantLock reentrantLock = new ReentrantLock(true);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how the re-entrant lock helps here ? the count si already an atomic value

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

3 participants