Re: Changing iinstance type for everynode in the cluster
This archive was generated by
Thanks for your help.
Unfortunately this is not an option for me since it doesnt scale. I am
deploying 300 and 3000 nodes cluster, the 30 one is just for testing.
6301 Ivy Lane, Greenbelt, MD 20770
On Thu, Sep 18, 2014 at 1:17 AM, Rayson Ho <raysonlogin_at_gmail.com> wrote:
> I've never tried something like this myself, but I believe it would work
> if you stop the EBS cluster (*NOT* terminate), and then change the instance
> type from the EC2 management Console, and then restart the cluster, then
> StarCluster would happily reconfig the cluster for you:
> Just a reboot won't do it, as the private IP address changes when you
> change the instance type, and /etc/hosts would need to be changed again.
> (Test with a 2-node t1.micro cluster and change the type to t2.micro
> before doing anything experimental on a real production cluster.)
> Open Grid Scheduler - The Official Open Source Grid Engine
> On Wed, Sep 17, 2014 at 10:53 PM, Ramon Ramirez-Linan <rlinan_at_navteca.com>
>> Is there a way of changing the instance type for the entire cluster after
>> it has already be launched?
>> I want to launch a 30 nodes cluster with a cheaper instance type to
>> ingest data on each node's volume. Each node has a 1TB EBS attached and
>> there is no need to share data between nodes (no nfs or anything). Then
>> once the data is injected on each node I want to be able to change the
>> cluster instances to a more expensive one (more CPU/RAM)
>> Will cluster reboot let me do that?
>> Thanks in advance
>> [image: logo]
>> Ramon Ramirez-Linan
>> C: 301.789.9139
>> O: 202.505.1553
>> *www.navteca.com <http://www.navteca.com/>*
>> 6301 Ivy Lane, Greenbelt, MD 20770
>> Suite 700
>> [image: script]
>> [image: https://s3.amazonaws.com/www.navteca.com/img/certified.png]
>> StarCluster mailing list
Received on Thu Sep 18 2014 - 10:04:14 EDT