[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

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

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026142#comment-17026142 ] Wei-Chiu Chuang commented on HDFS-7175: --- Looks good to me +1. > Client-side SocketTimeoutException

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023275#comment-17023275 ] Stephen O'Donnell commented on HDFS-7175: - Yea, I ran it without the -showprogress switch, which

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023273#comment-17023273 ] Wei-Chiu Chuang commented on HDFS-7175: --- Makes sense to me [~sodonnell]. Have you verified the fsck

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

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

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022879#comment-17022879 ] Stephen O'Donnell commented on HDFS-7175: - This issue has been dormant for a long time, but as I

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022604#comment-17022604 ] Wei-Chiu Chuang commented on HDFS-7175: --- [~sodonnell] it looks to me HDFS-7175 wanted to do what

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14304666#comment-14304666 ] Akira AJISAKA commented on HDFS-7175: - Tried tcpdump with JDK8. The channel was quiet

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14304425#comment-14304425 ] Akira AJISAKA commented on HDFS-7175: - bq. I could see that the dots were sent out in

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14297190#comment-14297190 ] Subbu commented on HDFS-7175: - The problem that we face is that if we turn on showprogress,

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14297207#comment-14297207 ] Subbu commented on HDFS-7175: - I tried on jdk7. Note that the timeout happens only on large

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14297199#comment-14297199 ] Allen Wittenauer commented on HDFS-7175: I'm talking specifically about the null

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295782#comment-14295782 ] Allen Wittenauer commented on HDFS-7175: What are the chances this is a JDK7 vs.

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294591#comment-14294591 ] Hadoop QA commented on HDFS-7175: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294338#comment-14294338 ] Subbu commented on HDFS-7175: - I apologize for the delay in verification of this bug. I have

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294442#comment-14294442 ] Subbu commented on HDFS-7175: - One way to fix this may be to put out the . on the server even

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14209988#comment-14209988 ] Subbu commented on HDFS-7175: - The number 1 does not work in our large cluster. (Sorry for

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14209989#comment-14209989 ] Subbu commented on HDFS-7175: - Let me clarify that we see the same timeout issue by flushing

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14165434#comment-14165434 ] Allen Wittenauer commented on HDFS-7175: bq. could we at least considering making

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163240#comment-14163240 ] Vinayakumar B commented on HDFS-7175: - Below changes could serve the purpose mentioned

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163323#comment-14163323 ] Akira AJISAKA commented on HDFS-7175: - bq. elapsed time since the last flush adds a

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163498#comment-14163498 ] Hadoop QA commented on HDFS-7175: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14164137#comment-14164137 ] Allen Wittenauer commented on HDFS-7175: It'd be good to hear from LinkedIn to see

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14164290#comment-14164290 ] Bob Liu commented on HDFS-7175: --- I understand the complexity of adding the time based

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161786#comment-14161786 ] Akira AJISAKA commented on HDFS-7175: - Thanks [~mcvsubbu] for comment. [~aw], I'm

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162219#comment-14162219 ] Bob Liu commented on HDFS-7175: --- As a feature request, I am wondering if it's possible to

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162961#comment-14162961 ] Allen Wittenauer commented on HDFS-7175: bq. I would go back to pre- HDFS-2538

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161011#comment-14161011 ] Subbu commented on HDFS-7175: - I would go back to pre- HDFS-2538 behavior (i.e. flush every 100

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156224#comment-14156224 ] Akira AJISAKA commented on HDFS-7175: - bq. I'll test the patch in my environment. I've

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156227#comment-14156227 ] Hadoop QA commented on HDFS-7175: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14154546#comment-14154546 ] Akira AJISAKA commented on HDFS-7175: - Attached the patch to fix it by 3 (flushing an

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14154705#comment-14154705 ] Hadoop QA commented on HDFS-7175: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155970#comment-14155970 ] Mohammad Kamrul Islam commented on HDFS-7175: - Patch looks good to me. Can you

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14155999#comment-14155999 ] Akira AJISAKA commented on HDFS-7175: - These tests look unrelated to the patch. Several

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156017#comment-14156017 ] Hadoop QA commented on HDFS-7175: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (HDFS-7175) Client-side SocketTimeoutException during Fsck

[ https://issues.apache.org/jira/browse/HDFS-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156051#comment-14156051 ] Allen Wittenauer commented on HDFS-7175: Doing this every 100 is way too frequent.