[SERVER-30198] Support resumeAfter option to $changeNotification in sharded clusters Created: 17/Jul/17  Updated: 02/Oct/17  Resolved: 02/Oct/17

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Charlie Swanson
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-29504 Support resumeAfter behavior for shar... Closed
Duplicate
duplicates SERVER-29141 Add sharding support for merging chan... Closed
Sprint: Repl 2017-09-11, Repl 2017-10-02
Participants:

 Comments   
Comment by Charlie Swanson [ 02/Oct/17 ]

This work was done as part of SERVER-29141. There was minor re-ordering and pipeline-splitting work to be done, but it was tackled as part of that ticket.

Comment by Spencer Brody (Inactive) [ 18/Jul/17 ]

SERVER-29504 does not include any changes to mongos, it is specifically for the mongod changes. This ticket is the placeholder for any additional work that needs to be done in the mongos layer to make resumability work.

Comment by Charlie Swanson [ 18/Jul/17 ]

Do we expect there to be further changes? SERVER-29504 already includes code to ensure the part of the pipeline that makes sure we see the resume token is run during the merge phase - which will eventually happen on mongos. I'm not sure there's any additional work?

Comment by Spencer Brody (Inactive) [ 17/Jul/17 ]

This ticket is for the mongos changes to make resumability fully work in a sharded cluster. The mongod-only changes related to supporting the sharded resumability behavior is covered in SERVER-29504.

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