[SERVER-54380] Error processing TTL index for "config.system.sessions Created: 08/Feb/21  Updated: 24/Mar/21  Resolved: 24/Mar/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.4.2
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Konstantin Krasnov Assignee: Edwin Zhou
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS Linux release 7.8.2003


Participants:

 Description   

Hi,

We regularly see message in the log:

 \{"t":{"$date":"2021-02-06T03:36:27.579+03:00"},"s":"E", "c":"QUERY", "id":4615603, "ctx":"TTLMonitor","msg":"Erroneous index key found with reference to non-existent record id. Consider dropping and then re-creating the index and then running the validate command on the collection.","attr":\{"namespace":"config.system.sessions","recordId":{"RecordId":1832764},"indexKeyData":[\{"key":{"":{"$date":"2020-12-11T11:29:14.893Z"}},"pattern":\{"lastUse":1}}],"indexKeyPattern":\{"lastUse":1}}}

config.system.sessions is a system collection. What can be done to fix the problem?



 Comments   
Comment by Edwin Zhou [ 24/Mar/21 ]

HI akostadinov,

We'd like to see if this issue persists when using 4.4.4 and running --repair. Since you're currently unable to do that, I will go ahead and close this ticket. Once you're able to perform the upgrade and you continue to observe this behavior, you may reopen this ticket and we will be happy to continue the investigation.

Best,
Edwin

Comment by Konstantin Krasnov [ 18/Mar/21 ]

Hi Edwin,

We can't stop the MongoDB.

Comment by Edwin Zhou [ 17/Mar/21 ]

Hi kkrasnov@gmail.com,

We're you able to resolve your issue by copying your $dbpath and trying mongod --repair using the latest version of MongoDB?

Best,
Edwin

Comment by Edwin Zhou [ 25/Feb/21 ]

Hi kkrasnov@gmail.com, and thank you for your patience while we investigate this issue.

This error suggests a mismatch between collection and index data. This appears to be an in-memory problem with the same root cause as SERVER-50971 with a slightly different symptom. Fortunately, there's no indication of persisted data corruption.

We recommend upgrading to MongoDB 4.4.4. If the problem continues, there may be a persisted index inconsistency. First, make a complete copy of the database's $dbpath directory to safeguard so that you can work off of the current $dbpath. Then, try mongod --repair using the latest version of MongoDB.

Best,
Edwin

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