hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-3726) QJM: if a logger misses an RPC, don't retry that logger until next segment
Date Thu, 26 Jul 2012 01:08:34 GMT
Todd Lipcon created HDFS-3726:
---------------------------------

             Summary: QJM: if a logger misses an RPC, don't retry that logger until next segment
                 Key: HDFS-3726
                 URL: https://issues.apache.org/jira/browse/HDFS-3726
             Project: Hadoop HDFS
          Issue Type: Sub-task
          Components: ha
    Affects Versions: QuorumJournalManager (HDFS-3077)
            Reporter: Todd Lipcon
            Assignee: Todd Lipcon


Currently, if a logger misses an RPC in the middle of a log segment, or misses the {{startLogSegment}}
RPC (eg it was down or network was disconnected during that time period), then it will throw
an exception on every subsequent {{journal()}} call in that segment, since it knows that it
missed some edits in the middle.

We should change this exception to a specific IOE subclass, and have the client side of QJM
detect the situation and stop sending IPCs until the next {{startLogSegment}} call.

This isn't critical for correctness but will help reduce log spew on both sides.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message