You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2016/02/04 00:30:40 UTC
[jira] [Closed] (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:all-tabpanel ]
Fabian Hueske closed FLINK-3161.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
Fixed with f7d1911518da4bd1b4f742e5b4525e7867665f51
> 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
> Fix For: 1.0.0
>
>
> 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)