Stackato 2.10.x Router does not reconnect to doozer when it loses connection

Posted by lorned on 2013-09-17 15:50
OS: All / Any | Product: Stackato | tags: 2.10.4 2.10.6 doozer patch reconnect router stackato
Question: 

I've noticed that when my routers can't connect to the primary/doozer node for more than a few seconds, they give up and enter a 'starting' state. Is there anything that can be done about this?

Answer: 

We've generated a patch that adds some reconnection logic to the router role. The patch is available for both 2.10.4 and 2.10.6, with instructions to follow.

###2.10.4
You can download this patch from http://get.stackato.com/patch/2.10/stackato-2.10.4-router-reconnect.sh. You'll want to upload it to every node in your cluster running the router role (Including the router on your primary node, for consistency). After you've uploaded the patch, open a terminal session to each of your nodes and execute 'sh stackato-2.10.4-router-reconnect.sh'. Once the patch has been applied you'll need to restart your router role via 'kato restart router'. If you've only got one router in your cluster this will interrupt access to/within your cluster for a few moments. If you have redundant routers this should not be a problem. NOTE: This patch touches the same file as http://community.activestate.com/node/9948, which must be installed first.

###2.10.6
This patch is available via kato patch. You will need to open a terminal session to a node in your cluster and execute 'kato patch update' to download the latest manifest. Once you've done this you can install the patch via 'kato patch install'. This will deploy and install the patch to every node in your cluster, and restart the 'router' role where appropriate. Note that if you have one router in your cluster this will interrupt access to/within your cluster for a few moments while the role restarts.