[SERVER-80884] ReadConcernMajorityNotAvailableYet: Read concern majority reads are currently not possible Created: 08/Sep/23 Updated: 22/Sep/23 Resolved: 22/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Uyen Vu | Assignee: | Alison Rhea Thorne |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Hi,
We are trying restore mongodb in EKS from snapshot of EBS and we have deployed then error log is as below:
|
| Comments |
| Comment by Alison Rhea Thorne [ 22/Sep/23 ] |
|
Hello uyenvt85@gmail.com, Thank you for your report. Looking at the log that you’ve provided it appears that the primary trouble that you are running into is due to the replica set not being configured nor initialized. Below, I’ve provided some documentation that may assist with resolving this: From what I am able to tell based on the log provided, it is unlikely that you are running into a core server bug. We recommend reaching out to the mongodb community forums, as it’s quite a strong resource for acquiring assistance with resolving matters such as what you’ve described. Should it be determined that you are encountering a server bug that should be filed, then we can further assist with triaging the matter. Thank you! |
| Comment by Uyen Vu [ 08/Sep/23 ] |
|
Affect Version: 5.0.19 |