Re: Clean shutdown when scaling down a job


Mike Youngstrom
 

Thanks, for the record I'm on release 2889.

Mike

On Wed, Jul 15, 2015 at 1:48 AM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

You should not have to specify resource pool sizes (in fact we are
deprecating this feature soon). I'll look into this tomorrow morning.

Sent from my iPhone

On Jul 14, 2015, at 9:56 PM, Mike Youngstrom <youngm(a)gmail.com> wrote:

Ah, we aren't specifying resource pool sizes. Letting bosh manage that.

Mike

On Tue, Jul 14, 2015 at 10:52 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Hi,
Did you decrease resource pool size too ?

Thanks

On Wed, Jul 15, 2015 at 1:27 PM, Mike Youngstrom <youngm(a)gmail.com>
wrote:

We recently scaled down a bunch of our DEAs. We did this by simply
reducing the instances in our job and deploying. When doing this it didn't
appear that bosh shut down these extra VMs allowing them to evacuate prior
to being deleted. We got messages like:

"Started deleting unneeded instances"

Is this expected behaviour?

Mike

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

Join cf-bosh@lists.cloudfoundry.org to automatically receive all group messages.