openstack team mailing list archive

[Diego Parrilla Santamaría <diego.parrilla.santamaria@xxxxxxxxx>]

Hi gtt,

what does it mean for you 'lots of instance simultaneously'? 100, 1000,
10000, more?

We have launched >100 (but less than <1000) simultaneously without any
issue. Rabbit running in a multicore with several gigs of RAM with out of
the box configuration.

Cheers
Diego
 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parrilla@xxxxxxxxxxxx** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*



On Tue, Feb 19, 2013 at 9:35 AM, gtt116 <gtt116@xxxxxxx> wrote:

>  Hi all,
>
> When create lots of instance simultaneously, there will be lots of
> instance in ERROR state. And most of them are caused by network rpc request
> timeout. This result is not so graceful.
>
> I think it will be better if scheduler keep a queue of creating request.
> when he find all the hosts are busy enough(compute_node.current_workload
> reach some value), stop cast the request to host temporarily, until he
> found some host free enough. In this way, we can make sure booting lots of
> instances simultaneously results in active instances rather than lots of
> ERROR instance. but will cause a small weak point, if the top value of
> current_workload small enough, create instance processing will be slow.
>
> Do you have another quick fix?
>
> Thanks,
>
> --
> best regards,
> gtt
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>