[jira] [Updated] (HDFS-10347) Namenode report bad block method doesn't log the bad block or datanode.
[
https://issues.apache.org/jira/browse/HDFS-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junping Du updated HDFS-10347:
--
Fix Version/s: 2.8.0
> Namenode report bad block method doesn't log the bad block or datanode.
> ---
>
> Key: HDFS-10347
> URL: https://issues.apache.org/jira/browse/HDFS-10347
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
>Affects Versions: 2.7.0
>Reporter: Rushabh S Shah
>Assignee: Rushabh S Shah
>Priority: Minor
> Fix For: 2.8.0, 2.7.3, 3.0.0-alpha1
>
> Attachments: HDFS-10347.patch
>
>
> Currently the method {{FSNamesystem#reportBadBlocks}} doesn't log any
> information regarding the bad block id or the datanode on which corrupt block
> is detected.
> It would be helpful to log that information to debug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10347) Namenode report bad block method doesn't log the bad block or datanode.
[
https://issues.apache.org/jira/browse/HDFS-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee updated HDFS-10347:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.7.3
Status: Resolved (was: Patch Available)
> Namenode report bad block method doesn't log the bad block or datanode.
> ---
>
> Key: HDFS-10347
> URL: https://issues.apache.org/jira/browse/HDFS-10347
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
>Affects Versions: 2.7.0
>Reporter: Rushabh S Shah
>Assignee: Rushabh S Shah
>Priority: Minor
> Fix For: 2.7.3
>
> Attachments: HDFS-10347.patch
>
>
> Currently the method {{FSNamesystem#reportBadBlocks}} doesn't log any
> information regarding the bad block id or the datanode on which corrupt block
> is detected.
> It would be helpful to log that information to debug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10347) Namenode report bad block method doesn't log the bad block or datanode.
[
https://issues.apache.org/jira/browse/HDFS-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rushabh S Shah updated HDFS-10347:
--
Status: Patch Available (was: Open)
> Namenode report bad block method doesn't log the bad block or datanode.
> ---
>
> Key: HDFS-10347
> URL: https://issues.apache.org/jira/browse/HDFS-10347
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
>Affects Versions: 2.7.0
>Reporter: Rushabh S Shah
>Assignee: Rushabh S Shah
>Priority: Minor
> Attachments: HDFS-10347.patch
>
>
> Currently the method {{FSNamesystem#reportBadBlocks}} doesn't log any
> information regarding the bad block id or the datanode on which corrupt block
> is detected.
> It would be helpful to log that information to debug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10347) Namenode report bad block method doesn't log the bad block or datanode.
[
https://issues.apache.org/jira/browse/HDFS-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rushabh S Shah updated HDFS-10347:
--
Attachment: HDFS-10347.patch
> Namenode report bad block method doesn't log the bad block or datanode.
> ---
>
> Key: HDFS-10347
> URL: https://issues.apache.org/jira/browse/HDFS-10347
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
>Affects Versions: 2.7.0
>Reporter: Rushabh S Shah
>Assignee: Rushabh S Shah
>Priority: Minor
> Attachments: HDFS-10347.patch
>
>
> Currently the method {{FSNamesystem#reportBadBlocks}} doesn't log any
> information regarding the bad block id or the datanode on which corrupt block
> is detected.
> It would be helpful to log that information to debug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-10347) Namenode report bad block method doesn't log the bad block or datanode.
[
https://issues.apache.org/jira/browse/HDFS-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee updated HDFS-10347:
--
Summary: Namenode report bad block method doesn't log the bad block or
datanode. (was: Namenode report bad bad method doesn't log the bad block or
datanode.)
> Namenode report bad block method doesn't log the bad block or datanode.
> ---
>
> Key: HDFS-10347
> URL: https://issues.apache.org/jira/browse/HDFS-10347
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
>Affects Versions: 2.7.0
>Reporter: Rushabh S Shah
>Assignee: Rushabh S Shah
>Priority: Minor
>
> Currently the method {{FSNamesystem#reportBadBlocks}} doesn't log any
> information regarding the bad block id or the datanode on which corrupt block
> is detected.
> It would be helpful to log that information to debug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
