[SERVER-6911] TTL monitor reports "ERROR: error processing ttl for db" during initial sync Created: 31/Aug/12  Updated: 11/Jul/16  Resolved: 04/Sep/12

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Replication
Affects Version/s: 2.2.0
Fix Version/s: 2.2.1, 2.3.0

Type: Bug Priority: Trivial - P5
Reporter: Kevin Matulef Assignee: Kevin Matulef
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Operating System: ALL
Participants:

 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.



 Comments   
Comment by auto [ 27/Sep/12 ]

Author:

{u'date': u'2012-09-02T17:39:50-07:00', u'email': u'matulef@gmail.com', u'name': u'Kevin Matulef'}

Message: SERVER-6911 don't run TTL monitor if not in a readable state
Branch: v2.2
https://github.com/mongodb/mongo/commit/f87923d19fc3d5b65d4c1743b758dd6bc03b783d

Comment by auto [ 04/Sep/12 ]

Author:

{u'date': u'2012-09-02T17:39:50-07:00', u'email': u'matulef@gmail.com', u'name': u'Kevin Matulef'}

Message: SERVER-6911 don't run TTL monitor if not in a readable state
Branch: master
https://github.com/mongodb/mongo/commit/b35b8e0520d7bc5d1ac3bb96df16c311c685efe2

Generated at Thu Feb 08 03:13:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.