[OAK-6673] Improve cold standby logging

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.7.8, 1.8.0
• Component/s: segment-tar, tarmk-standby
• Labels: cold-standby
• Assignee: Andrei Dulceanu
• Reporter: Andrei Dulceanu
• Created: 15/Sep/17 08:00
• Updated: 04/Oct/19 17:52
• Resolved: 25/Sep/17 11:25

Description

With the new feature which allows chunking in blob transfer between server and client, there are various places in which more meaningful log messages could be used. For example, on the server, there's a tally of the no. of chunks sent/total no. of chunks, but this part is missing on the client, i.e. no. of chunks received/total no. of chunks.

Another case which would benefit from improved logging is when a big blob can't be sent fully from the server to the client in readTimeoutMs. The current exception message is a bit scarce in details (e.g. "Unable to load remote blob " + blobId + " at " + path + "#" + pName). This could also mean that the remote blob doesn't exist on the server in the first place. A better option would be to advise about increasing readTimeoutMs.

Finally, the same log level should be used everywhere, since currently DEBUG and INFO are interchangeably mixed.

/cc frm