[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:
Documented
documents SERVER-33778 Remove change_stream_remove_shard.js Closed
Related
related to DOCS-11715 Docs for SERVER-34818: changeStream o... Closed
Participants:
Days since reply: 5 years, 32 weeks, 2 days ago
Epic Link: DOCS: 4.0 Server
Story Points: 0.25

 Description   

Description

We 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)

  • removeShard cmd
  • Change Streams: Could maybe add a Behavior section to this page documenting this.
  • individual shell methods.
  • Using this ticket to also flesh out the what is and isn't resumable based on changestream at collection/db/deployment level.

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: DOCS-11438: shard removal and change stream cursor resumability
Branch: v3.6
https://github.com/mongodb/docs/commit/430c9a450417aa4528eb0794d7ffaebb302983bc

Comment by Githook User [ 02/Jul/18 ]

Author:

{'username': 'kay-kim', 'name': 'kay', 'email': 'kay.kim@10gen.com'}

Message: DOCS-11438: shard removal and change stream cursor resumability
Branch: master
https://github.com/mongodb/docs/commit/787a2adb396ee26570d83a23b619a983181cecd3

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?

Generated at Thu Feb 08 08:02:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.