Skip to content
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

failed replication_test.py::test_replication_timeout_on_full_sync #4795

Open
BorysTheDev opened this issue Mar 18, 2025 · 4 comments
Open

failed replication_test.py::test_replication_timeout_on_full_sync #4795

BorysTheDev opened this issue Mar 18, 2025 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@BorysTheDev
Copy link
Contributor

https://github.com/dragonflydb/dragonfly/actions/runs/13892743446/job/38867312517

@BorysTheDev BorysTheDev added the bug Something isn't working label Mar 18, 2025
@BorysTheDev BorysTheDev self-assigned this Mar 18, 2025
@BorysTheDev
Copy link
Contributor Author

somehow we are stuck on the

  VLOG(1) << "Waiting for all full sync cut confirmations";
  sync_block->Wait();

next messages were done after terminating because sync_block->cancel() was called in err_handler

@BorysTheDev
Copy link
Contributor Author

Possible cause: to cancel replication we use Cancel error, but the streamer in this case can skip the callback WaitForInflightToComplete check

void JournalStreamer::Cancel() {
  ...
  if (!cntx_->IsError()) {
    WaitForInflightToComplete();
  }
}

@kostasrim
Copy link
Contributor

Possible cause: to cancel replication we use Cancel error, but the streamer in this case can skip the callback WaitForInflightToComplete check

void JournalStreamer::Cancel() {
  ...
  if (!cntx_->IsError()) {
    WaitForInflightToComplete();
  }
}

yes already aware of this. If you recall I was checking memory ordering around that synchronization primitive but IMO I think there is another issue.

@BorysTheDev
Copy link
Contributor Author

BorysTheDev commented Mar 18, 2025

yes already aware of this. If you recall I was checking memory ordering around that synchronization primitive but IMO I think there is another issue.

Agree. I just write about it to not forgetting in the future

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants