Re: cf scale behavior is undocumented (and surprising)

Jesse T. Alford

Yeah, but do they do rolling restart or vertical scaling? I'm unaware of
any. A blue-green deploy to boost RAM is definitely an option, but it seems
like over kill, especially if you're already using a blue-green pattern to
maintain the ability to roll back a version (as now the scale change would
take up one of your "versions").

I don't actually know if the current CC API makes rolling scales possible
from the client side, plugin or no. Might the V3 API offer something around

On Wed, Jun 15, 2016, 5:03 AM Daniel Mikusa <dmikusa(a)> wrote:

On Tue, Jun 14, 2016 at 10:07 PM, Carlo Alberto Ferraris <
carlo.ferraris(a)> wrote:

there is no mention that vertical scaling requires a restart of all
application instances. At least in v220/dea_next cf scale -m and -k will
restart all instances.

I think it would be a good idea to have the documentation explicitly
state that vertical scaling will cause application downtime.

I was also wondering whether there is already a story about making all cf
scale operations not require a full restart (but rather a rolling restart,
ideally having new instances start before old ones are stopped) - this
looks to me something that shouldn't need to require a "manual" blue-green
Just an FYI, there are plugins that do automated blue-green deploys, such
as autopilot and cf-blue-green-deploy.


Join to automatically receive all group messages.