[jira] [Commented] (HDFS-2136) 1073: Fault injection for StorageDirectory failures during read/write of FSImage/Edits files

[ https://issues.apache.org/jira/browse/HDFS-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061790#comment-13061790 ] Konstantin Boudnik commented on HDFS-2136: -- Todd, I find this {{They're also

[jira] [Commented] (HDFS-2138) fix aop.xml to refer to the right hadoop-common.version variable

[ https://issues.apache.org/jira/browse/HDFS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061798#comment-13061798 ] Konstantin Boudnik commented on HDFS-2138: -- Giri, patch doesn't apply to trunk.

[jira] [Commented] (HDFS-1073) Simpler model for Namenode's fs Image and edit Logs

[ https://issues.apache.org/jira/browse/HDFS-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061833#comment-13061833 ] Konstantin Shvachko commented on HDFS-1073: --- I would also like to ask for some

[jira] [Commented] (HDFS-2018) Move all journal stream management code into one place

[ https://issues.apache.org/jira/browse/HDFS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061844#comment-13061844 ] Ivan Kelly commented on HDFS-2018: -- Good comments, I have a 3 hour flight later so I'll

[jira] [Commented] (HDFS-2111) Add tests for ensuring that the DN will start with a few bad data directories (Part 1 of testing DiskChecker)

[ https://issues.apache.org/jira/browse/HDFS-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061933#comment-13061933 ] Hudson commented on HDFS-2111: -- Integrated in Hadoop-Hdfs-trunk #719 (See

[jira] [Commented] (HDFS-2131) Tests for HADOOP-7361

[ https://issues.apache.org/jira/browse/HDFS-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13061990#comment-13061990 ] Daryn Sharp commented on HDFS-2131: --- +1 good job! Tests for HADOOP-7361

[jira] [Updated] (HDFS-1981) When namenode goes down while checkpointing and if is started again subsequent Checkpointing is always failing

[ https://issues.apache.org/jira/browse/HDFS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HDFS-1981: - Status: Open (was: Patch Available) When namenode goes down while checkpointing

[jira] [Updated] (HDFS-1981) When namenode goes down while checkpointing and if is started again subsequent Checkpointing is always failing

[ https://issues.apache.org/jira/browse/HDFS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HDFS-1981: - Attachment: HDFS-1981-2.patch When namenode goes down while checkpointing and if

[jira] [Updated] (HDFS-1981) When namenode goes down while checkpointing and if is started again subsequent Checkpointing is always failing

[ https://issues.apache.org/jira/browse/HDFS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HDFS-1981: - Status: Patch Available (was: Open) When namenode goes down while checkpointing

[jira] [Commented] (HDFS-1981) When namenode goes down while checkpointing and if is started again subsequent Checkpointing is always failing

[ https://issues.apache.org/jira/browse/HDFS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062011#comment-13062011 ] ramkrishna.s.vasudevan commented on HDFS-1981: -- Hi Todd, Thanks for your

[jira] [Commented] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062023#comment-13062023 ] Daryn Sharp commented on HDFS-2034: --- +1 Great! Now we're protected whether or not

[jira] [Commented] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062024#comment-13062024 ] Hadoop QA commented on HDFS-2034: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-1977) Stop using StringUtils.stringifyException()

[ https://issues.apache.org/jira/browse/HDFS-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062068#comment-13062068 ] Bharath Mundlapudi commented on HDFS-1977: -- Todd, If you don't have any further

[jira] [Updated] (HDFS-2138) fix aop.xml to refer to the right hadoop-common.version variable

[ https://issues.apache.org/jira/browse/HDFS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated HDFS-2138: - Attachment: HDFS-2138-trunk.patch Thanks Cos I was fixing this on the MR-279 branch and

[jira] [Updated] (HDFS-2138) fix aop.xml to refer to the right hadoop-common.version variable

[ https://issues.apache.org/jira/browse/HDFS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated HDFS-2138: - Status: Patch Available (was: Open) fix aop.xml to refer to the right

[jira] [Updated] (HDFS-2138) fix aop.xml to refer to the right hadoop-common.version variable

[ https://issues.apache.org/jira/browse/HDFS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated HDFS-2138: - Status: Open (was: Patch Available) fix aop.xml to refer to the right

[jira] [Commented] (HDFS-2134) Move DecommissionManager to block management

[ https://issues.apache.org/jira/browse/HDFS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062110#comment-13062110 ] Tsz Wo (Nicholas), SZE commented on HDFS-2134: -- Todd, thanks for taking a

[jira] [Commented] (HDFS-2134) Move DecommissionManager to block management

[ https://issues.apache.org/jira/browse/HDFS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062109#comment-13062109 ] Tsz Wo (Nicholas), SZE commented on HDFS-2134: -- Todd, thanks for taking a

[jira] [Commented] (HDFS-2138) fix aop.xml to refer to the right hadoop-common.version variable

[ https://issues.apache.org/jira/browse/HDFS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062124#comment-13062124 ] Hadoop QA commented on HDFS-2138: - -1 overall. Here are the results of testing the latest

[jira] [Updated] (HDFS-2134) Move DecommissionManager to block management

[ https://issues.apache.org/jira/browse/HDFS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2134: - Attachment: h2134_20110708.patch h2134_20110708.patch: forgot to call

[jira] [Commented] (HDFS-2134) Move DecommissionManager to block management

[ https://issues.apache.org/jira/browse/HDFS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062129#comment-13062129 ] Hadoop QA commented on HDFS-2134: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-2134) Move DecommissionManager to block management

[ https://issues.apache.org/jira/browse/HDFS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062130#comment-13062130 ] Hadoop QA commented on HDFS-2134: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062133#comment-13062133 ] John George commented on HDFS-2034: --- I don't think the above tests fail because of this

[jira] [Commented] (HDFS-2134) Move DecommissionManager to block management

[ https://issues.apache.org/jira/browse/HDFS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062136#comment-13062136 ] Tsz Wo (Nicholas), SZE commented on HDFS-2134: -- bq. -1 @author. The patch

[jira] [Commented] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062145#comment-13062145 ] Tsz Wo (Nicholas), SZE commented on HDFS-2034: -- I agreed that the failed tests

[jira] [Updated] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2034: - Resolution: Fixed Fix Version/s: 0.23.0 Hadoop Flags: [Reviewed]

[jira] [Updated] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2034: - Component/s: hdfs client length in getBlockRange becomes -ve when reading only

[jira] [Commented] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062163#comment-13062163 ] Hudson commented on HDFS-2034: -- Integrated in Hadoop-Hdfs-trunk-Commit #776 (See

[jira] [Commented] (HDFS-2134) Move DecommissionManager to block management

[ https://issues.apache.org/jira/browse/HDFS-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062198#comment-13062198 ] Hadoop QA commented on HDFS-2134: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-2138) fix aop.xml to refer to the right hadoop-common.version variable

[ https://issues.apache.org/jira/browse/HDFS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062236#comment-13062236 ] Matt Foley commented on HDFS-2138: -- +1. lgtm. The failure of unit test

[jira] [Updated] (HDFS-2131) Tests for HADOOP-7361

[ https://issues.apache.org/jira/browse/HDFS-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-2131: -- Component/s: test Tests for HADOOP-7361 - Key:

[jira] [Commented] (HDFS-2131) Tests for HADOOP-7361

[ https://issues.apache.org/jira/browse/HDFS-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062246#comment-13062246 ] Uma Maheswara Rao G commented on HDFS-2131: --- Thanks Daryn! for taking a look.

[jira] [Commented] (HDFS-1971) HA: Send block report from datanode to both active and standby namenodes

[ https://issues.apache.org/jira/browse/HDFS-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062250#comment-13062250 ] Uma Maheswara Rao G commented on HDFS-1971: --- Hi Sanjay, Are you started working

[jira] [Commented] (HDFS-2071) Use of isConnected() in DataXceiver is invalid

[ https://issues.apache.org/jira/browse/HDFS-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062251#comment-13062251 ] Hudson commented on HDFS-2071: -- Integrated in Hadoop-Hdfs-22-branch #70 (See

[jira] [Commented] (HDFS-941) Datanode xceiver protocol should allow reuse of a connection

[ https://issues.apache.org/jira/browse/HDFS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062253#comment-13062253 ] Hudson commented on HDFS-941: - Integrated in Hadoop-Hdfs-22-branch #70 (See

[jira] [Commented] (HDFS-1952) FSEditLog.open() appears to succeed even if all EDITS directories fail

[ https://issues.apache.org/jira/browse/HDFS-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13062252#comment-13062252 ] Hudson commented on HDFS-1952: -- Integrated in Hadoop-Hdfs-22-branch #70 (See