Dinesh, here is the ticket
https://issues.apache.org/jira/browse/CASSANDRA-14647
On Thu, Aug 16, 2018 at 10:13 AM dinesh.jo...@yahoo.com.INVALID
wrote:
> Vitali,
>
> It doesn't look like there is an existing Jira. It would be helpful if you
> could create one with as much information as possible
Vitali,
It doesn't look like there is an existing Jira. It would be helpful if you
could create one with as much information as possible. Can you reduce this
issue to a short, repeatable set of steps that we can reproduce? That'll be
helpful to debug this problem.
Dinesh
On Wednesday, Aug
I've upgraded to 3.0.17 and the issue is still there, Is there a jira
ticket for that bug or should i create one?
On Wed, Jul 25, 2018 at 2:57 PM Vitali Dyachuk wrote:
> I'm using 3.0.15. I see that there is some fix for sstable metadata in
> 3.0.16 https://issues.apache.org/jira/browse/CASSAND
I'm using 3.0.15. I see that there is some fix for sstable metadata in
3.0.16 https://issues.apache.org/jira/browse/CASSANDRA-14217 - is that a
fix for "reading cardinalyti from statistics.db" ?
On Wed, Jul 25, 2018 at 1:02 PM Hannu Kröger wrote:
> What version of Cassandra are you running? The
What version of Cassandra are you running? There is a bug in 3.10.0 and certain
3.0.x that occurs in certain conditions and corrupts that file.
Hannu
> Vitali Dyachuk kirjoitti 25.7.2018 kello 10.48:
>
> Hi,
> I have noticed in the cassandra system.log that there is some issue with
> sstable
