[SERVER-56115] Mongos not reflecting after upgrade to 4.4 from 4.2 Created: 15/Apr/21 Updated: 01/Jun/22 Resolved: 15/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Upgrade/Downgrade |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aayushi Mangal | Assignee: | Eric Sedor |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
We have 4 shards (3 replica set each) cluster was running on 4.2 We have upgraded our whole cluster as suggested by MongoDB document, to 4.4, with FCV remaining 4.2 Before upgrade, we checked active mongoses were 15, for 4.2 version Now after upgrade, we are seeing only 4 active mongoses, but when we checked manually that remaining mongos were working. Please help here to get the right count. |
| Comments |
| Comment by Eric Sedor [ 15/Jul/21 ] | ||
|
I'm going to close this ticket, but we are happy to reopen it if you are able to provide this additional information. Thanks, | ||
| Comment by Eric Sedor [ 01/Jul/21 ] | ||
|
Hi aayushi.mangal@visiblealpha.com, I wanted to check in to see if you could provide the above information to help us investigate further. Thanks, | ||
| Comment by Eric Sedor [ 21/May/21 ] | ||
|
Thank you for the information so far aayushi.mangal@visiblealpha.com. Are you still having this issue? If so, then for a mongos that is functional but not listing correctly in config.mongos, would you please archive (tar or zip) and upload to that link:
You can upload this to the same upload portal. | ||
| Comment by Aayushi Mangal [ 07/May/21 ] | ||
|
file uploaded | ||
| Comment by Eric Sedor [ 28/Apr/21 ] | ||
|
I've created a secure upload portal for you. Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. | ||
| Comment by Aayushi Mangal [ 28/Apr/21 ] | ||
|
Hi Eric, Yes, when we are verfying our mongos count after upgrade we are not getting count correct. And we verified manually, we have more number of mongos. And regarding requested information, i would like to add that in privately, is that feasible? | ||
| Comment by Eric Sedor [ 27/Apr/21 ] | ||
|
Hi aayushi.mangal@visiblealpha.com and thank you for your patience. We'd like to understand more about this issue. You mentioned that you checked manually that all mongoses are working. Are you saying that you can query the cluster correctly from all mongos routers and that the output of sh.status() is the only place this issue is visible? Can you please provide the contents of the config.mongos collection?
| ||
| Comment by Aayushi Mangal [ 21/Apr/21 ] | ||
|
Using sh.status() under active mongoses: active mongoses: | ||
| Comment by Kelsey Schubert [ 20/Apr/21 ] | ||
|
Could you clarify what the output is where you are only seeing 4 mongoses? Thanks, |