hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4941) TestNNThroughputBenchmark fails because of interrupted ReplicationMonitor
Date Fri, 28 Jun 2013 15:22:20 GMT

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

Kihwal Lee commented on HDFS-4941:
----------------------------------

Sorry for the delay in fixing HDFS-4887. I've posted a new patch.
                
> TestNNThroughputBenchmark fails because of interrupted ReplicationMonitor
> -------------------------------------------------------------------------
>
>                 Key: HDFS-4941
>                 URL: https://issues.apache.org/jira/browse/HDFS-4941
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode, test
>    Affects Versions: 3.0.0
>            Reporter: Andrew Wang
>
> This has been breaking trunk test runs pretty consistently.
> HDFS-4840 introduced some new code to BlockManager that terminates the NN if the ReplicationMonitor
thread is interrupted unexpectedly:
> {code}
>           if (!namesystem.isRunning()) {
>             LOG.info("Stopping ReplicationMonitor.");
>             if (!(t instanceof InterruptedException)) {
>               LOG.info("ReplicationMonitor received an exception"
>                   + " while shutting down.", t);
>             }
>             break;
>           }
>           LOG.fatal("ReplicationMonitor thread received Runtime exception. ", t);
>           terminate(1, t);
> {code}
> Unfortunately, NNThroughputBenchmark interrupts in ReplicationStats#generateInputs:
> {code}
>       // stop replication monitor
>       BlockManagerTestUtil.getReplicationThread(namesystem.getBlockManager())
>           .interrupt();
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message