Re: cf restage and downtime

Dieu Cao <dcao@...>

Hi Peter,

Actually `cf restage` does cause down time. It will stop existing
instances, stage the new app bits with the buildpack, and start new
It's possible that your app may start quickly enough that you aren't seeing
down time.
It's recommended, that for now, you should use a blue-green deployment
strategy to ensure there is no down time to your users.
If you just need your app to pick up environment variables that aren't
required during staging, you could also just restart your app instead of
restaging with each change.


On Fri, Jul 3, 2015 at 9:17 AM, Peter Dotchev <dotchev(a)> wrote:


We use some user-provided services to provide some configurations to our
Sometime we need to update the configurations but without downtime.
So we update these configs using cf update-user-provided-service command
and then we have to restage bound apps.
I have noticed that cf restage causes no downtime as it first starts the
new instances and only then stops the old ones.
This is ok for us, but I could not find any documentation of this
behaviour. Can we rely on this to stay like that in the future or would it
be better to use blue-green deployment (more manual work)?

Best regards,

cf-dev mailing list

Join { to automatically receive all group messages.