[
https://issues.apache.org/jira/browse/OOZIE-3570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998739#comment-16998739
]
Junfan Zhang commented on OOZIE-3570:
-------------------------------------
[~asalamon74]. According to this
[question|https://stackoverflow.com/questions/10237563/set-ssh-connection-timeout],
SSH connectTimeout option is only valid in some scenarios. What I understand
is that when the remote host is hung, this option is invalid.
We have encountered this problem in a production environment. I then added a
timeout command prefix to solve it and avoid running out of system threads.
Maybe it's not a good solution.
> SSH Action execution command should add the mechanism of timeout
> ----------------------------------------------------------------
>
> Key: OOZIE-3570
> URL: https://issues.apache.org/jira/browse/OOZIE-3570
> Project: Oozie
> Issue Type: Bug
> Reporter: Junfan Zhang
> Assignee: Junfan Zhang
> Priority: Major
>
> *Phenomenon*
> Currently, In SSH action, When the remote machine is hung, execution command
> will waiting. This will cause the number of Oozie threads to be occupied,
> which will cause delays in scheduling other tasks.
> *Solution*
> SSH Action execution command should add timeout prefix. But the {{ssh -o
> ConnectTimeout=20}} is invalid
> {code:java}
> timeout 20s ssh xxxxxxxxxx
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
