[jira] [Commented] (HDFS-12791) NameNode Fsck http Connection can timeout for directories with multiple levels
[
https://issues.apache.org/jira/browse/HDFS-12791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261474#comment-16261474
]
Chen Liang commented on HDFS-12791:
---
[~zhz] Sorry I should have updated it. I believe it should be 3.1.0, I have
updated the JIRA. ([~msingh] Please correct me if I'm wrong).
> NameNode Fsck http Connection can timeout for directories with multiple levels
> --
>
> Key: HDFS-12791
> URL: https://issues.apache.org/jira/browse/HDFS-12791
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: tools
>Reporter: Mukul Kumar Singh
>Assignee: Mukul Kumar Singh
> Fix For: 3.1.0
>
> Attachments: HDFS-12791.001.patch
>
>
> Currently the http connections are flushed for every 100 files, however if
> there are multiple levels of directories in the namespace then flushing will
> be postponed till multiple directories levels have been traversed. This
> connection timeout can be avoided if both files and directories are
> considered for the flushing query.
> {code}
> if (showprogress && (replRes.totalFiles + ecRes.totalFiles) % 100 == 0) {
> out.println();
> out.flush();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12791) NameNode Fsck http Connection can timeout for directories with multiple levels
[
https://issues.apache.org/jira/browse/HDFS-12791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261456#comment-16261456
]
Zhe Zhang commented on HDFS-12791:
--
Thanks for the work [~msingh] and [~vagarychen]. What should be the fix version?
> NameNode Fsck http Connection can timeout for directories with multiple levels
> --
>
> Key: HDFS-12791
> URL: https://issues.apache.org/jira/browse/HDFS-12791
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: tools
>Reporter: Mukul Kumar Singh
>Assignee: Mukul Kumar Singh
> Attachments: HDFS-12791.001.patch
>
>
> Currently the http connections are flushed for every 100 files, however if
> there are multiple levels of directories in the namespace then flushing will
> be postponed till multiple directories levels have been traversed. This
> connection timeout can be avoided if both files and directories are
> considered for the flushing query.
> {code}
> if (showprogress && (replRes.totalFiles + ecRes.totalFiles) % 100 == 0) {
> out.println();
> out.flush();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12791) NameNode Fsck http Connection can timeout for directories with multiple levels
[
https://issues.apache.org/jira/browse/HDFS-12791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16246971#comment-16246971
]
Hudson commented on HDFS-12791:
---
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13217 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13217/])
HDFS-12791. NameNode Fsck http Connection can timeout for directories (cliang:
rev 10a1f557e775e7a55958b106dd10021ac7394843)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NamenodeFsck.java
> NameNode Fsck http Connection can timeout for directories with multiple levels
> --
>
> Key: HDFS-12791
> URL: https://issues.apache.org/jira/browse/HDFS-12791
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: tools
>Reporter: Mukul Kumar Singh
>Assignee: Mukul Kumar Singh
> Attachments: HDFS-12791.001.patch
>
>
> Currently the http connections are flushed for every 100 files, however if
> there are multiple levels of directories in the namespace then flushing will
> be postponed till multiple directories levels have been traversed. This
> connection timeout can be avoided if both files and directories are
> considered for the flushing query.
> {code}
> if (showprogress && (replRes.totalFiles + ecRes.totalFiles) % 100 == 0) {
> out.println();
> out.flush();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12791) NameNode Fsck http Connection can timeout for directories with multiple levels
[
https://issues.apache.org/jira/browse/HDFS-12791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16246948#comment-16246948
]
Chen Liang commented on HDFS-12791:
---
Committed to trunk, thanks Mukul for the contribution!
> NameNode Fsck http Connection can timeout for directories with multiple levels
> --
>
> Key: HDFS-12791
> URL: https://issues.apache.org/jira/browse/HDFS-12791
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: tools
>Reporter: Mukul Kumar Singh
>Assignee: Mukul Kumar Singh
> Attachments: HDFS-12791.001.patch
>
>
> Currently the http connections are flushed for every 100 files, however if
> there are multiple levels of directories in the namespace then flushing will
> be postponed till multiple directories levels have been traversed. This
> connection timeout can be avoided if both files and directories are
> considered for the flushing query.
> {code}
> if (showprogress && (replRes.totalFiles + ecRes.totalFiles) % 100 == 0) {
> out.println();
> out.flush();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12791) NameNode Fsck http Connection can timeout for directories with multiple levels
[
https://issues.apache.org/jira/browse/HDFS-12791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16246944#comment-16246944
]
Chen Liang commented on HDFS-12791:
---
Thanks for working on this [~msingh]! +1 on v001 patch, the failed tests all
passed in my local run. Will commit this shortly.
> NameNode Fsck http Connection can timeout for directories with multiple levels
> --
>
> Key: HDFS-12791
> URL: https://issues.apache.org/jira/browse/HDFS-12791
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: tools
>Reporter: Mukul Kumar Singh
>Assignee: Mukul Kumar Singh
> Attachments: HDFS-12791.001.patch
>
>
> Currently the http connections are flushed for every 100 files, however if
> there are multiple levels of directories in the namespace then flushing will
> be postponed till multiple directories levels have been traversed. This
> connection timeout can be avoided if both files and directories are
> considered for the flushing query.
> {code}
> if (showprogress && (replRes.totalFiles + ecRes.totalFiles) % 100 == 0) {
> out.println();
> out.flush();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-12791) NameNode Fsck http Connection can timeout for directories with multiple levels
[
https://issues.apache.org/jira/browse/HDFS-12791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16244523#comment-16244523
]
Hadoop QA commented on HDFS-12791:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
21s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {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:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 18m
40s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
6s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
44s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
5s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
12m 36s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
7s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
2s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
11s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
11s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
43s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
12m 39s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
59s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}112m 1s{color}
| {color:red} hadoop-hdfs in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
28s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}170m 32s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hdfs.TestDFSStripedOutputStreamWithFailure |
| | hadoop.hdfs.TestReadStripedFileWithMissingBlocks |
| | hadoop.hdfs.TestDFSStripedOutputStreamWithFailure060 |
| | hadoop.hdfs.qjournal.server.TestJournalNodeSync |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:5b98639 |
| JIRA Issue | HDFS-12791 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12896674/HDFS-12791.001.patch |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit shadedclient findbugs checkstyle |
| uname | Linux 5ae343e25933 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | trunk / e4c220e |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_131 |
| findbugs | v3.1.0-RC1 |
| unit |
https://builds.apache.org/job/PreCommit-HDFS-Build/22005/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HDFS-Build/22005/testReport/ |
|
