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

Mongos sharding filled with "update will be retried b/c sharding config info is stale" errors

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: 2.0.2
    • Fix Version/s: None
    • Component/s: Logging, Sharding
    • Labels:
      None
    • Environment:
      ubuntu 11.04
    • Operating System:
      ALL

      Description

      I believe this bug was suppose to be fixed in 2.0.2 and there are notes it is fixed in 2.3 (appears there is a fix (https://jira.mongodb.org/browse/SERVER-4387) but what do we do until then?

      mongos logs are full of stale config error message.
      we are running 2.0.2 on all machines, 4 application servers with mongos and a 6 machine shard/replica set with 3 shards and 2 member replica set with arbiter. Tried flush router command on all mongos instances but still no luck.

      Sat Apr 14 06:52:59 [conn120] update will be retried b/c sharding config info is stale,
      Sat Apr 14 06:52:59 [conn121] update will be retried b/c sharding config info is stale,
      Sat Apr 14 06:52:59 [conn121] update will be retried b/c sharding config info is stale,
      Sat Apr 14 06:52:59 [conn120] update will be retried b/c sharding config info is stale,
      Sat Apr 14 06:52:59 [conn120] update will be retried b/c sharding config info is stale,
      Sat Apr 14 06:52:59 [conn120] update will be retried b/c sharding config info is stale,
      Sat Apr 14 06:53:01 [conn121] update will be retried b/c sharding config info is stale,

        Attachments

          Activity

            People

            Assignee:
            backlog-server-sharding Backlog - Sharding Team
            Reporter:
            joep joe piscitella
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: