[SERVER-18105] add ns to error log for bad ttl index key Created: 17/Apr/15  Updated: 26/May/15  Resolved: 14/May/15

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

Type: Improvement Priority: Trivial - P5
Reporter: Luke Alford Assignee: Ramon Fernandez Marina
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-17984 TTL Monitor doesn't modify query to m... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Github pull request #954



 Comments   
Comment by Ramon Fernandez Marina [ 14/May/15 ]

lalford, apologies for the delay in getting back to you. The work on SERVER-17984 makes the changes you suggested in your pull request unnecessary, but the good news is that SERVER-17984 adds very detailed error messages that I think should meet your needs: the error message went from

key for ttl index can only have 1 field

to

key for ttl index can only have 1 field, skipping ttl job for: { v: 1, key: { y: 1.0 }, name: "y_1", ns: "test.foo", expireAfterSeconds: 10.0 }

SERVER-17984 also adds this detailed information to the logs in a few other cases – see 3a8bcdfb if interested in more details.

Cheers,
Ramón.

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