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

TTL monitor reports "ERROR: error processing ttl for db" during initial sync

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Trivial - P5
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.2.1, 2.3.0
    • Component/s: Indexing, Replication
    • Labels:
      None
    • Operating System:
      ALL

      Description

      The TTL monitor runs during initial sync, and reports an error each time it fails to query the databases. The error message looks like:

      Thu Aug 30 11:08:42 [TTLMonitor] assertion 13436 not master or secondary; cannot currently read from this replSet member ns:config.system.indexes query:{ expireAfterSeconds: { $exists: true } }
      Thu Aug 30 11:08:42 [TTLMonitor] problem detected during query over config.system.indexes : { $err: "not master or secondary; cannot currently read from this replSet member", code: 13436 }
      Thu Aug 30 11:08:42 [TTLMonitor] ERROR: error processing ttl for db: config 10065 invalid parameter: expected an object ()

      The error is harmless, but the message is confusing. The TTL monitor should exit gracefully when running on a node that's not yet a primary or secondary.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: