aboutsummaryrefslogtreecommitdiff
path: root/sbin
diff options
context:
space:
mode:
authorNicholas Chammas <nicholas.chammas@gmail.com>2015-03-07 12:33:41 +0000
committerSean Owen <sowen@cloudera.com>2015-03-07 12:33:41 +0000
commit2646794ffb2970618087e2e964d9f4c953e17e6a (patch)
treecc9cab091a0b05a6e453237c850c51e55ef51f1c /sbin
parent48a723c98684c5bb3d185cada4888cae952791bd (diff)
downloadspark-2646794ffb2970618087e2e964d9f4c953e17e6a.tar.gz
spark-2646794ffb2970618087e2e964d9f4c953e17e6a.tar.bz2
spark-2646794ffb2970618087e2e964d9f4c953e17e6a.zip
[EC2] Reorder print statements on termination
The PR reorders some print statements slightly on cluster termination so that they read better. For example, from this: ``` Are you sure you want to destroy the cluster spark-cluster-test? The following instances will be terminated: Searching for existing cluster spark-cluster-test in region us-west-2... Found 1 master(s), 2 slaves > ... ALL DATA ON ALL NODES WILL BE LOST!! Destroy cluster spark-cluster-test (y/N): ``` To this: ``` Searching for existing cluster spark-cluster-test in region us-west-2... Found 1 master(s), 2 slaves The following instances will be terminated: > ... ALL DATA ON ALL NODES WILL BE LOST!! Are you sure you want to destroy the cluster spark-cluster-test? (y/N) ``` Author: Nicholas Chammas <nicholas.chammas@gmail.com> Closes #4932 from nchammas/termination-print-order and squashes the following commits: c23711d [Nicholas Chammas] reorder prints on termination
Diffstat (limited to 'sbin')
0 files changed, 0 insertions, 0 deletions