[SERVER-75994] "Collection refresh failed": No chunks were found for the collection config.system.sessions Created: 12/Apr/23 Updated: 19/May/23 Resolved: 19/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ulan Kospanov | Assignee: | Chris Kelly |
| Resolution: | Done | Votes: | 0 |
| Labels: | Bug | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||
| Description |
|
We sharded our db, after that, there is problem with Logical Session Cache Refresh, because, in logs we can see such as lines:
What is already done: MongoDB version "5.0.4".
|
| Comments |
| Comment by Chris Kelly [ 19/May/23 ] | ||||
|
Thanks for adding the extra context! I'll go ahead and close this for now. | ||||
| Comment by Ulan Kospanov [ 17/May/23 ] | ||||
|
Hi, chris.kelly@mongodb.com , thank you, We resolved the issue. In my case, there are some steps: That's all. But, I recommend, do this steps only as a last resort, because MongoDB developers dont't recommend manually change config database) Good luck! | ||||
| Comment by Ulan Kospanov [ 17/May/23 ] | ||||
|
More new log messages after updating
| ||||
| Comment by Ulan Kospanov [ 17/May/23 ] | ||||
|
In the logs, there is new error messages.
| ||||
| Comment by Ulan Kospanov [ 05/May/23 ] | ||||
|
Hi, chris.kelly@mongodb.com , We are going to update our mongoDB to 6.0v. As soon as we finish, I'll write here according to the results) Thanks for reply) | ||||
| Comment by Chris Kelly [ 04/May/23 ] | ||||
|
We still need additional information to diagnose the problem. If this is still an issue for you, would you please provide the requested info above? | ||||
| Comment by Chris Kelly [ 12/Apr/23 ] | ||||
|
Some initial thoughts: It is not recommended to modify these collections. If they were modified manually, it would probably make sense that it impacts logical session cache refresh on mongos which are reaching out to it. You mention FCV is set to 5.0, did you recently upgrade from 4.4 around when this was sharded (before or after?) It's worth mentioning that there have been a number of minor version updates since 5.0.4, and you may find this issue doesn't exist on the newest patch release of 5.0 (currently 5.0.16), including
I would consider trying it out on the latest patch release to confirm the above (or any other fixed issues) aren't contributing to your problem. If you find the above hasn't resolved the issue:
| ||||
| Comment by Ulan Kospanov [ 12/Apr/23 ] | ||||
|
my email: kospanovulan@gmail.com |