[
https://issues.apache.org/jira/browse/HDFS-13544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HDFS-13544:
---------------------------------
Fix Version/s: (was: 2.9.2)
2.10.0
Updated the fix versions since the patch is not committed to branch-2.9.
> Improve logging for JournalNode in federated cluster
> ----------------------------------------------------
>
> Key: HDFS-13544
> URL: https://issues.apache.org/jira/browse/HDFS-13544
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: federation, hdfs
> Reporter: Hanisha Koneru
> Assignee: Hanisha Koneru
> Priority: Major
> Fix For: 2.10.0, 3.2.0, 3.1.1, 3.0.3
>
> Attachments: HDFS-13544.001.patch
>
>
> 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.
> {code:java}
> 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{code}
> We should add the NameserviceID or the JournalID to appropriate JournalNode
> logs to help with debugging.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
