Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-95086

Investigate proper queue size for resharding cloner

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability

      If I'm reading this correctly, the current queue size is numCursors*2 (I suspect that the original intent was number of results * 2). Given that a fetcher can get thousands of results in one go, the queue depth seems too low, and can potentially make the fetcher block unnecessarily instead of dumping everything to the queue and fetch the next results immediately.

            Assignee:
            Unassigned Unassigned
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: