You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2013/06/28 01:44:20 UTC

[jira] [Created] (HDFS-4941) TestNNThroughputBenchmark fails because of interrupted ReplicationMonitor

Andrew Wang created HDFS-4941:
---------------------------------

             Summary: 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