[jira] [Commented] (HDFS-11164) Mover should avoid unnecessary retries if the block is pinned

[ https://issues.apache.org/jira/browse/HDFS-11164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734561#comment-15734561 ] Surendra Singh Lilhore commented on HDFS-11164: --- I tested and its working fine. I have one

[jira] [Commented] (HDFS-8411) Add bytes count metrics to datanode for ECWorker

[ https://issues.apache.org/jira/browse/HDFS-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734508#comment-15734508 ] Kai Zheng commented on HDFS-8411: - Thanks [~andrew.wang] for the ping! It's good for me to have a very

[jira] [Commented] (HDFS-11224) Lifeline message should be ignored for dead nodes

[ https://issues.apache.org/jira/browse/HDFS-11224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734475#comment-15734475 ] Vinayakumar B commented on HDFS-11224: -- Thanks [~anu] for review. HDFS-9911, is not related to this

[jira] [Commented] (HDFS-9911) TestDataNodeLifeline Fails intermittently

[ https://issues.apache.org/jira/browse/HDFS-9911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734468#comment-15734468 ] Vinayakumar B commented on HDFS-9911: - I think analysis of [~tasanuma0829] makes sense. There is a

[jira] [Commented] (HDFS-11156) Add new op GETFILEBLOCKLOCATIONS to WebHDFS REST API

[ https://issues.apache.org/jira/browse/HDFS-11156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734432#comment-15734432 ] Weiwei Yang commented on HDFS-11156: Hi [~andrew.wang] Please let me know if you have any more

[jira] [Commented] (HDFS-11072) Add ability to unset and change directory EC policy

[ https://issues.apache.org/jira/browse/HDFS-11072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734398#comment-15734398 ] SammiChen commented on HDFS-11072: -- I'm rethinking about Rakesh and Andrew's comments. A directory can be

[jira] [Commented] (HDFS-11156) Add new op GETFILEBLOCKLOCATIONS to WebHDFS REST API

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

[jira] [Assigned] (HDFS-11226) Storagepolicy command is not working with "-fs" option

[ https://issues.apache.org/jira/browse/HDFS-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula reassigned HDFS-11226: --- Assignee: Brahma Reddy Battula > Storagepolicy command is not working with

[jira] [Created] (HDFS-11226) Storagepolicy command is not working with "-fs" option

Archana T created HDFS-11226: Summary: Storagepolicy command is not working with "-fs" option Key: HDFS-11226 URL: https://issues.apache.org/jira/browse/HDFS-11226 Project: Hadoop HDFS Issue

[jira] [Comment Edited] (HDFS-11225) NameNode crashed because deleteSnapshot held FSNamesystem lock too long

[ https://issues.apache.org/jira/browse/HDFS-11225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734211#comment-15734211 ] Yiqun Lin edited comment on HDFS-11225 at 12/9/16 4:03 AM: --- It also exists in

[jira] [Commented] (HDFS-11225) NameNode crashed because deleteSnapshot held FSNamesystem lock too long

[ https://issues.apache.org/jira/browse/HDFS-11225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734211#comment-15734211 ] Yiqun Lin commented on HDFS-11225: -- It also exists in release version 2.7.1 that I have ever seem this

[jira] [Updated] (HDFS-11156) Add new op GETFILEBLOCKLOCATIONS to WebHDFS REST API

[ https://issues.apache.org/jira/browse/HDFS-11156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated HDFS-11156: --- Attachment: HDFS-11156.12.patch > Add new op GETFILEBLOCKLOCATIONS to WebHDFS REST API >

[jira] [Commented] (HDFS-11160) VolumeScanner reports write-in-progress replicas as corrupt incorrectly

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

[jira] [Updated] (HDFS-11186) [SPS]: Daemon thread of SPS should start only in Active NN

[ https://issues.apache.org/jira/browse/HDFS-11186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-11186: --- Summary: [SPS]: Daemon thread of SPS should start only in Active NN (was: [SPS]:

[jira] [Updated] (HDFS-11123) [SPS] Make storage policy satisfier daemon work on/off dynamically

[ https://issues.apache.org/jira/browse/HDFS-11123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-11123: --- Attachment: HDFS-10285-HDFS-11123.00.patch Attached the initial patch for this

[jira] [Commented] (HDFS-11094) Send back HAState along with NamespaceInfo during a versionRequest as an optional parameter

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

[jira] [Updated] (HDFS-11094) Send back HAState along with NamespaceInfo during a versionRequest as an optional parameter

[ https://issues.apache.org/jira/browse/HDFS-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated HDFS-11094: --- Attachment: HDFS-11094.010.patch Attaching trunk patch again so it runs against jenkins instead of

[jira] [Updated] (HDFS-11094) Send back HAState along with NamespaceInfo during a versionRequest as an optional parameter

[ https://issues.apache.org/jira/browse/HDFS-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated HDFS-11094: --- Attachment: (was: HDFS-11094.010.patch) > Send back HAState along with NamespaceInfo during a

[jira] [Commented] (HDFS-11094) Send back HAState along with NamespaceInfo during a versionRequest as an optional parameter

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

[jira] [Commented] (HDFS-11207) Revert HDFS-5079. Cleaning up NNHAStatusHeartbeat.State DatanodeProtocolProtos.

[ https://issues.apache.org/jira/browse/HDFS-11207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733672#comment-15733672 ] Eric Badger commented on HDFS-11207: Thanks, [~kihwal]! > Revert HDFS-5079. Cleaning up

[jira] [Updated] (HDFS-11094) Send back HAState along with NamespaceInfo during a versionRequest as an optional parameter

[ https://issues.apache.org/jira/browse/HDFS-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated HDFS-11094: --- Status: Patch Available (was: Reopened) > Send back HAState along with NamespaceInfo during a

[jira] [Updated] (HDFS-11094) Send back HAState along with NamespaceInfo during a versionRequest as an optional parameter

[ https://issues.apache.org/jira/browse/HDFS-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated HDFS-11094: --- Attachment: HDFS-11094.010-b2.patch Attaching associated branch-2/branch-2.8 patch since it won't

[jira] [Updated] (HDFS-11094) Send back HAState along with NamespaceInfo during a versionRequest as an optional parameter

[ https://issues.apache.org/jira/browse/HDFS-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated HDFS-11094: --- Attachment: HDFS-11094.010.patch Attaching new trunk patch after the revert > Send back HAState

[jira] [Updated] (HDFS-11207) Revert HDFS-5079. Cleaning up NNHAStatusHeartbeat.State DatanodeProtocolProtos.

[ https://issues.apache.org/jira/browse/HDFS-11207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-11207: --- Fix Version/s: 3.0.0-alpha2 Release Note: HDFS-5079 was reverted since it introduced incompatible

[jira] [Updated] (HDFS-5079) Cleaning up NNHAStatusHeartbeat.State DatanodeProtocolProtos.

[ https://issues.apache.org/jira/browse/HDFS-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-5079: -- Release Note: This change affects wire-compatibility of the NameNode/DataNode heartbeat protocol. Only

[jira] [Updated] (HDFS-11094) Send back HAState along with NamespaceInfo during a versionRequest as an optional parameter

[ https://issues.apache.org/jira/browse/HDFS-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-11094: --- Fix Version/s: (was: 3.0.0-alpha2) > Send back HAState along with NamespaceInfo during a

[jira] [Commented] (HDFS-8411) Add bytes count metrics to datanode for ECWorker

[ https://issues.apache.org/jira/browse/HDFS-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733531#comment-15733531 ] Andrew Wang commented on HDFS-8411: --- Cool, thanks for the review Sammi! [~drankye] mind giving this a

[jira] [Commented] (HDFS-5079) Cleaning up NNHAStatusHeartbeat.State DatanodeProtocolProtos.

[ https://issues.apache.org/jira/browse/HDFS-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733521#comment-15733521 ] Hudson commented on HDFS-5079: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10973 (See

[jira] [Commented] (HDFS-11094) Send back HAState along with NamespaceInfo during a versionRequest as an optional parameter

[ https://issues.apache.org/jira/browse/HDFS-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733520#comment-15733520 ] Hudson commented on HDFS-11094: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10973 (See

[jira] [Resolved] (HDFS-11207) Unnecessary incompatible change of NNHAStatusHeartbeat.state in DatanodeProtocolProtos

[ https://issues.apache.org/jira/browse/HDFS-11207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee resolved HDFS-11207. --- Resolution: Done > Unnecessary incompatible change of NNHAStatusHeartbeat.state in >

[jira] [Commented] (HDFS-11207) Unnecessary incompatible change of NNHAStatusHeartbeat.state in DatanodeProtocolProtos

[ https://issues.apache.org/jira/browse/HDFS-11207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733496#comment-15733496 ] Kihwal Lee commented on HDFS-11207: --- Reverted HDFS-5079 and HDFS-11094. > Unnecessary incompatible

[jira] [Reopened] (HDFS-11094) Send back HAState along with NamespaceInfo during a versionRequest as an optional parameter

[ https://issues.apache.org/jira/browse/HDFS-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee reopened HDFS-11094: --- I've reverted this, as HDFS-5079 was reverted. Please rework the patch to reflect that. > Send back

[jira] [Updated] (HDFS-5079) Cleaning up NNHAStatusHeartbeat.State DatanodeProtocolProtos.

[ https://issues.apache.org/jira/browse/HDFS-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-5079: - Release Note: This change affects wire-compatibility of the NameNode/DataNode heartbeat protocol. Only

[jira] [Commented] (HDFS-5079) Cleaning up NNHAStatusHeartbeat.State DatanodeProtocolProtos.

[ https://issues.apache.org/jira/browse/HDFS-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733485#comment-15733485 ] Kihwal Lee commented on HDFS-5079: -- Reverted and updated the release note. > Cleaning up

[jira] [Updated] (HDFS-5079) Cleaning up NNHAStatusHeartbeat.State DatanodeProtocolProtos.

[ https://issues.apache.org/jira/browse/HDFS-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-5079: - Fix Version/s: 3.0.0-alpha1 > Cleaning up NNHAStatusHeartbeat.State DatanodeProtocolProtos. >

[jira] [Updated] (HDFS-5079) Cleaning up NNHAStatusHeartbeat.State DatanodeProtocolProtos.

[ https://issues.apache.org/jira/browse/HDFS-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-5079: - Fix Version/s: (was: 3.0.0-alpha1) > Cleaning up NNHAStatusHeartbeat.State DatanodeProtocolProtos. >

[jira] [Commented] (HDFS-11197) Listing encryption zones fails when deleting a EZ that is on a snapshotted directory

[ https://issues.apache.org/jira/browse/HDFS-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733390#comment-15733390 ] Hudson commented on HDFS-11197: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10972 (See

[jira] [Updated] (HDFS-11197) Listing encryption zones fails when deleting a EZ that is on a snapshotted directory

[ https://issues.apache.org/jira/browse/HDFS-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Chen updated HDFS-11197: - Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 3.0.0-alpha2 2.8.0

[jira] [Updated] (HDFS-11225) NameNode crashed because deleteSnapshot held FSNamesystem lock too long

[ https://issues.apache.org/jira/browse/HDFS-11225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-11225: --- Description: The deleteSnapshot operation is synchronous. In certain situations this

[jira] [Created] (HDFS-11225) NameNode crashed because deleteSnapshot held FSNamesystem lock too long

Wei-Chiu Chuang created HDFS-11225: -- Summary: NameNode crashed because deleteSnapshot held FSNamesystem lock too long Key: HDFS-11225 URL: https://issues.apache.org/jira/browse/HDFS-11225 Project:

[jira] [Commented] (HDFS-11197) Listing encryption zones fails when deleting a EZ that is on a snapshotted directory

[ https://issues.apache.org/jira/browse/HDFS-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1579#comment-1579 ] Xiao Chen commented on HDFS-11197: -- +1, committing this. > Listing encryption zones fails when deleting

[jira] [Commented] (HDFS-11160) VolumeScanner reports write-in-progress replicas as corrupt incorrectly

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

[jira] [Commented] (HDFS-11224) Lifeline message should be ignored for dead nodes

[ https://issues.apache.org/jira/browse/HDFS-11224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732985#comment-15732985 ] Anu Engineer commented on HDFS-11224: - Btw, I am +1 on committing this. > Lifeline message should be

[jira] [Commented] (HDFS-11224) Lifeline message should be ignored for dead nodes

[ https://issues.apache.org/jira/browse/HDFS-11224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732854#comment-15732854 ] Anu Engineer commented on HDFS-11224: - [~vinayrpet] Thanks for catching this and providing a patch.

[jira] [Updated] (HDFS-11160) VolumeScanner reports write-in-progress replicas as corrupt incorrectly

[ https://issues.apache.org/jira/browse/HDFS-11160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDFS-11160: --- Attachment: HDFS-11160.branch-2.patch Thanks [~kihwal] for the review! I am posting branch-2

[jira] [Commented] (HDFS-5079) Cleaning up NNHAStatusHeartbeat.State DatanodeProtocolProtos.

[ https://issues.apache.org/jira/browse/HDFS-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732634#comment-15732634 ] Kihwal Lee commented on HDFS-5079: -- This doesn't seem to much value while breaking compatibility during

[jira] [Commented] (HDFS-11207) Unnecessary incompatible change of NNHAStatusHeartbeat.state in DatanodeProtocolProtos

[ https://issues.apache.org/jira/browse/HDFS-11207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732628#comment-15732628 ] Kihwal Lee commented on HDFS-11207: --- I am going to revert HDFS-5079 later today if there is no

[jira] [Commented] (HDFS-11221) Have StorageDirectory return Optional instead of File/null

[ https://issues.apache.org/jira/browse/HDFS-11221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732184#comment-15732184 ] Ewan Higgs commented on HDFS-11221: --- Yes, this targets trunk only. > Have StorageDirectory return

[jira] [Commented] (HDFS-11223) Fix typos in HttpFs documentations

[ https://issues.apache.org/jira/browse/HDFS-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732078#comment-15732078 ] Yiqun Lin commented on HDFS-11223: -- Thanks [~ajisakaa]. > Fix typos in HttpFs documentations >

[jira] [Commented] (HDFS-11197) Listing encryption zones fails when deleting a EZ that is on a snapshotted directory

[ https://issues.apache.org/jira/browse/HDFS-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732067#comment-15732067 ] Wei-Chiu Chuang commented on HDFS-11197: +1 from me. [~xiaochen] would you also like to comment on

[jira] [Commented] (HDFS-11223) Fix typos in HttpFs documentations

[ https://issues.apache.org/jira/browse/HDFS-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732051#comment-15732051 ] Hudson commented on HDFS-11223: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10969 (See

[jira] [Comment Edited] (HDFS-8411) Add bytes count metrics to datanode for ECWorker

[ https://issues.apache.org/jira/browse/HDFS-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731999#comment-15731999 ] SammiChen edited comment on HDFS-8411 at 12/8/16 11:56 AM: --- Andrew, thanks for

[jira] [Commented] (HDFS-8411) Add bytes count metrics to datanode for ECWorker

[ https://issues.apache.org/jira/browse/HDFS-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731999#comment-15731999 ] SammiChen commented on HDFS-8411: - Andrew, thanks for provide the sample patch! It perfectly solves the

[jira] [Updated] (HDFS-11223) Fix typos in HttpFs documentations

[ https://issues.apache.org/jira/browse/HDFS-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated HDFS-11223: - Resolution: Fixed Fix Version/s: 3.0.0-alpha2 2.8.0 Status:

[jira] [Commented] (HDFS-11224) Lifeline message should be ignored for dead nodes

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

[jira] [Commented] (HDFS-11222) Document application/octet-stream as required content type for HTTPFS PUT and POST

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

[jira] [Updated] (HDFS-11222) Document application/octet-stream as required content type for HTTPFS PUT and POST

[ https://issues.apache.org/jira/browse/HDFS-11222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin updated HDFS-11222: - Attachment: HDFS-11222.001.patch > Document application/octet-stream as required content type for HTTPFS

[jira] [Updated] (HDFS-11222) Document application/octet-stream as required content type for HTTPFS PUT and POST

[ https://issues.apache.org/jira/browse/HDFS-11222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin updated HDFS-11222: - Attachment: (was: HDFS-11222.001.patch) > Document application/octet-stream as required content type

[jira] [Commented] (HDFS-11224) Lifeline message should be ignored for dead nodes

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

[jira] [Updated] (HDFS-11224) Lifeline message should be ignored for dead nodes

[ https://issues.apache.org/jira/browse/HDFS-11224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B updated HDFS-11224: - Attachment: HDFS-11224-02.patch Updated comment. > Lifeline message should be ignored for dead

[jira] [Commented] (HDFS-11224) Lifeline message should be ignored for dead nodes

[ https://issues.apache.org/jira/browse/HDFS-11224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731649#comment-15731649 ] Brahma Reddy Battula commented on HDFS-11224: - [~vinayrpet] Nice Catch... Patch LGTM, apart

[jira] [Commented] (HDFS-11156) Add new op GETFILEBLOCKLOCATIONS to WebHDFS REST API

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

[jira] [Commented] (HDFS-10206) Datanodes not sorted properly by distance when the reader isn't a datanode

[ https://issues.apache.org/jira/browse/HDFS-10206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731604#comment-15731604 ] Nandakumar commented on HDFS-10206: --- Thanks [~mingma] for the reviews and commit. > Datanodes not

[jira] [Updated] (HDFS-11224) Lifeline message should be ignored for dead nodes

[ https://issues.apache.org/jira/browse/HDFS-11224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B updated HDFS-11224: - Status: Patch Available (was: Open) > Lifeline message should be ignored for dead nodes >

[jira] [Updated] (HDFS-11224) Lifeline message should be ignored for dead nodes

[ https://issues.apache.org/jira/browse/HDFS-11224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B updated HDFS-11224: - Attachment: HDFS-11224-01.patch Attached the patch. Please review. > Lifeline message should be