[SERVER-66918] show collecions timeout , bacause lastSeenConfigServerOpTime term in mongos is bigger than config server term Created: 01/Jun/22  Updated: 20/Jul/22  Resolved: 20/Jul/22

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

Type: Bug Priority: Major - P3
Reporter: kaipeng li Assignee: Chris Kelly
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2022-06-01-18-54-49-851.png     PNG File image-2022-06-01-18-59-14-101.png     PNG File image-2022-06-01-19-00-19-278.png    
Operating System: ALL
Participants:

 Description   

mongo version: 4.0.3

how it happed?
we can hook file write for config server,  oplog will not be written to the file.

  1. config server can raise term for election
  2. shard server exchange information with config server  and raise lastSeenConfigServerOpTime in memory
  3. mongos  exchange information with shard and raise lastSeenConfigServerOpTime in memory
  4. restart config server and unregister hook ,  the term for config server lesser than lastSeenConfigServerOpTime


 Comments   
Comment by Chris Kelly [ 20/Jul/22 ]

We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Christopher

Comment by Chris Kelly [ 01/Jul/22 ]

Kaipeng,

Were you able to upgrade to 4.2? Is this something that is still persisting?

Christopher

Comment by Chris Kelly [ 06/Jun/22 ]

Hi kaipeng,

MongoDB 4.0.3 reached end of life in April 2022 and is no longer supported. Can you please upgrade to MongoDB v4.2+ and let us know if your problem persists?

Regards,
Christopher

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