[SERVER-45413] Sessions collection is not set up & Failed to generate TTL index for config.system.sessions on all shards Created: 08/Jan/20  Updated: 13/Jan/20  Resolved: 09/Jan/20

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Sharding, TTL
Affects Version/s: 4.2.2
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: YUN-JHEN WANG Assignee: Carl Champain (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-44720 Send createIndexes, dropIndexes, and ... Closed
Participants:

 Description   

After upgrade to MongoDB version 4.2.2,

We got may message from config server as following:

2020-01-02T02:02:11.259Z I  SHARDING [conn4808] distributed lock 'config' acquired for 'createCollection', ts : 5e0d4f2300cb687a26c36207
2020-01-02T02:02:11.262Z I  SHARDING [conn4808] distributed lock 'config.system.sessions' acquired for 'createCollection', ts : 5e0d4f2300cb687a26c3620b
2020-01-02T02:02:11.265Z I  SHARDING [conn4808] distributed lock with ts: 5e0d4f2300cb687a26c3620b' unlocked.
2020-01-02T02:02:11.268Z I  SHARDING [conn4808] distributed lock with ts: 5e0d4f2300cb687a26c36207' unlocked.
2020-01-02T02:02:38.918Z I  SHARDING [conn4808] distributed lock 'config' acquired for 'createCollection', ts : 5e0d4f3e00cb687a26c36304
2020-01-02T02:02:38.921Z I  SHARDING [conn4808] distributed lock 'config.system.sessions' acquired for 'createCollection', ts : 5e0d4f3e00cb687a26c36308
2020-01-02T02:02:38.924Z I  SHARDING [conn4808] distributed lock with ts: 5e0d4f3e00cb687a26c36308' unlocked.
2020-01-02T02:02:38.927Z I  SHARDING [conn4808] distributed lock with ts: 5e0d4f3e00cb687a26c36304' unlocked.
2020-01-02T02:02:38.927Z I  CONTROL  [LogicalSessionCacheRefresh] Failed to generate TTL index for config.system.sessions on all shards, will try again on the next refresh interval
2020-01-02T02:02:38.927Z I  CONTROL  [LogicalSessionCacheRefresh] Sessions collection is not set up; waiting until next sessions refresh interval: request doesn't allow collection to be created implicitly
2020-01-02T02:04:42.584Z I  SHARDING [conn4808] distributed lock 'config' acquired for 'createCollection', ts : 5e0d4fba00cb687a26c366f0
2020-01-02T02:04:42.587Z I  SHARDING [conn4808] distributed lock 'config.system.sessions' acquired for 'createCollection', ts : 5e0d4fba00cb687a26c366f4
2020-01-02T02:04:42.590Z I  SHARDING [conn4808] distributed lock with ts: 5e0d4fba00cb687a26c366f4' unlocked.
2020-01-02T02:04:42.593Z I  SHARDING [conn4808] distributed lock with ts: 5e0d4fba00cb687a26c366f0' unlocked.
2020-01-02T02:07:11.259Z I  SHARDING [conn4808] distributed lock 'config' acquired for 'createCollection', ts : 5e0d504f00cb687a26c36bbf
2020-01-02T02:07:11.262Z I  SHARDING [conn4808] distributed lock 'config.system.sessions' acquired for 'createCollection', ts : 5e0d504f00cb687a26c36bc3

Please, could you explain the signification and how fix it?

Best regards,



 Comments   
Comment by YUN-JHEN WANG [ 13/Jan/20 ]

Hi Carl,

Thanks a lot !

 

Best regards,

Comment by Carl Champain (Inactive) [ 09/Jan/20 ]

Hi phiphiphina@gmail.com,

Thanks for the report.
This issue was actually worked on in SERVER-44720. These log lines appear because createIndexes is being sent to shards that don't own chunks for the sessions collection. Luckily, It doesn't indicate anything wrong on your side and the extra log noise should go away in v4.4. I'm going to close this ticket as a duplicate, but you can watch SERVER-44720 for updates.

Kind regards,
Carl

 

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