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

getLastError(2) hangs forever when "replSet error RS102 too stale to catch up"

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 1.7.0
    • Component/s: Replication
    • Labels:
      None
    • Environment:
      db version v1.7.1-pre-, pdfile version 4.5
      Thu Sep 9 15:50:22 git version: 10f750fa617e7499a89e9a140d89ddb4a7427ad6
    • ALL

      1. Set up replica set of 3 servers.
      2. Insert 2000 docs, each 1K size.
      3. Call getLastError(2), ie. wait for last write to reach at least two servers

      Problem: call never returns.

      However, works when only inserting 1000 docs.

      Servers log during problem:
      m30002| Thu Sep 9 17:22:45 [rs_sync] replSet error RS102 too stale to catch up, at least from primary: 127.0.0.1:30000
      m30002| Thu Sep 9 17:22:45 [rs_sync] replSet our last optime : Sep 9 17:22:43 4c895023:6
      m30002| Thu Sep 9 17:22:45 [rs_sync] replSet oldest at 127.0.0.1:30000 : Sep 9 17:22:43 4c895023:c2
      m30002| Thu Sep 9 17:22:45 [rs_sync] replSet See http://www.mongodb.org/display/DOCS/Resyncing+a+Very+Stale+Replica+Set+Member
      m30002| Thu Sep 9 17:22:45 [rs_sync] replSet error RS102 too stale to catch up
      m30000| Thu Sep 9 17:22:46 [initandlisten] connection accepted from 127.0.0.1:61974 #15
      m30001| Thu Sep 9 17:22:46 [rs_sync] replSet error RS102 too stale to catch up, at least from primary: 127.0.0.1:30000
      m30001| Thu Sep 9 17:22:46 [rs_sync] replSet our last optime : Sep 9 17:22:43 4c895023:6
      m30001| Thu Sep 9 17:22:46 [rs_sync] replSet oldest at 127.0.0.1:30000 : Sep 9 17:22:43 4c895023:c2
      m30001| Thu Sep 9 17:22:46 [rs_sync] replSet See http://www.mongodb.org/display/DOCS/Resyncing+a+Very+Stale+Replica+Set+Member
      m30001| Thu Sep 9 17:22:46 [rs_sync] replSet error RS102 too stale to catch up
      m30000| Thu Sep 9 17:24:45 [conn14] end connection 127.0.0.1:61973
      m30000| Thu Sep 9 17:24:46 [conn15] end connection 127.0.0.1:61974
      m30000| Thu Sep 9 17:24:46 [initandlisten] connection accepted from 127.0.0.1:62005 #16
      m30002| Thu Sep 9 17:24:46 [rs_sync] replSet error RS102 too stale to catch up, at least from primary: 127.0.0.1:30000
      m30002| Thu Sep 9 17:24:46 [rs_sync] replSet our last optime : Sep 9 17:22:43 4c895023:6
      m30002| Thu Sep 9 17:24:46 [rs_sync] replSet oldest at 127.0.0.1:30000 : Sep 9 17:22:43 4c895023:c2
      m30002| Thu Sep 9 17:24:46 [rs_sync] replSet See http://www.mongodb.org/display/DOCS/Resyncing+a+Very+Stale+Replica+Set+Member
      m30002| Thu Sep 9 17:24:46 [rs_sync] replSet error RS102 too stale to catch up
      m30000| Thu Sep 9 17:24:47 [initandlisten] connection accepted from 127.0.0.1:62006 #17
      m30001| Thu Sep 9 17:24:47 [rs_sync] replSet error RS102 too stale to catch up, at least from primary: 127.0.0.1:30000
      m30001| Thu Sep 9 17:24:47 [rs_sync] replSet our last optime : Sep 9 17:22:43 4c895023:6
      m30001| Thu Sep 9 17:24:47 [rs_sync] replSet oldest at 127.0.0.1:30000 : Sep 9 17:22:43 4c895023:c2
      m30001| Thu Sep 9 17:24:47 [rs_sync] replSet See http://www.mongodb.org/display/DOCS/Resyncing+a+Very+Stale+Replica+Set+Member
      m30001| Thu Sep 9 17:24:47 [rs_sync] replSet error RS102 too stale to catch up

            Assignee:
            kristina Kristina Chodorow (Inactive)
            Reporter:
            tonyh Tony Hannan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: