Re: Merging some trunk changes to 23

(Sorry, I missed hdfs-dev@ and my mail filters didn't help either). Sounds good. As per the email I sent out to general@ a couple of days ago, 0.23.1 is very close right now (there are a handful of perf bugs) after which we should be good for the merge. thanks, Arun On Jan 5, 2012, at 7:52 PM

[jira] [Created] (HDFS-2768) BackupNode stop can not close proxy connections because it is not a proxy instance.

BackupNode stop can not close proxy connections because it is not a proxy instance. --- Key: HDFS-2768 URL: https://issues.apache.org/jira/browse/HDFS-2768 Project: Hadoo

[jira] [Created] (HDFS-2767) HA: ConfiguredFailoverProxyProvider should support NameNodeProtocol

HA: ConfiguredFailoverProxyProvider should support NameNodeProtocol --- Key: HDFS-2767 URL: https://issues.apache.org/jira/browse/HDFS-2767 Project: Hadoop HDFS Issue Type: Sub-

[jira] [Resolved] (HDFS-1863) When all data directory volumes pulled out in DataNode, Its better to shutdown.

[ https://issues.apache.org/jira/browse/HDFS-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-1863. --- Resolution: Cannot Reproduce This doesn't seem to be a problem on 0.23 given Bharath's work (see comments abo

[jira] [Resolved] (HDFS-1724) Can not browse the Data Node blocks from NameNode UI if there is no Data Node hostname mappings in clients.

[ https://issues.apache.org/jira/browse/HDFS-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G resolved HDFS-1724. --- Resolution: Not A Problem Release Note: Clients should have host mappings configu

[jira] [Resolved] (HDFS-1587) JVM crash under writes: ExceptionMark destructor expects no pending exceptions

[ https://issues.apache.org/jira/browse/HDFS-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-1587. --- Resolution: Not A Problem This looked to be cause jars were updated during the runtime. The mail thread http:

[jira] [Resolved] (HDFS-973) DataNode.setDataNode() considered dangerous

[ https://issues.apache.org/jira/browse/HDFS-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-973. -- Resolution: Cannot Reproduce This does not seem to be a problem in 0.23+, reading the DataNode instantiation cod

Jenkins build became unstable: Hadoop-Hdfs-trunk #918

See

Hadoop-Hdfs-trunk - Build # 918 - Unstable

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/918/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 12179 lines...] [INFO] xmlOutput is false [INFO]

Hadoop-Hdfs-0.23-Build - Build # 131 - Unstable

See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/131/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 14068 lines...] [INFO] --- maven-source-plugin:2.1.2:

Jenkins build became unstable: Hadoop-Hdfs-0.23-Build #131

See

[jira] [Resolved] (HDFS-851) NPE in FSDir.getBlockInfo

[ https://issues.apache.org/jira/browse/HDFS-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-851. -- Resolution: Duplicate This was fixed by Bharat's recent work on moving all calls to the FileUtil.listFiles wrapp