[SERVER-68328] Add ResumableChangeStreamError label to ReadConcernMajorityNotAvailableYet errors Created: 26/Jul/22  Updated: 29/Oct/23  Resolved: 25/Aug/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0, 5.0.16, 6.0.6

Type: Improvement Priority: Major - P3
Reporter: Shane Harvey Assignee: Vesselina Ratcheva (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-74001 Replace MaxTimeMSExpired with ReadCon... Closed
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0, v5.0, v4.4
Sprint: Repl 2022-08-22, Repl 2022-09-05
Participants:

 Description   

A user is reporting that their change stream is failing with a ReadConcernMajorityNotAvailableYet errors:

We have a service that listen on one collection, we use change stream to watch for a collection. We use mongodb 5.0 version. I don’t know why but we encountered this error:

pymongo.errors.OperationFailure: Executor error during getMore :: caused by :: Committed view disappeared while running operation, full error: {'ok': 0.0, 'errmsg': 'Executor error during getMore :: caused by :: Committed view disappeared while running operation', 'code': 134, 'codeName': 'ReadConcernMajorityNotAvailableYet', '$clusterTime': {'clusterTime': Timestamp(1635457764, 1), 'signature': {'hash': b'\xb9\xedq\xf5)\xa2\xd9s\xe6\xe8\xbc\x01\xfd\x1b\xb3\x1d[;#V', 'keyId': 7021065227265376259}}, 'operationTime': Timestamp(1635457764, 1)}
About database server we use:

storage engine: WiredTiger
Replication Factor: Three-node
Minor Version 6.0.0-20210924172808_1
Version 5.0
Read-only Nodes: 0

I would like to get help on knowing what could be the cause of the error and how to prevent it?

https://www.mongodb.com/community/forums/t/committed-view-disappeared-read-concern-majority-not-available-yet-code-134/130471

Should the server be attaching the ResumableChangeStreamError label to ReadConcernMajorityNotAvailableYet errors so that the driver can retry?



 Comments   
Comment by Githook User [ 20/Mar/23 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-68328 Add ResumableChangeStreamError label to ReadConcernMajorityNotAvailableYet errors

(cherry picked from commit 929980fe47f160e792fa20d5e6c36a858bb2143b)
Branch: v6.0
https://github.com/mongodb/mongo/commit/314d2de45084848f56b1f8e2af6e321b91bf6467

Comment by Githook User [ 01/Mar/23 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-68328 Add ResumableChangeStreamError label to ReadConcernMajorityNotAvailableYet errors

(cherry picked from commit 929980fe47f160e792fa20d5e6c36a858bb2143b)
Branch: v5.0
https://github.com/mongodb/mongo/commit/7dec35483f80ae27e3aa3a1338121aaa54f6de79

Comment by Alan Zheng [ 27/Feb/23 ]

Backport to v5.0 and v6.0 approved. v4.4 is EOL in <1 year and we recommend customers upgrade to newer versions soon. 

Comment by Britt Snyman [ 01/Sep/22 ]

Replacing the 6.1.0-rc1 fixVersion with 6.2.0-rc0 since these tickets had commits to master that were merged after we branched for v6.1.

Comment by Githook User [ 25/Aug/22 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-68328 Add ResumableChangeStreamError label to ReadConcernMajorityNotAvailableYet errors
Branch: master
https://github.com/mongodb/mongo/commit/929980fe47f160e792fa20d5e6c36a858bb2143b

Comment by Shane Harvey [ 01/Aug/22 ]

I'd say P3 maybe P2. For context the forum post has 1,400 views which indicates many users are likely facing the same issue. I would also be interesting to diagnose why the ReadConcernMajorityNotAvailableYet errors are happening to begin with (if they're unexpected).

Comment by Judah Schvimer [ 01/Aug/22 ]

shane.harvey@mongodb.com, what's the priority of this ticket?

Comment by Kyle Suarez [ 26/Jul/22 ]

This was initially sent to Query Execution, but I'm sending this over to the Replication queue for them to please take a look.

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