[SERVER-33778] Remove change_stream_remove_shard.js Created: 09/Mar/18 Updated: 29/Oct/23 Resolved: 12/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.4, 3.7.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | Charlie Swanson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Backport Requested: |
v3.6
|
||||||||||||||||||||||||
| Sprint: | Query 2018-03-26 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||||||
| Comments |
| Comment by Githook User [ 14/Mar/18 ] |
|
Author: {'email': 'charlie.swanson@mongodb.com', 'name': 'Charlie Swanson', 'username': 'cswanson310'}Message: (cherry picked from commit 52fc77b88084386047093b7a61eb5b9173bcd974) |
| Comment by Githook User [ 14/Mar/18 ] |
|
Author: {'email': 'charlie.swanson@mongodb.com', 'name': 'Charlie Swanson', 'username': 'cswanson310'}Message: |
| Comment by Andy Schwerin [ 13/Mar/18 ] |
|
I doubt we've documented the workaround I described, no. |
| Comment by Githook User [ 13/Mar/18 ] |
|
Author: {'email': 'charlie.swanson@mongodb.com', 'name': 'Charlie Swanson', 'username': 'cswanson310'}Message: We do not expect change streams to continue to work after removing a (cherry picked from commit 97b09e04e8eac43d1d03923ccfe8fae56cef6be2) |
| Comment by Githook User [ 12/Mar/18 ] |
|
Author: {'email': 'charlie.swanson@mongodb.com', 'name': 'Charlie Swanson', 'username': 'cswanson310'}Message: We do not expect change streams to continue to work after removing a |
| Comment by Charlie Swanson [ 12/Mar/18 ] |
|
schwerin I'm marking this ticket as 'documentation changes needed', recommending we document that we do not expect change streams to be able to survive a shard removal. You mentioned during triage that there was a known workaround involving zoned sharding that would allow an admin to remove a shard without disruption? Do we have any documentation of such a workaround? |