We are considering using cluster management-only for shared configuration for
our next project. Currently, we have 12 ATS nodes all acting independently.
The next project will have double that number of nodes, and I was trying to get
away from having to deploy configuration changes per node.
I was also considering adding in functionality such that I could send a PURGE
command to one node, and have that command be replicated across all of the
nodes in the cluster, as opposed to having to send a PURGE command to each of
the nodes individually.
Based on Bryan’s proposal, we are revisiting the idea of clustered ATS. I am
just giving feedback that we are considering using it.
If anyone has ideas on how to manage configs across this many nodes, or about
how to trigger PURGE and similar cache commands to all nodes, please let me
know.
Thanks,
Steven
On 8/19/16, 2:08 PM, "Bryan Call" <bc...@apache.org> wrote:
There are a few features we are looking to remove in the ATS 7.0.0 release.
If you are using these features and require them, please respond to this
email. We also need to have people that are willing to invest time and fix
some of the bugs for these features. Your feedback is very important!
There are a number of bugs filed against clustering. There are
alternatives to using clustering, such as parent selection and the CARP plugin
that Yahoo is open sourcing. If we are going to keep clustering supporting we
would need someone that is willing to work on the bugs.
The proposal is to remove the configurations options for clustering and
remove the code for it.
-Bryan
