[SERVER-24494] Parsing Linearizable Read command Created: 09/Jun/16  Updated: 05/Dec/16  Resolved: 18/Jul/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.3.10

Type: Task Priority: Major - P3
Reporter: Hari Devaraj Assignee: Hari Devaraj
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-9494 Docs for SERVER-24494: Parsing Linear... Closed
Related
related to DRIVERS-307 Support new readConcern level "linear... Closed
Backwards Compatibility: Minor Change
Sprint: Repl 16 (06/24/16), Repl 17 (07/15/16), Repl 18 (08/05/16)
Participants:

 Description   

First step in implementing linearizable reads: implement read concern level.

When a read is received with a read concern level “linearizable”, we must first check that the current node is master (available for writes). Nodes that are not currently in writable state shall return a NotMaster error. Linearizable reads are not permitted on Secondary nodes.

If an afterOpTime read concern option is also supplied, a parse error is returned. To limit project scope, afterOpTime read concern option will be incompatible with read concern level linearizable, for now.

Additionally, need to include unittests for parsing.



 Comments   
Comment by Hari Devaraj [ 18/Jul/16 ]

Need to allow for 'linearizable' read concern parsing.
Linearizable read concern returns a timeout error if noop replication takes longer than MaxTimeMS. Linearizable read concern returns a not master error if the command is run on a node that is not the primary.

Comment by Githook User [ 05/Jul/16 ]

Author:

{u'name': u'hari devaraj', u'email': u'hari.devaraj@10gen.com'}

Message: SERVER-24494 Implemented parsing for linearizable read concern
Branch: master
https://github.com/mongodb/mongo/commit/1aa84a66de0d2f83f9bc224d85278feff78b686a

Comment by Githook User [ 27/Jun/16 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: Revert "SERVER-24494 blacklist linearizable_read_concern_parsing.js from legacy suite"

This reverts commit cb0a631368529614bc210d1b3b22eae243b3dce6.
Branch: master
https://github.com/mongodb/mongo/commit/b0b1b300f0ab17c56a0c252371b76bbd9c44f291

Comment by Githook User [ 27/Jun/16 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: Revert "SERVER-24494 Implemented parsing for linearizable read concern."

This reverts commit cd5b90cfe19732cd576fc7b55e935fd4c74d187b.
Branch: master
https://github.com/mongodb/mongo/commit/15d3d1f9bd151a2cd21fc7bee0bffc61caaaeb1d

Comment by Githook User [ 24/Jun/16 ]

Author:

{u'name': u'hari devaraj', u'email': u'hari.devaraj@10gen.com'}

Message: SERVER-24494 blacklist linearizable_read_concern_parsing.js from legacy suite
Branch: master
https://github.com/mongodb/mongo/commit/cb0a631368529614bc210d1b3b22eae243b3dce6

Comment by Githook User [ 23/Jun/16 ]

Author:

{u'name': u'hari devaraj', u'email': u'hari.devaraj@10gen.com'}

Message: SERVER-24494 Implemented parsing for linearizable read concern.
Branch: master
https://github.com/mongodb/mongo/commit/cd5b90cfe19732cd576fc7b55e935fd4c74d187b

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