[HDFS-13544] Improve logging for JournalNode in federated cluster

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.10.0, 3.2.0, 3.1.1, 3.0.3
• Component/s: federation, hdfs
• Hadoop Flags: Reviewed
• Assignee: Hanisha Koneru
• Reporter: Hanisha Koneru
• Created: 10/May/18 19:59
• Updated: 29/Oct/18 09:52
• Resolved: 16/May/18 03:06

Description

In a federated cluster,when two namespaces utilize the same JournalSet, it is difficult to decode some of the log statements as to which Namespace it is logging for.
For example, the following two log statements do not tell us which Namespace the edit log belongs to.

INFO  server.Journal (Journal.java:prepareRecovery(773)) - Prepared recovery for segment 1: segmentState { startTxId: 1 endTxId: 10 isInProgress: true } lastWriterEpoch: 1 lastCommittedTxId: 10

INFO  server.Journal (Journal.java:acceptRecovery(826)) - Synchronizing log startTxId: 1 endTxId: 11 isInProgress: true: old segment startTxId: 1 endTxId: 10 isInProgress: true is not the right length

We should add the NameserviceID or the JournalID to appropriate JournalNode logs to help with debugging.