[DOCS-11438] Docs for SERVER-33778: Remove change_stream_remove_shard.js Created: 13/Mar/18 Updated: 29/Oct/23 Resolved: 02/Jul/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.3, 3.6.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kay Kim (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 5 years, 32 weeks, 2 days ago | ||||||||||||||||
| Epic Link: | DOCS: 4.0 Server | ||||||||||||||||
| Story Points: | 0.25 | ||||||||||||||||
| Description |
DescriptionWe would like to change the documentation about removing a shard to say that we do not expect change streams to be able to survive and be completely resumable when a shard is removed. As described in the linked tickets here, there is a possibility that the change streams will not be able to contact the removed shard for long enough. Scope of changes (files that need work and how much)
Read product documentation (design, spec, scope docs)Read Changestream design docs to get an idea for any other pieces which might impact the additions to the docs. MVP (work and date?)Should take a few hours of writing effort between the three possible pages. |
| Comments |
| Comment by Githook User [ 02/Jul/18 ] |
|
Author: {'username': 'kay-kim', 'name': 'kay', 'email': 'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 02/Jul/18 ] |
|
Author: {'username': 'kay-kim', 'name': 'kay', 'email': 'kay.kim@10gen.com'}Message: |
| Comment by Charlie Swanson [ 14/Mar/18 ] |
|
That sounds useful to me, but I'm not actually familiar with what the workaround was. From what I was told (briefly), it involved isolating that shard via zoned sharding and waiting for all chunks to be migrated away from it, but I'm not sure what happens after that... |
| Comment by Jonathan DeStefano [ 13/Mar/18 ] |
|
charlie.swanson@mongodb.com schwerin Should we plan on documenting the zone sharding workaround (once identified) or just what's in the description above? |