[jira] [Created] (HDFS-7874) Even-though rollback image is created, after restarting namenode with rollingUpgrade started option , createdRollbackImages is set to false.

J.Andreina created HDFS-7874: Summary: Even-though rollback image is created, after restarting namenode with rollingUpgrade started option , createdRollbackImages is set to false. Key: HDFS-7874 URL:

[jira] [Updated] (HDFS-7874) Even-though rollback image is created, after restarting namenode with rollingUpgrade started option , createdRollbackImages is set to false.

[ https://issues.apache.org/jira/browse/HDFS-7874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated HDFS-7874: - Attachment: HDFS-7874.1.patch While restarting namenode with rolling upgrade started option ,

[jira] [Updated] (HDFS-7869) Inconsistency in the return information while performing rolling upgrade

[ https://issues.apache.org/jira/browse/HDFS-7869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated HDFS-7869: - Attachment: HDFS-7869.2.patch Updated the patch with correction in one existing testcase. Inconsistency

[jira] [Updated] (HDFS-7869) Inconsistency in the return information while performing rolling upgrade

[ https://issues.apache.org/jira/browse/HDFS-7869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated HDFS-7869: - Attachment: HDFS-7869.1.patch Hi Vinayakumar B , Thanks for looking at this issue. I have attached a

[jira] [Commented] (HDFS-7867) Update action param from start to prepare in rolling upgrade code comment.

[ https://issues.apache.org/jira/browse/HDFS-7867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14344392#comment-14344392 ] J.Andreina commented on HDFS-7867: -- Failures are not related to this patch. Unit Testcases

[jira] [Updated] (HDFS-7867) Update action param from start to prepare in rolling upgrade code comment.

[ https://issues.apache.org/jira/browse/HDFS-7867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated HDFS-7867: - Attachment: HDFS-7867.1.patch Attached a patch with changes as per description. Please review the patch.

[jira] [Updated] (HDFS-7867) Update action param from start to prepare in rolling upgrade code comment.

[ https://issues.apache.org/jira/browse/HDFS-7867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated HDFS-7867: - Status: Patch Available (was: Open) Update action param from start to prepare in rolling upgrade code

[jira] [Created] (HDFS-7869) Inconsistency in the return information while performing rolling upgrade

J.Andreina created HDFS-7869: Summary: Inconsistency in the return information while performing rolling upgrade Key: HDFS-7869 URL: https://issues.apache.org/jira/browse/HDFS-7869 Project: Hadoop HDFS

[jira] [Created] (HDFS-7867) Update action param from start to prepare in rolling upgrade code comment.

J.Andreina created HDFS-7867: Summary: Update action param from start to prepare in rolling upgrade code comment. Key: HDFS-7867 URL: https://issues.apache.org/jira/browse/HDFS-7867 Project: Hadoop HDFS

[jira] [Commented] (HDFS-7869) Inconsistency in the return information while performing rolling upgrade

[ https://issues.apache.org/jira/browse/HDFS-7869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14343136#comment-14343136 ] J.Andreina commented on HDFS-7869: -- finalize Rolling upgrade can be consistent with

[jira] [Commented] (HDFS-7820) Client Write fails after rolling upgrade rollback with block_id already exist in finalized state

[ https://issues.apache.org/jira/browse/HDFS-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14342696#comment-14342696 ] J.Andreina commented on HDFS-7820: -- Hi Arpit Agarwal thanks for looking at this issue.

[jira] [Updated] (HDFS-7820) Client Write fails after rolling upgrade operation with block_id already exist in finalized state

[ https://issues.apache.org/jira/browse/HDFS-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated HDFS-7820: - Attachment: HDFS-7820.1.patch I have attached a patch where the block id value will be incremented by 10

[jira] [Commented] (HDFS-6753) When one the Disk is full and all the volumes configured are unhealthy , then Datanode is not considering it as failure and datanode process is not shutting down .

[ https://issues.apache.org/jira/browse/HDFS-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1433#comment-1433 ] J.Andreina commented on HDFS-6753: -- Findbugs and Test failures are not related to this

[jira] [Created] (HDFS-7842) Blocks missed while performing downgrade immediately after rolling back the cluster.

J.Andreina created HDFS-7842: Summary: Blocks missed while performing downgrade immediately after rolling back the cluster. Key: HDFS-7842 URL: https://issues.apache.org/jira/browse/HDFS-7842 Project:

[jira] [Commented] (HDFS-7842) Blocks missed while performing downgrade immediately after rolling back the cluster.

[ https://issues.apache.org/jira/browse/HDFS-7842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336302#comment-14336302 ] J.Andreina commented on HDFS-7842: -- Observation: === Logs after Step 5 {noformat}

[jira] [Created] (HDFS-7821) After rolling upgrade total files and directories displayed on UI does not match with actual value.

J.Andreina created HDFS-7821: Summary: After rolling upgrade total files and directories displayed on UI does not match with actual value. Key: HDFS-7821 URL: https://issues.apache.org/jira/browse/HDFS-7821

[jira] [Commented] (HDFS-7820) Client Write fails after rolling upgrade operation with block_id already exist in finalized state

[ https://issues.apache.org/jira/browse/HDFS-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333098#comment-14333098 ] J.Andreina commented on HDFS-7820: -- Please have a look at this , Iam trying to analyse

[jira] [Created] (HDFS-7820) Client Write fails after rolling upgrade operation with block_id already exist in finalized state

J.Andreina created HDFS-7820: Summary: Client Write fails after rolling upgrade operation with block_id already exist in finalized state Key: HDFS-7820 URL: https://issues.apache.org/jira/browse/HDFS-7820

[jira] [Updated] (HDFS-6753) When one the Disk is full and all the volumes configured are unhealthy , then Datanode is not considering it as failure and datanode process is not shutting down .

[ https://issues.apache.org/jira/browse/HDFS-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated HDFS-6753: - Attachment: HDFS-6753.1.patch Hi Srikanth , Thanks for checking this jira. I agree with

[jira] [Created] (HDFS-7730) knox-env.sh script should exit with proper error message , if JAVA is not set.

J.Andreina created HDFS-7730: Summary: knox-env.sh script should exit with proper error message , if JAVA is not set. Key: HDFS-7730 URL: https://issues.apache.org/jira/browse/HDFS-7730 Project: Hadoop

[jira] [Created] (HDFS-7447) Number of maximum Acl entries on a File/Folder should be made user configurable than hardcoding .

J.Andreina created HDFS-7447: Summary: Number of maximum Acl entries on a File/Folder should be made user configurable than hardcoding . Key: HDFS-7447 URL: https://issues.apache.org/jira/browse/HDFS-7447

[jira] [Created] (HDFS-6805) NPE is thrown at Namenode , for every block report sent from DN

J.Andreina created HDFS-6805: Summary: NPE is thrown at Namenode , for every block report sent from DN Key: HDFS-6805 URL: https://issues.apache.org/jira/browse/HDFS-6805 Project: Hadoop HDFS

[jira] [Created] (HDFS-6753) When one the Disk is full and all the volumes configured are unhealthy , then Datanode is not considering it as failure and datanode process is not shutting down .

J.Andreina created HDFS-6753: Summary: When one the Disk is full and all the volumes configured are unhealthy , then Datanode is not considering it as failure and datanode process is not shutting down . Key: HDFS-6753

[jira] [Created] (HDFS-6654) Setting Extended ACLs recursively for another user belonging to the same group is not working

J.Andreina created HDFS-6654: Summary: Setting Extended ACLs recursively for another user belonging to the same group is not working Key: HDFS-6654 URL: https://issues.apache.org/jira/browse/HDFS-6654

[jira] [Commented] (HDFS-6654) Setting Extended ACLs recursively for another user belonging to the same group is not working

[ https://issues.apache.org/jira/browse/HDFS-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14057293#comment-14057293 ] J.Andreina commented on HDFS-6654: -- I was confused by looking at

[jira] [Created] (HDFS-6630) Unable to fetch the block information by Browsing the file system on Namenode UI through IE9

J.Andreina created HDFS-6630: Summary: Unable to fetch the block information by Browsing the file system on Namenode UI through IE9 Key: HDFS-6630 URL: https://issues.apache.org/jira/browse/HDFS-6630

[jira] [Commented] (HDFS-2831) Description of dfs.namenode.name.dir should be changed

[ https://issues.apache.org/jira/browse/HDFS-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13966243#comment-13966243 ] J.Andreina commented on HDFS-2831: -- Thanks everyone for explaining. I got the difference.

[jira] [Commented] (HDFS-3377) While Balancing more than 10 Blocks are being moved from one DN even though the maximum number of blocks to be moved in an iterations is hard coded to 5

[ https://issues.apache.org/jira/browse/HDFS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289233#comment-13289233 ] J.Andreina commented on HDFS-3377: -- Thanks Ashish for clarifying the point that

[jira] [Created] (HDFS-3493) Replication is not happened for the block (which is recovered and in finalized) to the Datanode which has got the same block with old generation timestamp in RBW

J.Andreina created HDFS-3493: Summary: Replication is not happened for the block (which is recovered and in finalized) to the Datanode which has got the same block with old generation timestamp in RBW Key: HDFS-3493

[jira] [Commented] (HDFS-3457) Number of UnderReplicated blocks and Number of Files in the cluster, displayed in UI and Fsck report is different

[ https://issues.apache.org/jira/browse/HDFS-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284725#comment-13284725 ] J.Andreina commented on HDFS-3457: -- yes Ashish you are right, UI report displays the count

[jira] [Updated] (HDFS-3457) Number of UnderReplicated blocks displayed in UI and Fsck report is different

[ https://issues.apache.org/jira/browse/HDFS-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated HDFS-3457: - Description: Scenario: = Write an HDFS application with the following sequence of operations 1.

[jira] [Commented] (HDFS-3457) Number of UnderReplicated blocks displayed in UI and Fsck report is different

[ https://issues.apache.org/jira/browse/HDFS-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285374#comment-13285374 ] J.Andreina commented on HDFS-3457: -- Hi Aaron, Thanks for looking into this defect.

[jira] [Commented] (HDFS-3457) Number of UnderReplicated blocks and Number of Files in the cluster, displayed in UI and Fsck report is different

[ https://issues.apache.org/jira/browse/HDFS-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13283112#comment-13283112 ] J.Andreina commented on HDFS-3457: -- {quote} any chance you can figure out an easier way to

[jira] [Created] (HDFS-3457) Number of UnderReplicated blocks and Number of Files in the cluster, displayed in UI and Fsck report is different

J.Andreina created HDFS-3457: Summary: Number of UnderReplicated blocks and Number of Files in the cluster, displayed in UI and Fsck report is different Key: HDFS-3457 URL:

[jira] [Updated] (HDFS-3457) Number of UnderReplicated blocks and Number of Files in the cluster, displayed in UI and Fsck report is different

[ https://issues.apache.org/jira/browse/HDFS-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated HDFS-3457: - Attachment: UI screenshots.docx Attached the screenshot for UI report Number of

[jira] [Updated] (HDFS-3457) Number of UnderReplicated blocks and Number of Files in the cluster, displayed in UI and Fsck report is different

[ https://issues.apache.org/jira/browse/HDFS-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated HDFS-3457: - Attachment: (was: UI screenshots.docx) Number of UnderReplicated blocks and Number of Files in

[jira] [Created] (HDFS-3407) When dfs.datanode.directoryscan.interval is configured to 0 DN get shutdown but when configured to -1/ less than 0 values directory scan is disabled

J.Andreina created HDFS-3407: Summary: When dfs.datanode.directoryscan.interval is configured to 0 DN get shutdown but when configured to -1/ less than 0 values directory scan is disabled Key: HDFS-3407 URL:

[jira] [Commented] (HDFS-3360) SNN gets Shutdown if the conf dfs.namenode.checkpoint.dir and dfs.namenode.checkpoint.edits.dir is configured to more than 6 comma seperated values with 3-4 level in

[ https://issues.apache.org/jira/browse/HDFS-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13273090#comment-13273090 ] J.Andreina commented on HDFS-3360: -- @Uma, for the configurations

[jira] [Created] (HDFS-3377) While Balancing more than 10 Blocks are being moved from one DN even though the maximum number of blocks to be moved in an iterations is hard coded to 5

J.Andreina created HDFS-3377: Summary: While Balancing more than 10 Blocks are being moved from one DN even though the maximum number of blocks to be moved in an iterations is hard coded to 5 Key: HDFS-3377 URL:

[jira] [Created] (HDFS-3360) SNN gets Shutdown if the conf dfs.namenode.checkpoint.dir and dfs.namenode.checkpoint.edits.dir is configured to more than 6 comma seperated values

J.Andreina created HDFS-3360: Summary: SNN gets Shutdown if the conf dfs.namenode.checkpoint.dir and dfs.namenode.checkpoint.edits.dir is configured to more than 6 comma seperated values Key: HDFS-3360 URL:

[jira] [Updated] (HDFS-3360) SNN gets Shutdown if the conf dfs.namenode.checkpoint.dir and dfs.namenode.checkpoint.edits.dir is configured to more than 6 comma seperated values with 3-4 level in e

[ https://issues.apache.org/jira/browse/HDFS-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated HDFS-3360: - Summary: SNN gets Shutdown if the conf dfs.namenode.checkpoint.dir and dfs.namenode.checkpoint.edits.dir

[jira] [Commented] (HDFS-3360) SNN gets Shutdown if the conf dfs.namenode.checkpoint.dir and dfs.namenode.checkpoint.edits.dir is configured to more than 6 comma seperated values with 3-4 level in

[ https://issues.apache.org/jira/browse/HDFS-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13268141#comment-13268141 ] J.Andreina commented on HDFS-3360: -- Configured dfs.namenode.checkpoint.dir and

[jira] [Created] (HDFS-3356) When dfs.block.size is configured to 0 the block which is created in rbw is never deleted

J.Andreina created HDFS-3356: Summary: When dfs.block.size is configured to 0 the block which is created in rbw is never deleted Key: HDFS-3356 URL: https://issues.apache.org/jira/browse/HDFS-3356

[jira] [Created] (HDFS-3326) Even when dfs.support.append is set to true log message displays that the append is disabled

J.Andreina created HDFS-3326: Summary: Even when dfs.support.append is set to true log message displays that the append is disabled Key: HDFS-3326 URL: https://issues.apache.org/jira/browse/HDFS-3326

[jira] [Updated] (HDFS-3320) When dfs.namenode.safemode.min.datanodes is configured there is a mismatch in UI report

[ https://issues.apache.org/jira/browse/HDFS-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated HDFS-3320: - Target Version/s: 2.0.0, 3.0.0 (was: 0.23.1) Affects Version/s: (was: 0.23.1)

[jira] [Created] (HDFS-3320) When dfs.namenode.safemode.min.datanodes is configured there is a mismatch in UI report

J.Andreina created HDFS-3320: Summary: When dfs.namenode.safemode.min.datanodes is configured there is a mismatch in UI report Key: HDFS-3320 URL: https://issues.apache.org/jira/browse/HDFS-3320 Project:

[jira] [Created] (HDFS-3325) When configuring dfs.namenode.safemode.threshold-pct to a value greater or equal to 1 there is mismatch in the UI report

J.Andreina created HDFS-3325: Summary: When configuring dfs.namenode.safemode.threshold-pct to a value greater or equal to 1 there is mismatch in the UI report Key: HDFS-3325 URL:

<    1   2   3   4   5