Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
None
-
1
Description
From MB-44158
Looks like the time taken for gometa protocol before peer sync is taking 4 Seconds.
Check and Fix the same.
172.23.97.77 - Indexer - Leader
Leader received connection request from watcher 172.23.97.83
2021-05-15T16:55:28.703-07:00 [Info] LeaderServer.listenFollower(): Receive connection request from follower 172.23.97.83:39500
2021-05-15T16:55:28.703-07:00 [Info] LeaderSyncProxy.updateAcceptedEpochAfterQuroum()
Delay 1 - Seeing a couple of seconds delay here before the state machine in leader goes ahead.
2021-05-15T16:55:30.013-07:00 [Info] LeaderSyncProxy.notifyNewEpoch()
2021-05-15T16:55:30.029-07:00 [Info] LeaderSyncProxy.updateCurrentEpochAfterQuorum()
Delay 2 - Seeing another couple of seconds delay here before actually sending the data.
2021-05-15T16:55:32.891-07:00 [Info] LeaderSyncProxy.sendHeader lastCommittedTxid: 38654706347
2021-05-15T16:55:32.891-07:00 [Info] LeaderSyncProxy.sendEntriesInCommittedLog(): startTxid 0 endTxid 38654706346 observer first txid 38654706346
2021-05-15T16:55:32.891-07:00 [Info] snapshot info : name: MAIN last_seqnum: 2980 docCount : 221
2021-05-15T16:55:32.895-07:00 [Info] LeaderSyncProxy.sendTrailer lastCommittedTxid: 38654706347
2021-05-15T16:55:32.895-07:00 [Info] LeaderSyncProxy.declareNewLeaderAfterQuorum()
Attachments
Issue Links
- relates to
-
MB-44158 [System Test] Seeing errors "DDLServiceMgr: Failed to start metadata provider" several times in the test
-
- Closed
-