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

better progress tracking for stale config errors in mongos reads/commands

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding
    • ALL

    Description

      For very expensive and long-running aggregation operations (query/m-r/agg) in very active clusters, the retry logic in parallel.cpp may need to be more aggressive. The default number of retries in this case may not be appropriate - explicit progress tracking is probably a better approach.

      See intermittent error:
      http://buildlogs.mongodb.org/MCI_linux-64/builds/289241/test/slow2_0/mr_during_migrate.js

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: