You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/02/03 16:56:40 UTC
[jira] [Commented] (FLINK-3161) Externalize cluster start-up and
tear-down when available
[ https://issues.apache.org/jira/browse/FLINK-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130596#comment-15130596 ]
ASF GitHub Bot commented on FLINK-3161:
---------------------------------------
Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/1523#issuecomment-179308417
Hi @greghogan, thanks for the update!
Looks good to merge.
> 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)