hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hanisha Koneru (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-13544) Improve logging for JournalNode in federated cluster
Date Fri, 11 May 2018 22:14:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-13544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472747#comment-16472747
] 

Hanisha Koneru commented on HDFS-13544:
---------------------------------------

Thanks [~elgoiri]. Will go ahead with journal id.

Here are some examples of new logs from JournalNode
{code:java}
INFO org.apache.hadoop.hdfs.qjournal.server.Journal: Updating lastPromisedEpoch from 0 to
1 for client /127.0.0.1 ; journal id: ns1

INFO org.apache.hadoop.hdfs.qjournal.server.Journal: getSegmentInfo(19): EditLogFile(file=/data/jn/ns1/current/edits_inprogress_0000000000000000019,first=0000000000000000019,last=0000000000000000019,inProgress=true,hasCorruptHeader=false)
-> startTxId: 19 endTxId: 19 isInProgress: true ; journal id: ns1

INFO org.apache.hadoop.hdfs.qjournal.server.Journal: Accepted recovery for segment 19: segmentState
{ startTxId: 19 endTxId: 19 isInProgress: true } acceptedInEpoch: 2 ; journal id: ns1{code}

> 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
>         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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message