I'm seeing the same with cassandra-2.0.4 during compaction, after lot of
sstable files are streamed after bootstrap/repair. Strange thing is, the 'Last
written key >= current key' exception during compaction of L0, L1 sstables,
goes away after restarting cassandra. But, then see those warnings a
tual Nodes and
256 tokens are assigned to it, how does the STATUS line only show one token
value? In this case the -12331...#.
On Mon, Oct 7, 2013 at 9:00 PM, Sameer Farooqui wrote:
Thanks, Ravi!
>
>
>
>On Mon, Oct 7, 2013 at 2:40 AM, ravi prasad wrote:
>
>the output of &
the output of "nodetool gossipinfo" are the application states of each
endpoint/node in the cluster that are exchanged b/w the nodes during gossiping.
"Severity" is basically a measure of compaction activity/events in a node ( see
https://issues.apache.org/jira/browse/CASSANDRA-3722 for the det
Hi,
I have a data modelling question. I'm modelling for an use case where, an
object can have multiple facets and each facet can have multiple revisions and
the query pattern looks like "get latest 'n' revisions for all facets for an
object (n=1,2,3)". With a table like below:
create tabl
