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

Use selective receive to allow for vnode to be blocked #27

Merged
merged 3 commits into from
Apr 9, 2024

Commits on Mar 27, 2024

  1. Use selective receive to allow for vnode to be blocked

    Block and unblock a vnode when triggering a repair.  Otherwise their is a potential race condition:
    
    - aae_controller is triggered into repair mode, queueing all updates to be re-applied after rebuild complete
    - update is applied to leveled backend by vnode
    - snapshot is taken for rebuild (including update)
    - message is cast to aae_controller with update ... which will be queued and applied twice
    - update is queue
    martinsumner committed Mar 27, 2024
    Configuration menu
    Copy the full SHA
    43fab28 View commit details
    Browse the repository at this point in the history
  2. Handle message outside of selective receive

    If the selective receive times out - then need to handle the release message
    martinsumner committed Mar 27, 2024
    Configuration menu
    Copy the full SHA
    eeba0ad View commit details
    Browse the repository at this point in the history

Commits on Apr 4, 2024

  1. Configuration menu
    Copy the full SHA
    71a7c5e View commit details
    Browse the repository at this point in the history