[ 
https://issues.apache.org/jira/browse/HBASE-18045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564450#comment-17564450
 ] 

Hudson commented on HBASE-18045:
--------------------------------

Results for branch master
        [build #629 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/629/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/629/General_20Nightly_20Build_20Report/]






(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/629/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/629/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Add ' -o ConnectTimeout=10' to the ssh command we use in ITBLL chaos monkeys
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-18045
>                 URL: https://issues.apache.org/jira/browse/HBASE-18045
>             Project: HBase
>          Issue Type: Improvement
>          Components: integration tests
>            Reporter: Michael Stack
>            Assignee: Narasimha Sharma
>            Priority: Trivial
>             Fix For: 3.0.0-alpha-4
>
>
> Monkeys hang on me in long running tests. I've not spent too much time on it 
> since it rare enough but I just went through a spate of them. When monkey 
> kill ssh hangs, all killing stops which can give a false sense of victory 
> when you wake up in the morning and your job 'passed'. I also see monkeys 
> kill all servers in a cluster and fail to bring them back which causes job 
> fail as no one is serving data. The latter may actually be another issue but 
> for the former, I've  had some success adding  -o ConnectTimeout=10 as an 
> option on ssh. You can do it easily enough via config but this issue is to 
> suggest that we add it in code.
> Here is how you add it via config if interested:
> <property >
> <name>hbase.it.clustermanager.ssh.opts</name>
> <value> -o ConnectTimeout=10 </value>
> </property >



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to