> On 5 Jan 2016, at 00:56, Manoj Samel <manojsamelt...@gmail.com> wrote: > > Hi, > > Slider 0.80 with secured cluster. > > Say I have cluster with 1 component running. I do upgrade and add second > component. After running the upgrade command, when I do "slider list xxx > --containers" the first running component shows "awaiting heartbeat" for > like 2 minutes ... There is also pause in slider "Status" ping for this > container for same interval. > > Curious why does a existing container takes such long time to heartbeat to > AM when a new component is added ??? > > Thanks, > > Manoj
Again, this is because the AM kills itself. The agents have to wait for a new AM to come up, and then find its new registry binding for its new location —the same process it follows on any AM failure
