[jira] [Commented] (FLINK-3161) Externalize cluster start-up and tear-down when available

["Stephan Ewen (JIRA)" <ji...@apache.org>]

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

Stephan Ewen commented on FLINK-3161:
-------------------------------------

I think one reason we did not originally do that is that errors during start up will not report back as easily when the SSH command runs in the background.
If there is a way to get good error messages when the remote command fails, there is really no reason to not do this.

Another option would be to all a flag that runs the script with parallel SSH connections.

> Externalize cluster start-up and tear-down when available
> ---------------------------------------------------------
>
>                 Key: FLINK-3161
>                 URL: https://issues.apache.org/jira/browse/FLINK-3161
>             Project: Flink
>          Issue Type: Improvement
>          Components: Start-Stop Scripts
>    Affects Versions: 1.0.0
>            Reporter: Greg Hogan
>            Assignee: Greg Hogan
>            Priority: Minor
>
> I have been using pdsh, pdcp, and rpdcp to both distribute compiled Flink and to start and stop the TaskManagers. The current shell script initializes TaskManagers one-at-a-time. This is trivial to background but would be unthrottled.
> From pdsh's archived homepage: "uses a sliding window of threads to execute remote commands, conserving socket resources while allowing some connections to timeout if needed".
> What other tools could be supported when available?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)