[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:

 
{"t":\{"$date":"2023-08-25T04:43:36.621+00:00"},"s":"I",  "c":"-",        "id":4939300, "ctx":"monitoring-keys-for-HMAC","msg":"Failed to refresh key cache","attr":\{"error":"ReadConcernMajorityNotAvailableYet: Read concern majority reads are currently not possible.","nextWakeupMillis":200}}
{"t":\{"$date":"2023-08-25T04:43:36.633+00:00"},"s":"I",  "c":"CONTROL",  "id":20714,   "ctx":"LogicalSessionCacheRefresh","msg":"Failed to refresh session cache, will try again at the next refresh interval","attr":\{"error":"NotYetInitialized: Replication has not yet been configured"}}
{"t":\{"$date":"2023-08-25T04:43:36.634+00:00"},"s":"I",  "c":"CONTROL",  "id":20711,   "ctx":"LogicalSessionCacheReap","msg":"Failed to reap transaction table","attr":\{"error":"NotYetInitialized: Replication has not yet been configured"}}
{"t":\{"$date":"2023-08-25T04:43:36.821+00:00"},"s":"I",  "c":"-",        "id":4939300, "ctx":"monitoring-keys-for-HMAC","msg":"Failed to refresh key cache","attr":\{"error":"ReadConcernMajorityNotAvailableYet: Read concern majority reads are currently not possible.","nextWakeupMillis":400}}
{"t":\{"$date":"2023-08-25T04:43:37.221+00:00"},"s":"I",  "c":"-",        "id":4939300, "ctx":"monitoring-keys-for-HMAC","msg":"Failed to refresh key cache","attr":\{"error":"ReadConcernMajorityNotAvailableYet: Read concern majority reads are currently not possible.","nextWakeupMillis":600}}
{"t":\{"$date":"2023-08-25T04:43:37.743+00:00"},"s":"I",  "c":"REPL",     "id":21098,   "ctx":"BackgroundSync","msg":"Starting rollback due to fetcher error","attr":\{"error":"OplogStartMissing: the sync source's oplog and our oplog have diverged, going into rollback. our last optime fetched: { ts: Timestamp(1692933605, 1), t: 53 }. source's GTE: \{ ts: Timestamp(1692938125, 2), t: 54 }","lastCommittedOpTime":\{"ts":{"$timestamp":{"t":0,"i":0}},"t":-1}}}
{"t":\{"$date":"2023-08-25T04:43:37.744+00:00"},"s":"I",  "c":"NETWORK",  "id":22989,   "ctx":"conn10","msg":"Error sending response to client. Ending connection from remote","attr":\{"error":{"code":9001,"codeName":"SocketException","errmsg":"Broken pipe"},"remote":"10.0.3.66:60730","connectionId":10}}
{"t":\{"$date":"2023-08-25T04:43:37.744+00:00"},"s":"I",  "c":"-",        "id":4939300, "ctx":"monitoring-keys-for-HMAC","msg":"Failed to refresh key cache","attr":\{"error":"ReadConcernMajorityNotAvailableYet: Read concern majority reads are currently not possible.","nextWakeupMillis":800}}
{"t":\{"$date":"2023-08-25T04:43:37.744+00:00"},"s":"I",  "c":"NETWORK",  "id":22989,   "ctx":"conn7","msg":"Error sending response to client. Ending connection from remote","attr":\{"error":{"code":9001,"codeName":"SocketException","errmsg":"Broken pipe"},"remote":"127.0.0.1:50996","connectionId":7}}

 

 



 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!
Rhea

Comment by Uyen Vu [ 08/Sep/23 ]

Affect Version: 5.0.19

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