Re: Do not use Cassandra 3.11.0+ or Cassandra 3.0.12+

2017-09-12 Thread Jeff Jirsa
On the user side: 3.11.0 or 3.0.14 is probably what you want to use for new clusters as long as you can avoid calling the getTombstoneRatio() mbean with your metrics gathering tools. On Tue, Sep 12, 2017 at 8:35 AM, Sandeep S wrote: > Hi, > > What is the current stable version? > > Sandeep. >

Re: Do not use Cassandra 3.11.0+ or Cassandra 3.0.12+

2017-09-12 Thread Chris Lohfink
Last Ive seen of it OpsCenter does not collect this metric. I don't think any monitoring tools do. Chris > On Sep 11, 2017, at 4:06 PM, CPC wrote: > > Hi, > > Is this bug fixed in dse 5.1.3? As I understand calling jmx getTombStoneRatio > trigers that bug. We are using opscenter as well and d

Re: Do not use Cassandra 3.11.0+ or Cassandra 3.0.12+

2017-09-12 Thread Sandeep S
Hi, What is the current stable version? Sandeep. On 11 September 2017 at 23:06, CPC wrote: > Hi, > > Is this bug fixed in dse 5.1.3? As I understand calling jmx > getTombStoneRatio > trigers that bug. We are using opscenter as well and do you have any idea > whether opscenter using/calling thi

Re: Do not use Cassandra 3.11.0+ or Cassandra 3.0.12+

2017-09-12 Thread CPC
Hi, Is this bug fixed in dse 5.1.3? As I understand calling jmx getTombStoneRatio trigers that bug. We are using opscenter as well and do you have any idea whether opscenter using/calling this method? Thanks On Aug 29, 2017 6:35 AM, "Jeff Jirsa" wrote: > I shouldn't actually say I don't think