Re: cf scale command sequence
Siva Balan <mailsiva@...>
Thanks. What I am concerned about are the inflight transactions on the
container when it is being destroyed. What happens to them? If the routes
are removed from the GoRouter before the container is destroyed, I believe,
it has some lead time to process inflight transactions. But if the route is
removed after the container is destroyed, the probability of inflight
transactions getting killed is more. Also, I dont understand how it can
happen either way. The code path should do one or the other but not both.
toggle quoted message
Show quoted text
container when it is being destroyed. What happens to them? If the routes
are removed from the GoRouter before the container is destroyed, I believe,
it has some lead time to process inflight transactions. But if the route is
removed after the container is destroyed, the probability of inflight
transactions getting killed is more. Also, I dont understand how it can
happen either way. The code path should do one or the other but not both.
On Thu, May 5, 2016 at 2:16 PM, Michael Fraenkel <michael.fraenkel(a)gmail.com
wrote:
It is pretty much a race. It can happen either way. GoRouter will retry on
failed connects so if the route remains when the container is removed, the
next instance will be tried.
- Michael
On 5/5/16 3:34 PM, Siva Balan wrote:
When I issue a cf scale command to bring down the number of app instances
from, say 10 to 5, what is the sequence of events that take place to make
this happen? I am particularly interested to know if the containers are
removed before their routes are removed from the gorouter or is it the
other way round? This question if for both diego and DEA versions.
Thanks
Siva Balan
--
http://www.twitter.com/sivabalans