[SERVER-20493] CSRS with protocolVersion:0 is very slow due to waiting for committed snapshot advancement messages via heartbeats Created: 18/Sep/15  Updated: 14/Apr/16  Resolved: 06/Oct/15

Status: Closed
Project: Core Server
Component/s: Replication, Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Eric Milkie
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-20494 Enable reading from CSRS secondaries Closed
is related to SERVER-20604 CSRS with protocol version 1 is slow ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: RPL A (10/09/15)
Participants:

 Comments   
Comment by Eric Milkie [ 06/Oct/15 ]

The default is now protocolVersion 1, so there should be no reason to run CSRS with pv0. If one must, one can use the workaround described above.

Comment by Spencer Brody (Inactive) [ 24/Sep/15 ]

We should revert this line once this has been fixed

Comment by Githook User [ 24/Sep/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-20494 SERVER-20493 Change CatalogManagerReplicaSet to use Nearest read preference
Branch: master
https://github.com/mongodb/mongo/commit/75f185e88b063ab13e0686552202de38618dec54

Comment by Spencer Brody (Inactive) [ 18/Sep/15 ]

As a workaround you can turn the heartbeat frequency for the config server replica set down (setting it to 100ms instead of the default 2 seconds seems to make the issue more or less go away)

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