[
https://issues.apache.org/jira/browse/FLINK-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102467#comment-15102467
]
Greg Hogan commented on FLINK-3161:
-----------------------------------
Using {{pdsh}}, I removed {{bc}} from one of my TaskManager instances and the
error is reported as follows:
{noformat}
[ec2-user@ip-10-0-36-56 flink-1.0-SNAPSHOT]$ ./bin/start-cluster.sh
Starting cluster.
Starting jobmanager daemon on host ip-10-0-36-56.
10.0.36.56: [ERROR] Program 'bc' not found. Please install bc or define
'taskmanager.memory.size' instead of 'taskmanager.memory.fraction' in
flink-conf.yaml
pdsh@ip-10-0-36-56: 10.0.36.56: ssh exited with exit code 1
10.0.38.130: Starting taskmanager daemon on host ip-10-0-38-130.
10.0.41.51: Starting taskmanager daemon on host ip-10-0-41-51.
10.0.47.133: Starting taskmanager daemon on host ip-10-0-47-133.
{noformat}
> 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)
