[SERVER-17151] Avoid fsync command in ConfigCoordinator Created: 02/Feb/15  Updated: 11/Jan/16  Resolved: 03/Mar/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.0.0-rc7
Fix Version/s: 3.1.0

Type: Bug Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Kaloian Manassiev
Resolution: Done Votes: 1
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-16638 remove fsync messages from config ser... Closed
Related
related to SERVER-17300 Balancer tries to create config.tags ... Closed
is related to SERVER-17118 moveChunk is slow with wired tiger Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Write command to config server will send fsync command first before executing write operations. This causes sharding operations (e.g. moveChunk) slow on wired tiger, because sharding operations write changelogs to config server and fsync is expensive on wired tiger.



 Comments   
Comment by Githook User [ 03/Mar/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-17151 ConfigCoordinator should not call fsync

This is expensive to do, especially with WiredTiger and is not a
deterministic check. This change replaces it with something cheaper, but
has the same outcome - validates that previous writes were successfully
journaled, which is an approximate predictor that subsequent writes have
high chance of succeeding.
Branch: master
https://github.com/mongodb/mongo/commit/41986e669a4ef32b38c433a2cfd0b70e872e6899

Generated at Thu Feb 08 03:43:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.