refactor getChunkManager() and sharding code to better handle parallel queries.

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.1.1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket has turned into a more general refactoring of the parallel cursor code, minimizing the use of getChunkManager(), but also includes the original issue:

      getChunkManager()'s failure mode is to throw masserts, which is incorrect as changes in sharding are not generally exception cases - this leads to very ugly logs and confusing codepaths. Also, there are various configurable levels of reloading for getChunkManager(), these should be clearer and encapsulated.

              Assignee:
              Greg Studer (Inactive)
              Reporter:
              Greg Studer (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: