Re: how does the loadbalancer know how much to bid for a node

From: Justin Riley <no email>
Date: Wed, 14 Nov 2012 11:50:11 -0500

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Bruce/Raj,

Yes, this is still the case. When you run the loadbalancer on a spot
cluster it will always launch spot instances when adding nodes using
the original spot bid used to create the initial cluster. In the
future we should probably allow overriding the spot bid via the
"loadbalance" command...

~Justin


On 10/31/2012 01:15 PM, Rajat Banerjee wrote:
> ---------- Forwarded message ----------
>
> From: Bruce Hoff <bruce.hoff_at_sagebase.org
> <mailto:bruce.hoff_at_sagebase.org>> To: starcluster_at_mit.edu
> <mailto:starcluster_at_mit.edu> Cc: Date: Tue, 30 Oct 2012 09:46:11
> -0700 Subject: [StarCluster] how does the loadbalancer know how
> much to bid for a node Hi: When using spot instances and the load
> balancer, how the load balancer decide how much to bid when adding
> a new node? Thanks, Bruce Hoff Sage Bionetworks
>
>
> Hi Bruce, The loadbalancer uses cluster.add_nodes to add new nodes.
> I remember from testing that it used to use the same price that you
> set for bids when the cluster was created. Things have changed, but
> it looks like (in cluster.py) add_nodes still uses the bid price
> that you specified when creating the cluster.
>
> The source is in:
> https://github.com/jtriley/StarCluster/blob/develop/starcluster/cluster.py
>
>
, search for add_nodes
>
> Best, Rajat Banerjee
>
>
> _______________________________________________ StarCluster mailing
> list StarCluster_at_mit.edu <mailto:StarCluster_at_mit.edu>
> http://mailman.mit.edu/mailman/listinfo/starcluster
>
>
>
>
> _______________________________________________ StarCluster mailing
> list StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCjy8MACgkQ4llAkMfDcrmiqwCffWLBzyU3KcZkofCP+V4jmb7a
d58AnjPtcDX8J44bdFWY+n3R7qdPNGfj
=burC
-----END PGP SIGNATURE-----
Received on Wed Nov 14 2012 - 11:50:15 EST