[SERVER-31396] Test that sharded changeStreams are resilient to individual node failure Created: 04/Oct/17  Updated: 30/Oct/23  Resolved: 23/May/18

Status: Closed
Project: Core Server
Component/s: Querying, Replication, Sharding
Affects Version/s: None
Fix Version/s: 4.0.0, 4.1.1

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Ian Boros
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0
Sprint: Query 2018-03-26, Query 2018-05-07, Query 2018-05-21, Query 2018-06-04
Participants:

 Comments   
Comment by Githook User [ 06/Jun/18 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}

Message: SERVER-31396 add tests for change streams being resilient to node failures in sharded cluster

(cherry picked from commit ee5a75a518806dbdd20460ef81db2b6a9717ece4)
Branch: v4.0
https://github.com/mongodb/mongo/commit/71fa3b81f9a3dbc682ccf087faf95e17780b21ff

Comment by Githook User [ 23/May/18 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}

Message: SERVER-31396 add tests for change streams being resilient to node failures in sharded cluster
Branch: master
https://github.com/mongodb/mongo/commit/ee5a75a518806dbdd20460ef81db2b6a9717ece4

Comment by Spencer Brody (Inactive) [ 04/Oct/17 ]

We're not actually sure that this works right now. If it doesn't, it will be up to the drivers to resume the stream by opening a new cursor.

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