Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Wed, 3 Feb 2016 23:30:40 +0000 (UTC)
From: "Fabian Hueske (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12921106.1449853683000.293618.1454542240049@Atlassian.JIRA>
In-Reply-To: <JIRA.12921106.1449853683000@Atlassian.JIRA>
References: <JIRA.12921106.1449853683000@Atlassian.JIRA>
 <JIRA.12921106.1449853683251@arcas>
Subject: [jira] [Closed] (FLINK-3161) Externalize cluster start-up and
 tear-down when available
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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)