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

cancel_sync is blocked when synchronisation is blocked by a memory alarm on the receiving node #1636

Closed
hairyhum opened this Issue Jul 5, 2018 · 0 comments

Comments

Projects
None yet
3 participants
@hairyhum
Copy link
Contributor

hairyhum commented Jul 5, 2018

To reproduce:

  1. Create a lazy mirrored queue
  2. Publish a lot of big messages (e.g. 4000 1MB messages)
  3. Restart a slave with watermark around 300M
  4. Start syncing
  5. See the queue stuck syncing
  6. Try to cancel sync

Affected version: master, 3.7

A syncing queue should somehow detect being stuck and at least support cancelation and policy changes. Maybe purge as well, to give user a way to exit the stuck state other than restarting nodes.

@hairyhum hairyhum added the bug label Jul 5, 2018

@hairyhum hairyhum added this to the 3.7.x milestone Jul 5, 2018

@michaelklishin michaelklishin modified the milestones: 3.7.x, 3.7.8 Jul 24, 2018

@michaelklishin michaelklishin changed the title cancel_sync does not work when synchronisation is blocked by the memory alarm on the receiving node. cancel_sync is blocked when synchronisation is blocked by a memory alarm on the receiving node Jul 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.