[SERVER-53346] The best method resolving BUG SERVER-45119 of mongodb 4.2.3 for rhel7 x86_64 Created: 14/Dec/20 Updated: 06/Dec/22 Resolved: 14/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Jing Feng | Assignee: | Backlog - Triage Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | Bug | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS:RHEL7 x86_64 |
||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Triage
|
||||||||
| Participants: | |||||||||
| Description |
|
Hi! Resently,My mongodb server having 16 shardings which mongodb version is 4.2.3 for rhel7 x86_64 ,one of the 16 shardings throws error messages about mongodb 4.x verion BUG 1. Can I just refresh the chunk version data of the abnormal collection but refresh global mongod's chunk version data?
|