Forum OpenACS Q&A: Re: Issue with reachable method in 5.10.1 dynamic clustering setup

In my testing nodes have been inactive for an hour or more and not removed from this page or the DynamicClusterPeers parameter.

It is intentional to show on the cluster-admin page inactive cluster nodes to show their state, the last contact, etc. If these nodes would be deleted from the admin page, the administration would be much harder.

It would be possible to provide a display mode to omit these nodes from the listing. Such a mode might be useful, when there is a high number of cluster nodes (more than one page), but I am not sure if this is somewhere needed.

It would also be possible to distinguish between short network separations (short times of lost reachability) and final deletion (when one scales a cluster up and shrinks it down later, without any intention to re-include after a network separation these nodes). Maybe this is what you are looking for?

Yes, we will have scaling events that bring up dynamic nodes with new ips and then bring them down when load is decreased. This will lead to a large set of inactive hosts over time if the load increases/decreases multiple times a day or over a week.

We have some logic to clean up similar parameters ClusterPeerIP and ClusterAuthorizedIP for this type of situation but thought maybe the DynamicClusterPeers would be self-controlled within the core functionality.