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.

Sign up for GitHub

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

Jump to bottom

Properly forward (or specifically don't) sys calls that result in read-only errors #4129

Merged
merged 1 commit into from
Mar 18, 2018
Merged

Properly forward (or specifically don't) sys calls that result in read-only errors #4129

merged 1 commit into from
Mar 18, 2018

Commits on Mar 14, 2018

  1. Properly forward (or specifically don't) sys calls that result in read 

    only errors.

Prior to this policy writes against a performance secondary would not
succeed because the read-only error was swallowed by handleError. In
addition to fixing this, it adds a similar function that explicitly
doesn't trigger forwarding. This is useful for things that are local to
the secondary such as raw operations and lease management.
    @jefferai
    jefferai committed Mar 14, 2018
    Configuration menu
    Copy the full SHA
    1a1a09a View commit details
    Browse the repository at this point in the history