[SERVER-17118] moveChunk is slow with wired tiger Created: 29/Jan/15 Updated: 09/Jul/16 Resolved: 02/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, WiredTiger |
| Affects Version/s: | 3.0.0-rc7 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | Andy Schwerin |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Comparing to 2.6 and MMAPv1, moveChunk is slow with wired tiger.
|
| Comments |
| Comment by Siyuan Zhou [ 02/Feb/15 ] |
|
Further investigation shows that it's ConfigCoordinator who sends "fsync" commands to config servers, not SyncClusterConnection. SyncClusterConnection uses { "getlasterror": 1, "fsync" : 1 } instead, which doesn't flush files if journaling is enabled. ConfigCoordinator is used by both mongos and mongod for writing to config servers.
|