toggle quoted messageShow quoted text
I've reproduced the behavior on a CF v228 installation: it's happening
because the app-version on CC's app model is changing on the scale. I've
filed a bug with the CAPI team about it athttps://www.pivotaltracker.com/story/show/112251451
Fortunately, this seems to happen only on the first scale-up or scale-down
after the upgrade to CF v228, and subsequent scales leave the remaining
desired instances undisturbed. One possible reason that this is happening
may be that a new 'ports' field is getting back-filled on the app when it's
altered with the new desired instance count, and that change to the 'ports'
field triggers a new internal version of the app to be generated and
submitted to the runtime backend. In any case, the relevant teams will
investigate the cause and possible remediations for the regression.
On Fri, Jan 22, 2016 at 10:51 AM, Eric Malm <emalm(a)pivotal.io> wrote:
Thanks for the report. That does sound disturbing, as scale-up and
scale-down operations on an app should not disrupt running instances that
are still desired. We'll have a pair from the CAPI or Diego teams take a
look at this as soon as possible.
Eric, CF Runtime Diego PM
On Fri, Jan 22, 2016 at 9:06 AM, Marco Nicosia <mnicosia(a)pivotal.io>
Good morning from wet SF,
I sat down and noticed something odd in last night's scrollback. This
happens to be PWS (cf 228, diego 0.1446.0, stemcell 3147) but it's a
general CF question:
$ cf app clickpoint
[...] state since cpu memory disk
#0 running 2016-01-19 07:21:10 PM 0.0% 78.9M of 128M 50.8M of
$ cf scale clickpoint -i 5
Scaling app clickpoint in org moragasystems / space development...
$ cf app clickpoint
state since cpu memory disk
#0 running 2016-01-21 03:57:48 PM 0.0% 37.4M of 128M 24.2M of
#1 running 2016-01-21 03:57:48 PM 0.0% 0 of 128M 0 of 1G
#2 running 2016-01-21 03:57:48 PM 0.0% 37.4M of 128M 24.2M of
#3 running 2016-01-21 03:57:49 PM 0.0% 39.3M of 128M 24.2M of
#4 running 2016-01-21 03:57:48 PM 0.0% 0 of 128M 0 of 1G
Hey. What happened to my container running since the 19th? It's not a
serious issue, but it seems like adding instances shouldn't disturb running
I looked at
https://docs.cloudfoundry.org/devguide/deploy-apps/cf-scale.html but I
didn't see what the expected behavior should be.
Pivotal Software, Inc.