[jira] [Commented] (HDFS-3744) Decommissioned nodes are included in cluster after switch which is not expected

[ https://issues.apache.org/jira/browse/HDFS-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428200#comment-13428200 ] Raju commented on HDFS-3744: Oh Yesterday was my bad day @work :( Let me correct my second

[jira] [Commented] (HDFS-3744) Decommissioned nodes are included in cluster after switch which is not expected

[ https://issues.apache.org/jira/browse/HDFS-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428228#comment-13428228 ] Raju commented on HDFS-3744: I would like to add some scenarios which can be handled by

[jira] [Commented] (HDFS-3735) [ NNUI -- NNJspHelper.java ] Last three fields not considered for display data in sorting

[ https://issues.apache.org/jira/browse/HDFS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427400#comment-13427400 ] Raju commented on HDFS-3735: Hey Brahma, {code} case FIELD_FAILED_VOL: ret =

[jira] [Commented] (HDFS-3744) Decommissioned nodes are included in cluster after switch which is not expected

[ https://issues.apache.org/jira/browse/HDFS-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427404#comment-13427404 ] Raju commented on HDFS-3744: I have 2 suggestions to handle the same issue 1. Persist the

[jira] [Commented] (HDFS-3744) Decommissioned nodes are included in cluster after switch which is not expected

[ https://issues.apache.org/jira/browse/HDFS-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426775#comment-13426775 ] Raju commented on HDFS-3744: {quote}We have to execute this particular command on both the

[jira] [Commented] (HDFS-3747) In some TestCace used in maven. The balancer-Test failed because of TimeOut

[ https://issues.apache.org/jira/browse/HDFS-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426777#comment-13426777 ] Raju commented on HDFS-3747: I guess, in this problem we need to worry about why source node

[jira] [Commented] (HDFS-3734) TestFSEditLogLoader.testReplicationAdjusted() will hang if number of blocks are more than one

[ https://issues.apache.org/jira/browse/HDFS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426783#comment-13426783 ] Raju commented on HDFS-3734: This is because of improper calculation of the blocksThreshold if

[jira] [Commented] (HDFS-3731) 2.0 release upgrade must handle blocks being written from 1.0

[ https://issues.apache.org/jira/browse/HDFS-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13425849#comment-13425849 ] Raju commented on HDFS-3731: {quote}We should probably hook the finalize code to also rm -rf

[jira] [Commented] (HDFS-2956) calling fetchdt without a --renewer argument throws NPE

[ https://issues.apache.org/jira/browse/HDFS-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13425861#comment-13425861 ] Raju commented on HDFS-2956: Here we are defining the protocol message as {code} message

[jira] [Commented] (HDFS-3731) 2.0 release upgrade must handle blocks being written from 1.0

[ https://issues.apache.org/jira/browse/HDFS-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13425015#comment-13425015 ] Raju commented on HDFS-3731: In the upgrade process we usually rename the old folder to