[jira] [Commented] (HDFS-7452) Can we skip getCorruptFiles() call for standby NameNode..?
[
https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156192#comment-15156192
]
Hadoop QA commented on HDFS-7452:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 10m 38s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
58s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 44s
{color} | {color:green} trunk passed with JDK v1.8.0_72 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 42s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
22s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 51s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
13s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
55s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 8s
{color} | {color:green} trunk passed with JDK v1.8.0_72 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 44s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
48s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 39s
{color} | {color:green} the patch passed with JDK v1.8.0_72 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 39s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 41s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 41s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
20s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 49s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
11s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 7s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 3s
{color} | {color:green} the patch passed with JDK v1.8.0_72 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 40s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 52m 52s {color}
| {color:red} hadoop-hdfs in the patch failed with JDK v1.8.0_72. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 49m 56s
{color} | {color:green} hadoop-hdfs in the patch passed with JDK v1.7.0_95.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 138m 39s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| JDK v1.8.0_72 Failed junit tests |
hadoop.hdfs.server.blockmanagement.TestReconstructStripedBlocksWithRackAwareness
|
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:0ca8df7 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/1273/HDFS-7452-002.patch |
| JIRA Issue | HDFS-7452 |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux bba4fa3f66b8 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed
Sep 3 21:56:
[jira] [Commented] (HDFS-7452) Can we skip getCorruptFiles() call for standby NameNode..?
[
https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155897#comment-15155897
]
Brahma Reddy Battula commented on HDFS-7452:
Uploaded the patch to fix the checkstyle comment.
> Can we skip getCorruptFiles() call for standby NameNode..?
> --
>
> Key: HDFS-7452
> URL: https://issues.apache.org/jira/browse/HDFS-7452
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Brahma Reddy Battula
>Assignee: Brahma Reddy Battula
>Priority: Minor
> Attachments: HDFS-7452-002.patch, HDFS-7452.patch
>
>
> Seen following warns logs from StandBy Namenode logs ..
> {noformat}
> 2014-11-27 17:50:32,497 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:42,557 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:52,617 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,117 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:02,678 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:12,738 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:22,798 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,119 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> {noformat}
> do we need to call for SNN..? I feel, it might not be required.can we
> maintain state wide..Please let me know, If I am wrong..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-7452) Can we skip getCorruptFiles() call for standby NameNode..?
[
https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148399#comment-15148399
]
Vinayakumar B commented on HDFS-7452:
-
Patch seems to be Okay, except the checkstyle comment.
+1 once that's addressed.
> Can we skip getCorruptFiles() call for standby NameNode..?
> --
>
> Key: HDFS-7452
> URL: https://issues.apache.org/jira/browse/HDFS-7452
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Brahma Reddy Battula
>Assignee: Brahma Reddy Battula
>Priority: Trivial
> Attachments: HDFS-7452.patch
>
>
> Seen following warns logs from StandBy Namenode logs ..
> {noformat}
> 2014-11-27 17:50:32,497 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:42,557 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:52,617 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,117 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:02,678 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:12,738 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:22,798 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,119 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> {noformat}
> do we need to call for SNN..? I feel, it might not be required.can we
> maintain state wide..Please let me know, If I am wrong..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-7452) Can we skip getCorruptFiles() call for standby NameNode..?
[
https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144956#comment-15144956
]
Hadoop QA commented on HDFS-7452:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 10s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
21s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 38s
{color} | {color:green} trunk passed with JDK v1.8.0_72 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 41s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
22s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 51s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
13s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
51s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 5s
{color} | {color:green} trunk passed with JDK v1.8.0_72 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 47s
{color} | {color:green} trunk passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
45s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 37s
{color} | {color:green} the patch passed with JDK v1.8.0_72 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 37s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 39s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 39s
{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m 20s
{color} | {color:red} hadoop-hdfs-project/hadoop-hdfs: patch generated 1 new +
186 unchanged - 0 fixed = 187 total (was 186) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 48s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
12s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 5s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 3s
{color} | {color:green} the patch passed with JDK v1.8.0_72 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 45s
{color} | {color:green} the patch passed with JDK v1.7.0_95 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 53m 9s {color}
| {color:red} hadoop-hdfs in the patch failed with JDK v1.8.0_72. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 50m 24s {color}
| {color:red} hadoop-hdfs in the patch failed with JDK v1.7.0_95. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
19s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 127m 2s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| JDK v1.8.0_72 Failed junit tests |
hadoop.hdfs.server.blockmanagement.TestComputeInvalidateWork |
| | hadoop.hdfs.server.datanode.TestBlockScanner |
| | hadoop.fs.TestHdfsNativeCodeLoader |
| JDK v1.7.0_95 Failed junit tests |
hadoop.hdfs.qjournal.client.TestQuorumJournalManager |
| | hadoop.fs.TestHdfsNativeCodeLoader |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:0ca8df7 |
| JIRA Patch URL |
https://issues.apache.org/ji
[jira] [Commented] (HDFS-7452) Can we skip getCorruptFiles() call for standby NameNode..?
[
https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144728#comment-15144728
]
Brahma Reddy Battula commented on HDFS-7452:
uploaded the patch to eliminate spam in standbynamenode..Kindly review..
> Can we skip getCorruptFiles() call for standby NameNode..?
> --
>
> Key: HDFS-7452
> URL: https://issues.apache.org/jira/browse/HDFS-7452
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Brahma Reddy Battula
>Assignee: Brahma Reddy Battula
>Priority: Trivial
> Attachments: HDFS-7452.patch
>
>
> Seen following warns logs from StandBy Namenode logs ..
> {noformat}
> 2014-11-27 17:50:32,497 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:42,557 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:52,617 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,117 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:02,678 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:12,738 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:22,798 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,119 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> {noformat}
> do we need to call for SNN..? I feel, it might not be required.can we
> maintain state wide..Please let me know, If I am wrong..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-7452) Can we skip getCorruptFiles() call for standby NameNode..?
[
https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144171#comment-15144171
]
Vinayakumar B commented on HDFS-7452:
-
[~brahmareddy], I think you can exclude the Logging for standbyexception (or
make debug) in {{FSNamesystem#getCorruptFiles()}}.
> Can we skip getCorruptFiles() call for standby NameNode..?
> --
>
> Key: HDFS-7452
> URL: https://issues.apache.org/jira/browse/HDFS-7452
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Brahma Reddy Battula
>Assignee: Brahma Reddy Battula
>Priority: Trivial
>
> Seen following warns logs from StandBy Namenode logs ..
> {noformat}
> 2014-11-27 17:50:32,497 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:42,557 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:52,617 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,117 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:02,678 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:12,738 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:22,798 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,119 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> {noformat}
> do we need to call for SNN..? I feel, it might not be required.can we
> maintain state wide..Please let me know, If I am wrong..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-7452) Can we skip getCorruptFiles() call for standby NameNode..?
[
https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534386#comment-14534386
]
Brahma Reddy Battula commented on HDFS-7452:
Thanks [~qwertymaniac] taking a look into this issue.. Yes, this jira is for
eliminate this spam..Let me know your thoughts on this..
> Can we skip getCorruptFiles() call for standby NameNode..?
> --
>
> Key: HDFS-7452
> URL: https://issues.apache.org/jira/browse/HDFS-7452
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Brahma Reddy Battula
>Assignee: Brahma Reddy Battula
>Priority: Trivial
>
> Seen following warns logs from StandBy Namenode logs ..
> {noformat}
> 2014-11-27 17:50:32,497 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:42,557 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:52,617 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,117 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:02,678 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:12,738 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:22,798 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,119 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> {noformat}
> do we need to call for SNN..? I feel, it might not be required.can we
> maintain state wide..Please let me know, If I am wrong..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-7452) Can we skip getCorruptFiles() call for standby NameNode..?
[
https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484575#comment-14484575
]
Harsh J commented on HDFS-7452:
---
IIUC, the Web UI of SBN tries to load up corrupt/missing block file info from
its local self, which also causes this log spam. We could eliminate that to
address this?
> Can we skip getCorruptFiles() call for standby NameNode..?
> --
>
> Key: HDFS-7452
> URL: https://issues.apache.org/jira/browse/HDFS-7452
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Brahma Reddy Battula
>Assignee: Brahma Reddy Battula
>Priority: Trivial
>
> Seen following warns logs from StandBy Namenode logs ..
> {noformat}
> 2014-11-27 17:50:32,497 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:42,557 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:52,617 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,117 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:02,678 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:12,738 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:22,798 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,119 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> {noformat}
> do we need to call for SNN..? I feel, it might not be required.can we
> maintain state wide..Please let me know, If I am wrong..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-7452) Can we skip getCorruptFiles() call for standby NameNode..?
[
https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238030#comment-14238030
]
Brahma Reddy Battula commented on HDFS-7452:
Hi [~vinayrpet]
Thanks for taking look into this issue..
{quote}
there cannot be any failover done as Client is connected to only one namenode
and tries to read the list.
{quote}
can't we skip this call to Standbynamenode..? Like Client directly connect to
Active Namenode and get the list..what do you say..?
> Can we skip getCorruptFiles() call for standby NameNode..?
> --
>
> Key: HDFS-7452
> URL: https://issues.apache.org/jira/browse/HDFS-7452
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Brahma Reddy Battula
>Assignee: Brahma Reddy Battula
>Priority: Trivial
>
> Seen following warns logs from StandBy Namenode logs ..
> {noformat}
> 2014-11-27 17:50:32,497 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:42,557 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:52,617 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,117 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:02,678 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:12,738 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:22,798 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,119 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> {noformat}
> do we need to call for SNN..? I feel, it might not be required.can we
> maintain state wide..Please let me know, If I am wrong..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-7452) Can we skip getCorruptFiles() call for standby NameNode..?
[
https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228077#comment-14228077
]
Vinayakumar B commented on HDFS-7452:
-
Hi [~brahmareddy], above code is used for collecting list of Corrupted files
via metrics either through JMX client or using UI [
http::///jmx ]. In these cases, there cannot be any failover
done as Client is connected to only one namenode and tries to read the list.
> Can we skip getCorruptFiles() call for standby NameNode..?
> --
>
> Key: HDFS-7452
> URL: https://issues.apache.org/jira/browse/HDFS-7452
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Brahma Reddy Battula
>Assignee: Brahma Reddy Battula
>
> Seen following warns logs from StandBy Namenode logs ..
> {noformat}
> 2014-11-27 17:50:32,497 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:42,557 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:52,617 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,117 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:02,678 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:12,738 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:22,798 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,119 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> {noformat}
> do we need to call for SNN..? I feel, it might not be required.can we
> maintain state wide..Please let me know, If I am wrong..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HDFS-7452) Can we skip getCorruptFiles() call for standby NameNode..?
[
https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227423#comment-14227423
]
Brahma Reddy Battula commented on HDFS-7452:
{code}
public String getCorruptFiles()
{
List list = new ArrayList();
try
{
Collection corruptFileBlocks = listCorruptFileBlocks("/", null);
int corruptFileCount = corruptFileBlocks.size();
if (corruptFileCount != 0)
for (CorruptFileBlockInfo c : corruptFileBlocks)
list.add(c.toString());
}
catch (IOException e)
{
LOG.warn(new StringBuilder().append("Get corrupt file blocks returned
error: ").append(e.getMessage()).toString());
}
return JSON.toString(list);
}
{code}
want to add inActiveState() in above code..
> Can we skip getCorruptFiles() call for standby NameNode..?
> --
>
> Key: HDFS-7452
> URL: https://issues.apache.org/jira/browse/HDFS-7452
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Brahma Reddy Battula
>Assignee: Brahma Reddy Battula
>
> Seen following warns logs from StandBy Namenode logs ..
> {noformat}
> 2014-11-27 17:50:32,497 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:42,557 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:50:52,617 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:00,117 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:02,678 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:12,738 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:22,798 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,058 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> 2014-11-27 17:51:30,119 | WARN | 512264920@qtp-429668078-606 | Get corrupt
> file blocks returned error: Operation category READ is not supported in state
> standby |
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getCorruptFiles(FSNamesystem.java:6916)
> {noformat}
> do we need to call for SNN..? I feel, it might not be required.can we
> maintain state wide..Please let me know, If I am wrong..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
