New Release of ecAudit

2019-08-01 Thread Per Otterström
We are pleased to announce the release of ecAudit 2.1.0. The ecAudit plug-in enhance Cassandra 3.x with audit logging functionality. In this release we've added support for a high-performance logging backend based on Chronicle as well as added new logging parameters and configuration options. T

Re: Repair failed and crash the node, how to bring it back?

2019-08-01 Thread Martin Xue
Thanks ASAD, I will look more into it. Regards Martin On Thu, Aug 1, 2019 at 11:40 PM ZAIDI, ASAD A wrote: > I don’t think anyone can predict with certainty if instance won’t crash > but there are good chances it will - unless you take remedial actions. > > If you are not doing subrange repair,

Re: Repair failed and crash the node, how to bring it back?

2019-08-01 Thread Martin Xue
Hi Alex, Thanks, much appreciated. Regards Martin On Thu, Aug 1, 2019 at 3:34 PM Alexander Dejanovski wrote: > Hi Martin, > > apparently this is the bug you've been hit by on hints : > https://issues.apache.org/jira/browse/CASSANDRA-14080 > It was fixed in 3.0.17. > > You didn't provide the l

Logon trigger

2019-08-01 Thread Abdul Patel
Hi All, As per normal databases have logon trigger, do we have similar option in cassandra. Would like to implement ip restrictions in cassandra, or any other method?

RE: Repair failed and crash the node, how to bring it back?

2019-08-01 Thread ZAIDI, ASAD A
I don’t think anyone can predict with certainty if instance won’t crash but there are good chances it will - unless you take remedial actions. If you are not doing subrange repair, a lot of merkle tree data can potentially be scanned/streamed taking toll on memory resources – that , taking acco