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

CSHARP-2043: Added AssumeIndexesExist option to improve robustness of sharded GridFS #294

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Commits on Oct 6, 2017

  1. CSHARP-2043: Added SuppressEnsureIndexes option to GridFSBucketOption…

    …s. By default is false and has no impact on any part of the system. If set to true, then suppresses the call to EnsureIndexes which occurs during every GridFS upload call. Benefit of this suppression is that: 1) EnsureIndexes [effectively] does a count against the fs.files collection, which will a) add latency in a cluster with global shards, b) requires find permission which may not be deisrable in a write-only repository and most importantly c) cause entire cluster to become unavailable if any single shard is unavailable, even if data being saved is not housed in the unavailable shard. 2) Less importantly, EnsureIndexes includes a list index command which implies a higher privilege than is really needed. If developer is a) confident that GridFS subsystem is properly set up and b) wants to robustify sharded GridFS against one shard being down c) wants keep client permissions to a minimum
    John Gibbons committed Oct 6, 2017
    Configuration menu
    Copy the full SHA
    1c08080 View commit details
    Browse the repository at this point in the history

Commits on Oct 11, 2017

  1. CSHARP-2043: used better name for option: was SuppressEnsureIndexes, …

    …now AssumeIndexesExist
    John Gibbons committed Oct 11, 2017
    Configuration menu
    Copy the full SHA
    fc57655 View commit details
    Browse the repository at this point in the history