Timeline for What happens exactly when a chunk gets migrated?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2018 at 17:47 | vote | accept | UnlimitedSlime | ||
| Jun 7, 2018 at 12:05 | comment | added | JJussi | Yes. Those are right choices, at your exam... :-) | |
| Jun 6, 2018 at 13:13 | comment | added | UnlimitedSlime | So, refered to this question: i.sstatic.net/97t3O.png Both 2nd and 3rd answers are correct, right? Since, as you said, shard0003 (original server) is serving all queries during the chunk migration. | |
| Jun 6, 2018 at 10:05 | comment | added | JJussi | During chunk migration (during copy of documents, config server update has not happened yet) original (chunk move source) server is serving all queries. After updating config server, the new server is serving all queries. If your find is still moving documents (cursor is open) during time when config server is updated, config server is updated, but that "cleaning" part waits until your cursor is closed. | |
| Jun 5, 2018 at 18:02 | comment | added | UnlimitedSlime | So, if I try to run collection.find() on a chunk that is getting migrated, the read operations get redirected automatically to the new shard, but it starts retrieving documents only AFTER the chunk has been migrated completely as a whole, right? In any case, as soon as you confirm the migration command, the config server updates immediately the shard location of where the chunk resides. | |
| Jun 5, 2018 at 13:34 | history | answered | JJussi | CC BY-SA 4.0 |
