[jira] [Reopened] (HDFS-10673) Optimize FSPermissionChecker's internal path usage

[ https://issues.apache.org/jira/browse/HDFS-10673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang reopened HDFS-10673: -- Sorry to reopen the JIRA. I want to test the branch-2.7 patch on Jenkins. > Optimize FSPermissionChecker's

[jira] [Updated] (HDFS-10673) Optimize FSPermissionChecker's internal path usage

[ https://issues.apache.org/jira/browse/HDFS-10673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated HDFS-10673: - Attachment: HDFS-10673-branch-2.7.00.patch > Optimize FSPermissionChecker's internal path usage >

[jira] [Commented] (HDFS-10378) FSDirAttrOp#setOwner throws ACE with wrong message

[ https://issues.apache.org/jira/browse/HDFS-10378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485170#comment-15485170 ] Hadoop QA commented on HDFS-10378: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (HDFS-9019) Adding informative message to sticky bit permission denied exception

[ https://issues.apache.org/jira/browse/HDFS-9019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485171#comment-15485171 ] Zhe Zhang commented on HDFS-9019: - Thanks for the work [~xyao]. Since affect version includes 2.7 (and I

[jira] [Updated] (HDFS-9019) Adding informative message to sticky bit permission denied exception

[ https://issues.apache.org/jira/browse/HDFS-9019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated HDFS-9019: Fix Version/s: 2.7.4 > Adding informative message to sticky bit permission denied exception >

[jira] [Updated] (HDFS-10378) FSDirAttrOp#setOwner throws ACE with wrong message

[ https://issues.apache.org/jira/browse/HDFS-10378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Zhuge updated HDFS-10378: -- Summary: FSDirAttrOp#setOwner throws ACE with wrong message (was: FSDirAttrOp#setOwner throws

[jira] [Commented] (HDFS-10276) HDFS should not expose path info that user has no permission to see.

[ https://issues.apache.org/jira/browse/HDFS-10276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485143#comment-15485143 ] Zhe Zhang commented on HDFS-10276: -- Thanks [~kevincox] [~yuanbo] [~yzhangal] for the work. I think it's a

[jira] [Updated] (HDFS-10276) HDFS should not expose path info that user has no permission to see.

[ https://issues.apache.org/jira/browse/HDFS-10276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated HDFS-10276: - Fix Version/s: 2.7.4 > HDFS should not expose path info that user has no permission to see. >

[jira] [Updated] (HDFS-5802) NameNode does not check for inode type before traversing down a path

[ https://issues.apache.org/jira/browse/HDFS-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated HDFS-5802: Fix Version/s: 2.7.4 > NameNode does not check for inode type before traversing down a path >

[jira] [Commented] (HDFS-5802) NameNode does not check for inode type before traversing down a path

[ https://issues.apache.org/jira/browse/HDFS-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485138#comment-15485138 ] Zhe Zhang commented on HDFS-5802: - Thanks [~xiaochen] [~qwertymaniac] [~yzhangal] for the work. I think

[jira] [Commented] (HDFS-10713) Throttle FsNameSystem lock warnings

[ https://issues.apache.org/jira/browse/HDFS-10713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485124#comment-15485124 ] Arpit Agarwal commented on HDFS-10713: -- Also patch will have to be rebased since HDFS-10742 just

[jira] [Commented] (HDFS-10713) Throttle FsNameSystem lock warnings

[ https://issues.apache.org/jira/browse/HDFS-10713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485104#comment-15485104 ] Arpit Agarwal commented on HDFS-10713: -- Thanks [~hanishakoneru]. Few more comments: # Log statement

[jira] [Updated] (HDFS-8818) Allow Balancer to run faster

[ https://issues.apache.org/jira/browse/HDFS-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated HDFS-8818: Status: Patch Available (was: Reopened) > Allow Balancer to run faster > > >

[jira] [Commented] (HDFS-8818) Allow Balancer to run faster

[ https://issues.apache.org/jira/browse/HDFS-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484907#comment-15484907 ] Zhe Zhang commented on HDFS-8818: - Quick note that 2 failures were found even without the patch. HDFS-10859

[jira] [Updated] (HDFS-8818) Allow Balancer to run faster

[ https://issues.apache.org/jira/browse/HDFS-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated HDFS-8818: Attachment: HDFS-8818-branch-2.7.00.patch > Allow Balancer to run faster > > >

[jira] [Created] (HDFS-10859) TestBalancer#testUnknownDatanodeSimple and testBalancerWithKeytabs fail in branch-2.7

Zhe Zhang created HDFS-10859: Summary: TestBalancer#testUnknownDatanodeSimple and testBalancerWithKeytabs fail in branch-2.7 Key: HDFS-10859 URL: https://issues.apache.org/jira/browse/HDFS-10859 Project:

[jira] [Commented] (HDFS-10858) FBR processing may generate incorrect reportedBlock-blockGroup mapping

[ https://issues.apache.org/jira/browse/HDFS-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484885#comment-15484885 ] Jing Zhao commented on HDFS-10858: -- A simple fix is: {code} @@ -2677,7 +2677,7 @@ private void

[jira] [Created] (HDFS-10858) FBR processing may generate incorrect reportedBlock-blockGroup mapping

Jing Zhao created HDFS-10858: Summary: FBR processing may generate incorrect reportedBlock-blockGroup mapping Key: HDFS-10858 URL: https://issues.apache.org/jira/browse/HDFS-10858 Project: Hadoop HDFS

[jira] [Commented] (HDFS-10857) Rolling upgrade can make data unavailable when the cluster has many failed volumes

[ https://issues.apache.org/jira/browse/HDFS-10857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484851#comment-15484851 ] Kihwal Lee commented on HDFS-10857: --- We can have {{FsDatasetImpl#checkDataDir()}} remove the failed

[jira] [Reopened] (HDFS-8818) Allow Balancer to run faster

[ https://issues.apache.org/jira/browse/HDFS-8818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang reopened HDFS-8818: - Sorry to reopen this one. I think this is a valid improvement for branch-2.7 and I'm trying to backport it.

[jira] [Updated] (HDFS-10857) Rolling upgrade can make data unavailable when the cluster has many failed volumes

[ https://issues.apache.org/jira/browse/HDFS-10857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-10857: -- Target Version/s: 2.6.5 (was: 2.6.4) > Rolling upgrade can make data unavailable when the cluster has

[jira] [Updated] (HDFS-10857) Rolling upgrade can make data unavailable when the cluster has many failed volumes

[ https://issues.apache.org/jira/browse/HDFS-10857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-10857: -- Affects Version/s: (was: 2.7.4) 2.6.4 > Rolling upgrade can make data

[jira] [Comment Edited] (HDFS-10857) Rolling upgrade can make data unavailable when the cluster has many failed volumes

[ https://issues.apache.org/jira/browse/HDFS-10857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484751#comment-15484751 ] Kihwal Lee edited comment on HDFS-10857 at 9/12/16 6:11 PM: It looks like it

[jira] [Updated] (HDFS-10857) Rolling upgrade can make data unavailable when the cluster has many failed volumes

[ https://issues.apache.org/jira/browse/HDFS-10857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-10857: -- Assignee: (was: Kihwal Lee) > Rolling upgrade can make data unavailable when the cluster has many

[jira] [Updated] (HDFS-10857) Rolling upgrade can make data unavailable when the cluster has many failed volumes

[ https://issues.apache.org/jira/browse/HDFS-10857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-10857: -- Target Version/s: 2.6.4 (was: 2.7.4) > Rolling upgrade can make data unavailable when the cluster has

[jira] [Commented] (HDFS-10857) Rolling upgrade can make data unavailable when the cluster has many failed volumes

[ https://issues.apache.org/jira/browse/HDFS-10857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484751#comment-15484751 ] Kihwal Lee commented on HDFS-10857: --- It looks like it is fixed in 2.8 and later.

[jira] [Updated] (HDFS-10857) Rolling upgrade can make data unavailable when the cluster has many failed volumes

[ https://issues.apache.org/jira/browse/HDFS-10857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-10857: -- Target Version/s: 2.7.4 (was: 2.8.0, 2.7.4) > Rolling upgrade can make data unavailable when the

[jira] [Updated] (HDFS-10857) Rolling upgrade can make data unavailable when the cluster has many failed volumes

[ https://issues.apache.org/jira/browse/HDFS-10857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-10857: -- Affects Version/s: 2.7.4 > Rolling upgrade can make data unavailable when the cluster has many failed

[jira] [Commented] (HDFS-10830) FsDatasetImpl#removeVolumes crashes with IllegalMonitorStateException when vol being removed is in use

[ https://issues.apache.org/jira/browse/HDFS-10830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484713#comment-15484713 ] Manoj Govindassamy commented on HDFS-10830: --- Thanks [~arpitagarwal]. >

[jira] [Assigned] (HDFS-10857) Rolling upgrade can make data unavailable when the cluster has many failed volumes

[ https://issues.apache.org/jira/browse/HDFS-10857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee reassigned HDFS-10857: - Assignee: Kihwal Lee > Rolling upgrade can make data unavailable when the cluster has many

[jira] [Created] (HDFS-10857) Rolling upgrade can make data unavailable when the cluster has many failed volumes

Kihwal Lee created HDFS-10857: - Summary: Rolling upgrade can make data unavailable when the cluster has many failed volumes Key: HDFS-10857 URL: https://issues.apache.org/jira/browse/HDFS-10857 Project:

[jira] [Commented] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[ https://issues.apache.org/jira/browse/HDFS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484358#comment-15484358 ] Akira Ajisaka commented on HDFS-10856: -- I'm thinking we should add eol=lf in the following lines to

[jira] [Commented] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[ https://issues.apache.org/jira/browse/HDFS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484355#comment-15484355 ] Akira Ajisaka commented on HDFS-10856: -- Okay, would you use LF instead of CR+LF in eol? > Update the

[jira] [Comment Edited] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[ https://issues.apache.org/jira/browse/HDFS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484329#comment-15484329 ] Yiqun Lin edited comment on HDFS-10856 at 9/12/16 2:50 PM: --- Sorry, [~ajisakaa],

[jira] [Commented] (HDFS-10850) getEZForPath should NOT throw FNF

[ https://issues.apache.org/jira/browse/HDFS-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484338#comment-15484338 ] Sergio Peña commented on HDFS-10850: [~andrew.wang] The following class is the one that contains the

[jira] [Commented] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[ https://issues.apache.org/jira/browse/HDFS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484329#comment-15484329 ] Yiqun Lin commented on HDFS-10856: -- Sorry, [~ajisakaa], it seems that the v001 patch still can't been

[jira] [Commented] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[ https://issues.apache.org/jira/browse/HDFS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484279#comment-15484279 ] Hadoop QA commented on HDFS-10856: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[ https://issues.apache.org/jira/browse/HDFS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin updated HDFS-10856: - Attachment: HDFS-10856.001.patch > Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[jira] [Commented] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[ https://issues.apache.org/jira/browse/HDFS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484251#comment-15484251 ] Yiqun Lin commented on HDFS-10856: -- Reupload the v001 patch. > Update the comment of

[jira] [Updated] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[ https://issues.apache.org/jira/browse/HDFS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin updated HDFS-10856: - Attachment: (was: HDFS-10856.001.patch) > Update the comment of

[jira] [Commented] (HDFS-10690) Optimize insertion/removal of replica in ShortCircuitCache.java

[ https://issues.apache.org/jira/browse/HDFS-10690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484232#comment-15484232 ] Fenghua Hu commented on HDFS-10690: --- [~xyao], I just got environment to test your patch. Below is the

[jira] [Commented] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[ https://issues.apache.org/jira/browse/HDFS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483954#comment-15483954 ] Akira Ajisaka commented on HDFS-10856: -- Your patch looks good. Would you rebase it? > Update the

[jira] [Commented] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[ https://issues.apache.org/jira/browse/HDFS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483937#comment-15483937 ] Hadoop QA commented on HDFS-10856: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[ https://issues.apache.org/jira/browse/HDFS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin updated HDFS-10856: - Attachment: HDFS-10856.001.patch > Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[jira] [Updated] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[ https://issues.apache.org/jira/browse/HDFS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin updated HDFS-10856: - Status: Patch Available (was: Open) Attach a simple patch for make a change. Let me know if my change

[jira] [Assigned] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

[ https://issues.apache.org/jira/browse/HDFS-10856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin reassigned HDFS-10856: Assignee: Yiqun Lin > Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport >

[jira] [Created] (HDFS-10856) Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport

Akira Ajisaka created HDFS-10856: Summary: Update the comment of BPServiceActor$Scheduler#scheduleNextBlockReport Key: HDFS-10856 URL: https://issues.apache.org/jira/browse/HDFS-10856 Project: Hadoop

[jira] [Commented] (HDFS-10850) getEZForPath should NOT throw FNF

[ https://issues.apache.org/jira/browse/HDFS-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483282#comment-15483282 ] Andrew Wang commented on HDFS-10850: [~spena] could you help shed some light on how Hive uses this

[jira] [Commented] (HDFS-10838) Last full block report received time for each DN should be easily discoverable

[ https://issues.apache.org/jira/browse/HDFS-10838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483279#comment-15483279 ] Vinayakumar B commented on HDFS-10838: -- {quote}Was having one doubt about the compatibility of

<    1   2