[SERVER-26378] Improve logging when Shard::runCommand on retries Created: 28/Sep/16  Updated: 29/Sep/16  Resolved: 28/Sep/16

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

Type: Improvement Priority: Major - P3
Reporter: Andy Schwerin Assignee: Andy Schwerin
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Sharding 2016-10-10
Participants:

 Description   

Shard::runCommand will retry an operation forever if no maxTime is provided, but it also only logs about the decision to retry at log level 2. This task is to log the first retry, every retry caused by a different upstream error code, and every 1000th retry with the same error code, so that retries can be distinguished from other hangs.



 Comments   
Comment by Andy Schwerin [ 28/Sep/16 ]

Turns out there is other logging that covers the interesting cases, here. Won't fix.

Generated at Thu Feb 08 04:11:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.