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

TEST: Retry synced-flush if ongoing ops on primary #30978

Merged
merged 6 commits into from
Jun 5, 2018

Commits on May 30, 2018

  1. TEST: Only synced-flush after global checkpoint synced

    When the last indexing operation is completed, we will fire a global
    checkpoint sync.  Since a global checkpoint sync request is a
    replication request, it will acquire an index shard permit on the
    primary when executing.  If this happens at the same time while we are
    issuing the synced-flush, the synced-flush request will fail as it
    thinks there are in-flight operations. We can avoid such situation by
    not issue the synced-flush until the global checkpoint on the primary is
    propagated to replicas.
    dnhatn committed May 30, 2018
    Configuration menu
    Copy the full SHA
    91b9e4d View commit details
    Browse the repository at this point in the history

Commits on May 31, 2018

  1. Configuration menu
    Copy the full SHA
    ee1a3c4 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    3597226 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    a0d69c8 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    c61f947 View commit details
    Browse the repository at this point in the history
  5. boaz suggestion

    dnhatn committed May 31, 2018
    Configuration menu
    Copy the full SHA
    93d959c View commit details
    Browse the repository at this point in the history