Restart req after you remove/add node to an IS cluster

,
1

Restart req after you remove/add node to an IS cluster

Hello,

Need you input on production migration. Our requirement is that before we put any code we have to take a node out of cluster, install the code base and put it back in the cluster.
In earlier versions to remove a node from a cluster, there was no need of a restart of the IS. But now (we are using 7.1.2) a restart is required (uggh !!).

So I am looking for workarounds (may be I don’t have to remove the node from cluster).

There are 3 entry points to any service in our implementation

  1. http port
  2. triggers
  3. schedulers.

I can take care of http port and triggers by disabling them but I cannot disable the schedulers as they run in a clustered environment (So if I disable on one they will get disabled on all nodes).

Has anyone faced this situation and have a workaround?

2

I thought it makes no difference either if the removed node has to be restarted or not since the remaining nodes are still processing requests. Then you do whatever you have to with the removed node after restarts.