[SERVER-28984] Improve Chunk Migration performance for clusters with high-latency Secondaries. Created: 26/Apr/17 Updated: 31/May/17 Resolved: 29/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.11 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | James Reitz | Assignee: | Kaloian Manassiev |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
| Comments |
| Comment by Kaloian Manassiev [ 29/Apr/17 ] |
|
Thanks for confirming your server version jimreitz. I am going to close this ticket as duplicate of Best regards, |
| Comment by James Reitz [ 29/Apr/17 ] |
|
@Kaloian Manassiev, I think you're right. We've been using 3.2.11. I didn't realize 3.4 had those changes. Thanks @Dan Pasette, I'll keep that in mind. Sometimes compression actually makes latency issues worse because it can add more latency to packet transmission. But it's highly dependent on the implementation. |
| Comment by Daniel Pasette (Inactive) [ 27/Apr/17 ] |
|
Another improvement made in v3.4 was compression of the wire protocol for intra-cluster data transfer ( |
| Comment by Kaloian Manassiev [ 27/Apr/17 ] |
|
Hi jimreitz, I believe what you are requesting duplicates Starting in version 3.4, if you are using the WiredTiger storage engine, the default write concern for migrations is w:1. The only time where majority write concern is used at the end of the migration. Historically, the default w:2 write concern was used as a way to achieve throttling and reduce the performance impact of migrations due to database level locking in MMAP V1. Best regards, |