-
Type: Bug
-
Resolution: Done
-
Priority: Trivial - P5
-
Affects Version/s: 2.2.0
-
Component/s: Index Maintenance, Replication
-
None
-
ALL
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.