Correct, Opscenter can monitor 2.0.10 and later clusters/nodes. It just can't provision them.
On Thu, Mar 12, 2015 at 1:16 PM, Ajay <ajay.ga...@gmail.com> wrote: > Thanks Nick. > > Does it mean that only adding a new node with 2.0.10 or later is a > problem?. If a new node added manually can be monitored from Opscenter? > > Thanks > Ajay > On 12-Mar-2015 10:19 pm, "Nick Bailey" <n...@datastax.com> wrote: > >> There isn't an OpsCenter specific mailing list no. >> >> To answer your question, the reason OpsCenter provisioning doesn't >> support 2.0.10 and 2.0.11 is due to >> https://issues.apache.org/jira/browse/CASSANDRA-8072. >> >> That bug unfortunately prevents OpsCenter provisioning from working >> correctly, but isn't serious outside of provisioning. OpsCenter may be able >> to come up with a workaround but at the moment those versions are >> unsupported. Sorry for inconvenience. >> >> -Nick >> >> On Thu, Mar 12, 2015 at 9:18 AM, Ajay <ajay.ga...@gmail.com> wrote: >> >>> Is there a separate forum for Opscenter? >>> >>> Thanks >>> Ajay >>> On 11-Mar-2015 4:16 pm, "Ajay" <ajay.ga...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> While adding a Cassandra node using OpsCenter (which is recommended), >>>> the versions of Cassandra (Datastax community edition) shows only 2.0.9 and >>>> not later versions in 2.0.x. Is there a reason behind it? 2.0.9 is >>>> recommended than 2.0.11? >>>> >>>> Thanks >>>> Ajay >>>> >>> >>
