[jira] [Commented] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378879#comment-15378879 ] Vinayakumar B commented on HDFS-10587: -- bq. Here it says checksum error at 81920, which is at the

[jira] [Commented] (HDFS-10626) VolumeScanner prints incorrect IOException in reportBadBlocks operation

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

[jira] [Commented] (HDFS-10632) DataXceiver to report the length of the block it's receiving

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

[jira] [Commented] (HDFS-10600) PlanCommand#getThrsholdPercentage should not use throughput value.

[ https://issues.apache.org/jira/browse/HDFS-10600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378758#comment-15378758 ] Yiqun Lin commented on HDFS-10600: -- Thanks a lot for the commit, [~eddyxu]! >

[jira] [Updated] (HDFS-10626) VolumeScanner prints incorrect IOException in reportBadBlocks operation

[ https://issues.apache.org/jira/browse/HDFS-10626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin updated HDFS-10626: - Attachment: HDFS-10626.002.patch > VolumeScanner prints incorrect IOException in reportBadBlocks

[jira] [Commented] (HDFS-10626) VolumeScanner prints incorrect IOException in reportBadBlocks operation

[ https://issues.apache.org/jira/browse/HDFS-10626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378755#comment-15378755 ] Yiqun Lin commented on HDFS-10626: -- Thanks [~shahrs87] and [~yzhangal] for the review. Post the new patch

[jira] [Updated] (HDFS-10632) DataXceiver to report the length of the block it's receiving

[ https://issues.apache.org/jira/browse/HDFS-10632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin updated HDFS-10632: - Status: Patch Available (was: Open) Attach a simple patch to fix this. > DataXceiver to report the

[jira] [Updated] (HDFS-10632) DataXceiver to report the length of the block it's receiving

[ https://issues.apache.org/jira/browse/HDFS-10632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin updated HDFS-10632: - Attachment: HDFS-10632.001.patch > DataXceiver to report the length of the block it's receiving >

[jira] [Assigned] (HDFS-10632) DataXceiver to report the length of the block it's receiving

[ https://issues.apache.org/jira/browse/HDFS-10632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin reassigned HDFS-10632: Assignee: Yiqun Lin > DataXceiver to report the length of the block it's receiving >

[jira] [Commented] (HDFS-10614) Appended blocks can be closed even before IBRs from DataNodes

[ https://issues.apache.org/jira/browse/HDFS-10614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378688#comment-15378688 ] Jing Zhao commented on HDFS-10614: -- Thanks for the fix and review, [~vinayrpet] and [~ajisakaa]. The

[jira] [Commented] (HDFS-10628) Log HDFS Balancer exit message to its own log

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

[jira] [Commented] (HDFS-8940) Support for large-scale multi-tenant inotify service

[ https://issues.apache.org/jira/browse/HDFS-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378555#comment-15378555 ] Ming Ma commented on HDFS-8940: --- [~drankye], it might come from the following assumption. Only admins can use

[jira] [Commented] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378546#comment-15378546 ] Wei-Chiu Chuang commented on HDFS-10587: I see. So for the logs I saw, there's no "Appending to "

[jira] [Updated] (HDFS-10632) DataXceiver to report the length of the block it's receiving

[ https://issues.apache.org/jira/browse/HDFS-10632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang updated HDFS-10632: - Labels: supportability (was: ) > DataXceiver to report the length of the block it's receiving >

[jira] [Updated] (HDFS-10632) DataXceiver to report the length of the block it's receiving

[ https://issues.apache.org/jira/browse/HDFS-10632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang updated HDFS-10632: - Priority: Trivial (was: Major) Component/s: hdfs datanode > DataXceiver

[jira] [Commented] (HDFS-8940) Support for large-scale multi-tenant inotify service

[ https://issues.apache.org/jira/browse/HDFS-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378541#comment-15378541 ] Kai Zheng commented on HDFS-8940: - Thanks [~mingma] for the confirm. I have another question, after reading

[jira] [Created] (HDFS-10632) DataXceiver to report the length of the block it's receiving

Yongjun Zhang created HDFS-10632: Summary: DataXceiver to report the length of the block it's receiving Key: HDFS-10632 URL: https://issues.apache.org/jira/browse/HDFS-10632 Project: Hadoop HDFS

[jira] [Updated] (HDFS-10628) Log HDFS Balancer exit message to its own log

[ https://issues.apache.org/jira/browse/HDFS-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiayi Zhou updated HDFS-10628: -- Attachment: HDFS-10628.002.patch Checkstyle fixed. Failure tests are not related as it's just a simple

[jira] [Comment Edited] (HDFS-10326) Disable setting tcp socket send/receive buffers for write pipelines

[ https://issues.apache.org/jira/browse/HDFS-10326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378500#comment-15378500 ] Mingliang Liu edited comment on HDFS-10326 at 7/14/16 10:18 PM: The v1

[jira] [Commented] (HDFS-10326) Disable setting tcp socket send/receive buffers for write pipelines

[ https://issues.apache.org/jira/browse/HDFS-10326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378500#comment-15378500 ] Mingliang Liu commented on HDFS-10326: -- The v1 patch rebases from {{trunk}} and resolve conflicts

[jira] [Updated] (HDFS-10326) Disable setting tcp socket send/receive buffers for write pipelines

[ https://issues.apache.org/jira/browse/HDFS-10326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingliang Liu updated HDFS-10326: - Attachment: HDFS-10326.001.patch > Disable setting tcp socket send/receive buffers for write

[jira] [Assigned] (HDFS-10326) Disable setting tcp socket send/receive buffers for write pipelines

[ https://issues.apache.org/jira/browse/HDFS-10326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingliang Liu reassigned HDFS-10326: Assignee: Mingliang Liu (was: Daryn Sharp) > Disable setting tcp socket send/receive

[jira] [Updated] (HDFS-10326) Disable setting tcp socket send/receive buffers for write pipelines

[ https://issues.apache.org/jira/browse/HDFS-10326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingliang Liu updated HDFS-10326: - Assignee: Daryn Sharp (was: Mingliang Liu) > Disable setting tcp socket send/receive buffers for

[jira] [Commented] (HDFS-10614) Appended blocks can be closed even before IBRs from DataNodes

[ https://issues.apache.org/jira/browse/HDFS-10614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378492#comment-15378492 ] Akira Ajisaka commented on HDFS-10614: -- Looks good to me. +1 pending another committer's review. cc:

[jira] [Commented] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378483#comment-15378483 ] Yongjun Zhang commented on HDFS-10587: -- I think this looks why we had new data reaching the new DN

[jira] [Commented] (HDFS-10623) Remove unused import of httpclient.HttpConnection from TestWebHdfsTokens.

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

[jira] [Commented] (HDFS-10628) Log HDFS Balancer exit message to its own log

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

[jira] [Commented] (HDFS-10601) Improve log message to include hostname when the NameNode is in safemode

[ https://issues.apache.org/jira/browse/HDFS-10601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378418#comment-15378418 ] Sean Busbey commented on HDFS-10601: +1 (non-binding) > Improve log message to include hostname when

[jira] [Commented] (HDFS-10628) Log HDFS Balancer exit message to its own log

[ https://issues.apache.org/jira/browse/HDFS-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378367#comment-15378367 ] Jiayi Zhou commented on HDFS-10628: --- Versions updated as comment. > Log HDFS Balancer exit message to

[jira] [Updated] (HDFS-10628) Log HDFS Balancer exit message to its own log

[ https://issues.apache.org/jira/browse/HDFS-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiayi Zhou updated HDFS-10628: -- Affects Version/s: 2.8.0 Target Version/s: 2.8.0 > Log HDFS Balancer exit message to its own log >

[jira] [Updated] (HDFS-10628) Log HDFS Balancer exit message to its own log

[ https://issues.apache.org/jira/browse/HDFS-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-10628: --- Priority: Minor (was: Major) Component/s: balancer & mover > Log HDFS Balancer exit message

[jira] [Commented] (HDFS-10628) Log HDFS Balancer exit message to its own log

[ https://issues.apache.org/jira/browse/HDFS-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378365#comment-15378365 ] Andrew Wang commented on HDFS-10628: +1 pending Jenkins, thanks for finding and fixing this Jiayi! Do

[jira] [Commented] (HDFS-10627) Volume Scanner mark a block as "suspect" even if the block sender encounters 'Broken pipe' or 'Connection reset by peer' exception

[ https://issues.apache.org/jira/browse/HDFS-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378353#comment-15378353 ] Daryn Sharp commented on HDFS-10627: Rushabh and I checked a few random healthy nodes on multiple

[jira] [Created] (HDFS-10631) Federation State Store ZooKeeper implementation

Inigo Goiri created HDFS-10631: -- Summary: Federation State Store ZooKeeper implementation Key: HDFS-10631 URL: https://issues.apache.org/jira/browse/HDFS-10631 Project: Hadoop HDFS Issue Type:

[jira] [Commented] (HDFS-10477) Stop decommission a rack of DataNodes caused NameNode fail over to standby

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

[jira] [Created] (HDFS-10630) Federation State Store

Inigo Goiri created HDFS-10630: -- Summary: Federation State Store Key: HDFS-10630 URL: https://issues.apache.org/jira/browse/HDFS-10630 Project: Hadoop HDFS Issue Type: Sub-task

[jira] [Created] (HDFS-10629) Federation Router

Inigo Goiri created HDFS-10629: -- Summary: Federation Router Key: HDFS-10629 URL: https://issues.apache.org/jira/browse/HDFS-10629 Project: Hadoop HDFS Issue Type: Sub-task Components:

[jira] [Commented] (HDFS-9271) Implement basic NN operations

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

[jira] [Updated] (HDFS-10628) Log HDFS Balancer exit message to its own log

[ https://issues.apache.org/jira/browse/HDFS-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiayi Zhou updated HDFS-10628: -- Attachment: HDFS-10628.001.patch > Log HDFS Balancer exit message to its own log >

[jira] [Updated] (HDFS-10628) Log HDFS Balancer exit message to its own log

[ https://issues.apache.org/jira/browse/HDFS-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiayi Zhou updated HDFS-10628: -- Status: Patch Available (was: Open) Simply log the exit message in Balancer log > Log HDFS Balancer

[jira] [Updated] (HDFS-10628) Log HDFS Balancer exit message to its own log

[ https://issues.apache.org/jira/browse/HDFS-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiayi Zhou updated HDFS-10628: -- Description: Currently, the exit message is logged to stderr. It would be more convenient if we also

[jira] [Created] (HDFS-10628) Log HDFS Balancer exit message to its own log

Jiayi Zhou created HDFS-10628: - Summary: Log HDFS Balancer exit message to its own log Key: HDFS-10628 URL: https://issues.apache.org/jira/browse/HDFS-10628 Project: Hadoop HDFS Issue Type:

[jira] [Commented] (HDFS-10623) Remove unused import of httpclient.HttpConnection from TestWebHdfsTokens.

[ https://issues.apache.org/jira/browse/HDFS-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378293#comment-15378293 ] Hanisha Koneru commented on HDFS-10623: --- Thank you [~arpitagarwal] for reviewing and committing the

[jira] [Updated] (HDFS-10623) Remove unused import of httpclient.HttpConnection from TestWebHdfsTokens.

[ https://issues.apache.org/jira/browse/HDFS-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-10623: - Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.7.3 Target

[jira] [Commented] (HDFS-10627) Volume Scanner mark a block as "suspect" even if the block sender encounters 'Broken pipe' or 'Connection reset by peer' exception

[ https://issues.apache.org/jira/browse/HDFS-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378278#comment-15378278 ] Daryn Sharp commented on HDFS-10627: I agree it's unfortunate there's no feedback mechanism. I

[jira] [Commented] (HDFS-10623) Remove unused import of httpclient.HttpConnection from TestWebHdfsTokens.

[ https://issues.apache.org/jira/browse/HDFS-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378245#comment-15378245 ] Arpit Agarwal commented on HDFS-10623: -- +1 this doesn't need a full Jenkins run. The test builds and

[jira] [Updated] (HDFS-9271) Implement basic NN operations

[ https://issues.apache.org/jira/browse/HDFS-9271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anatoli Shein updated HDFS-9271: Attachment: HDFS-9271.HDFS-8707.003.patch Please review the new patch. > Implement basic NN

[jira] [Commented] (HDFS-9271) Implement basic NN operations

[ https://issues.apache.org/jira/browse/HDFS-9271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378193#comment-15378193 ] Anatoli Shein commented on HDFS-9271: - Thank you [~bobhansen] for your comments. Here is what I did: A

[jira] [Updated] (HDFS-10623) Remove unused import of httpclient.HttpConnection from TestWebHdfsTokens.

[ https://issues.apache.org/jira/browse/HDFS-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanisha Koneru updated HDFS-10623: -- Status: Patch Available (was: In Progress) > Remove unused import of httpclient.HttpConnection

[jira] [Updated] (HDFS-10623) Remove unused import of httpclient.HttpConnection from TestWebHdfsTokens.

[ https://issues.apache.org/jira/browse/HDFS-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanisha Koneru updated HDFS-10623: -- Status: In Progress (was: Patch Available) > Remove unused import of httpclient.HttpConnection

[jira] [Updated] (HDFS-10623) Remove unused import of httpclient.HttpConnection from TestWebHdfsTokens.

[ https://issues.apache.org/jira/browse/HDFS-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanisha Koneru updated HDFS-10623: -- Attachment: HDFS-10623-branch-2.7.3.000.patch > Remove unused import of

[jira] [Work started] (HDFS-8897) Loadbalancer always exits with : java.io.IOException: Another Balancer is running.. Exiting ...

[ https://issues.apache.org/jira/browse/HDFS-8897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-8897 started by John Zhuge. > Loadbalancer always exits with : java.io.IOException: Another Balancer is > running..

[jira] [Assigned] (HDFS-8897) Loadbalancer always exits with : java.io.IOException: Another Balancer is running.. Exiting ...

[ https://issues.apache.org/jira/browse/HDFS-8897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Zhuge reassigned HDFS-8897: Assignee: John Zhuge > Loadbalancer always exits with : java.io.IOException: Another Balancer is >

[jira] [Updated] (HDFS-10477) Stop decommission a rack of DataNodes caused NameNode fail over to standby

[ https://issues.apache.org/jira/browse/HDFS-10477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yunjiong zhao updated HDFS-10477: - Attachment: HDFS-10477.005.patch Update patch to fix unit test. When called by tests like

[jira] [Commented] (HDFS-10623) Remove unused import of httpclient.HttpConnection from TestWebHdfsTokens.

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

[jira] [Updated] (HDFS-10623) Remove unused import of httpclient.HttpConnection from TestWebHdfsTokens.

[ https://issues.apache.org/jira/browse/HDFS-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanisha Koneru updated HDFS-10623: -- Status: Patch Available (was: Open) > Remove unused import of httpclient.HttpConnection from

[jira] [Updated] (HDFS-10623) Remove unused import of httpclient.HttpConnection from TestWebHdfsTokens.

[ https://issues.apache.org/jira/browse/HDFS-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanisha Koneru updated HDFS-10623: -- Attachment: HDFS-10623.000.patch > Remove unused import of httpclient.HttpConnection from

[jira] [Updated] (HDFS-10623) Remove unused import of httpclient.HttpConnection from TestWebHdfsTokens.

[ https://issues.apache.org/jira/browse/HDFS-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanisha Koneru updated HDFS-10623: -- Target Version/s: 2.7.3 > Remove unused import of httpclient.HttpConnection from

[jira] [Updated] (HDFS-7686) Re-add rapid rescan of possibly corrupt block feature to the block scanner

[ https://issues.apache.org/jira/browse/HDFS-7686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated HDFS-7686: --- Assignee: Colin P. McCabe (was: Rakesh R) > Re-add rapid rescan of possibly corrupt block feature to the

[jira] [Assigned] (HDFS-7686) Re-add rapid rescan of possibly corrupt block feature to the block scanner

[ https://issues.apache.org/jira/browse/HDFS-7686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R reassigned HDFS-7686: -- Assignee: Rakesh R (was: Colin P. McCabe) > Re-add rapid rescan of possibly corrupt block feature to

[jira] [Commented] (HDFS-10600) PlanCommand#getThrsholdPercentage should not use throughput value.

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

[jira] [Commented] (HDFS-10467) Router-based HDFS federation

[ https://issues.apache.org/jira/browse/HDFS-10467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377362#comment-15377362 ] Jing Zhao commented on HDFS-10467: -- Assigned the jira to [~elgoiri]. bq. Probably, it's a good idea to

[jira] [Updated] (HDFS-10600) PlanCommand#getThrsholdPercentage should not use throughput value.

[ https://issues.apache.org/jira/browse/HDFS-10600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei (Eddy) Xu updated HDFS-10600: - Resolution: Fixed Fix Version/s: (was: 2.9.0) 3.0.0-alpha1

[jira] [Updated] (HDFS-10467) Router-based HDFS federation

[ https://issues.apache.org/jira/browse/HDFS-10467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-10467: - Assignee: Inigo Goiri > Router-based HDFS federation > > >

[jira] [Updated] (HDFS-10626) VolumeScanner prints incorrect IOException in reportBadBlocks operation

[ https://issues.apache.org/jira/browse/HDFS-10626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang updated HDFS-10626: - Labels: supportability (was: ) > VolumeScanner prints incorrect IOException in reportBadBlocks

[jira] [Commented] (HDFS-10626) VolumeScanner prints incorrect IOException in reportBadBlocks operation

[ https://issues.apache.org/jira/browse/HDFS-10626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377289#comment-15377289 ] Yongjun Zhang commented on HDFS-10626: -- HI [~linyiqun], Thanks for reporting and working on the

[jira] [Commented] (HDFS-10627) Volume Scanner mark a block as "suspect" even if the block sender encounters 'Broken pipe' or 'Connection reset by peer' exception

[ https://issues.apache.org/jira/browse/HDFS-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377268#comment-15377268 ] Wei-Chiu Chuang commented on HDFS-10627: [~shahrs87] this piece of code can be useful during block

[jira] [Comment Edited] (HDFS-10625) VolumeScanner to report why a block is found bad

[ https://issues.apache.org/jira/browse/HDFS-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377247#comment-15377247 ] Yongjun Zhang edited comment on HDFS-10625 at 7/14/16 4:44 PM: --- Thanks

[jira] [Updated] (HDFS-10627) Volume Scanner mark a block as "suspect" even if the block sender encounters 'Broken pipe' or 'Connection reset by peer' exception

[ https://issues.apache.org/jira/browse/HDFS-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rushabh S Shah updated HDFS-10627: -- Description: In the BlockSender code, {code:title=BlockSender.java|borderStyle=solid}

[jira] [Created] (HDFS-10627) Volume Scanner mark a block as "suspect" even if the block sender encounters 'Broken pipe' or 'Connection reset by peer' exception

Rushabh S Shah created HDFS-10627: - Summary: Volume Scanner mark a block as "suspect" even if the block sender encounters 'Broken pipe' or 'Connection reset by peer' exception Key: HDFS-10627 URL:

[jira] [Commented] (HDFS-10625) VolumeScanner to report why a block is found bad

[ https://issues.apache.org/jira/browse/HDFS-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377247#comment-15377247 ] Yongjun Zhang commented on HDFS-10625: -- Thanks [~shahrs87] for the patch and [~jojochuang] for the

[jira] [Commented] (HDFS-10625) VolumeScanner to report why a block is found bad

[ https://issues.apache.org/jira/browse/HDFS-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377228#comment-15377228 ] Wei-Chiu Chuang commented on HDFS-10625: looks good to me. VolumeScanner uses BlockSender and a

[jira] [Commented] (HDFS-10596) libhdfs++: Implement hdfsFileIsEncrypted

[ https://issues.apache.org/jira/browse/HDFS-10596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377213#comment-15377213 ] James Clampffer commented on HDFS-10596: {code} 16/07/05 17:12:27 WARN util.NativeCodeLoader:

[jira] [Commented] (HDFS-10625) VolumeScanner to report why a block is found bad

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

[jira] [Commented] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377160#comment-15377160 ] Yongjun Zhang commented on HDFS-10587: -- Thanks a lot [~vinayrpet] and [~xupener]! As Vinay pointed,

[jira] [Commented] (HDFS-10328) Add per-cache-pool default replication num configuration

[ https://issues.apache.org/jira/browse/HDFS-10328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377045#comment-15377045 ] xupeng commented on HDFS-10328: --- [~cmccabe] Thanks a lot for the review :) > Add per-cache-pool default

[jira] [Assigned] (HDFS-10625) VolumeScanner to report why a block is found bad

[ https://issues.apache.org/jira/browse/HDFS-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rushabh S Shah reassigned HDFS-10625: - Assignee: Rushabh S Shah > VolumeScanner to report why a block is found bad >

[jira] [Updated] (HDFS-10625) VolumeScanner to report why a block is found bad

[ https://issues.apache.org/jira/browse/HDFS-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rushabh S Shah updated HDFS-10625: -- Attachment: HDFS-10625.patch > VolumeScanner to report why a block is found bad >

[jira] [Updated] (HDFS-10625) VolumeScanner to report why a block is found bad

[ https://issues.apache.org/jira/browse/HDFS-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rushabh S Shah updated HDFS-10625: -- Status: Patch Available (was: Open) Please review. > VolumeScanner to report why a block is

[jira] [Commented] (HDFS-10626) VolumeScanner prints incorrect IOException in reportBadBlocks operation

[ https://issues.apache.org/jira/browse/HDFS-10626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376964#comment-15376964 ] Rushabh S Shah commented on HDFS-10626: --- ltgm +1 (non binding) > VolumeScanner prints incorrect

[jira] [Commented] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376940#comment-15376940 ] Vinayakumar B commented on HDFS-10587: -- bq. org.apache.hadoop.fs.ChecksumException: Checksum error:

[jira] [Commented] (HDFS-10626) VolumeScanner prints incorrect IOException in reportBadBlocks operation

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

[jira] [Commented] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376897#comment-15376897 ] xupeng commented on HDFS-10587: --- hi [~vinayrpet] : logs related are listed below 134.228 {noformat}

[jira] [Issue Comment Deleted] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xupeng updated HDFS-10587: -- Comment: was deleted (was: And here are the logs : Hbase log {noformat} 2016-07-13 11:48:29,475 WARN

[jira] [Updated] (HDFS-10626) VolumeScanner prints incorrect IOException in reportBadBlocks operation

[ https://issues.apache.org/jira/browse/HDFS-10626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin updated HDFS-10626: - Description: VolumeScanner throws incorrect IOException in {{datanode.reportBadBlocks}}. The related

[jira] [Updated] (HDFS-10626) VolumeScanner prints incorrect IOException in reportBadBlocks operation

[ https://issues.apache.org/jira/browse/HDFS-10626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin updated HDFS-10626: - Attachment: HDFS-10626.001.patch Attach a simple patch to do a minor change. > VolumeScanner prints

[jira] [Updated] (HDFS-10626) VolumeScanner prints incorrect IOException in reportBadBlocks operation

[ https://issues.apache.org/jira/browse/HDFS-10626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin updated HDFS-10626: - Status: Patch Available (was: Open) > VolumeScanner prints incorrect IOException in reportBadBlocks

[jira] [Updated] (HDFS-10626) VolumeScanner prints incorrect IOException in reportBadBlocks operation

[ https://issues.apache.org/jira/browse/HDFS-10626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yiqun Lin updated HDFS-10626: - Priority: Minor (was: Major) > VolumeScanner prints incorrect IOException in reportBadBlocks operation >

[jira] [Created] (HDFS-10626) VolumeScanner prints incorrect IOException in reportBadBlocks operation

Yiqun Lin created HDFS-10626: Summary: VolumeScanner prints incorrect IOException in reportBadBlocks operation Key: HDFS-10626 URL: https://issues.apache.org/jira/browse/HDFS-10626 Project: Hadoop HDFS

[jira] [Commented] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376794#comment-15376794 ] Vinayakumar B commented on HDFS-10587: -- Hi [~xupeng], Can you add 229 and 77 logs as well for this

[jira] [Comment Edited] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376739#comment-15376739 ] xupeng edited comment on HDFS-10587 at 7/14/16 10:54 AM: - Hi all : I encountered

[jira] [Comment Edited] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376750#comment-15376750 ] xupeng edited comment on HDFS-10587 at 7/14/16 10:52 AM: - And here are the logs :

[jira] [Comment Edited] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376750#comment-15376750 ] xupeng edited comment on HDFS-10587 at 7/14/16 10:49 AM: - And here are the logs :

[jira] [Comment Edited] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376750#comment-15376750 ] xupeng edited comment on HDFS-10587 at 7/14/16 10:47 AM: - And here are the logs :

[jira] [Commented] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376750#comment-15376750 ] xupeng commented on HDFS-10587: --- And here are the logs : Hbase log

[jira] [Commented] (HDFS-10587) Incorrect offset/length calculation in pipeline recovery causes block corruption

[ https://issues.apache.org/jira/browse/HDFS-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376739#comment-15376739 ] xupeng commented on HDFS-10587: --- Hi all : I encountered the same issue, here is the scenario : a. hbase

[jira] [Commented] (HDFS-10570) Remove classpath conflicts of netty-all jar in hadoop-hdfs-client

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

[jira] [Commented] (HDFS-10570) Remove classpath conflicts of netty-all jar in hadoop-hdfs-client

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

[jira] [Commented] (HDFS-10570) Remove classpath conflicts of netty-all jar in hadoop-hdfs-client

[ https://issues.apache.org/jira/browse/HDFS-10570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376650#comment-15376650 ] Steve Loughran commented on HDFS-10570: --- +1, committed to trunk. I haven't yet cherry picked it to

[jira] [Updated] (HDFS-10570) Remove classpath conflicts of netty-all jar in hadoop-hdfs-client

[ https://issues.apache.org/jira/browse/HDFS-10570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HDFS-10570: -- Status: Open (was: Patch Available) > Remove classpath conflicts of netty-all jar in

  1   2   >