Hello,
I issue the subject command running Cassandra 2.2.12 and get this response:
Requested clearing snapshot(s) for [all keyspaces] with snapshot name
[1537185517560-rmsharesducc]
But the snapshot does not go away.
degenaro@myhost1:~>
Hello Shyam,
I think Jonathan understood the meaning of 'RF'. He is suggesting you to
look at all your keyspaces strategy/RF for the system_auth table and make
sure to use the right replication factor (and probably
a NetworkTopologyStrategy).
This might help: cqlsh -e "DESCRIBE KEYSPACE
Hello Gabriel,
Sorry for not answering earlier. I should have, given that I contributed
spreading this wrong idea. I will also try to edit my comment in the post.
I have been fooled by the piece of documentation you mentioned when
answering this question on our blog. I probably answered this one
Hello Gabriel,
Another clue to explore would be to use the TTL as a default value if
> that's a good fit. TTLs set at the table level with 'default_time_to_live'
> should not generate any tombstone at all in C*3.0+. Not tested on my hand,
> but I read about this.
>
As explained on a parallel
Just wanted to let you know running the command from all the nodes matched the
count of records on both clusters
One more question, can any body know how to import the data in different
keyspace using sstableloader
Thanks,
> On Sep 26, 2018, at 3:56 PM, rajasekhar kommineni wrote:
>
> I
Hi,
I am new to Cassandra. Is there any recommended maximum data size per node for
Cassandra 3 with STCS. Also any recommendation on SSD RAID 0 vs NVME JBOD?
ThanksSuresh
Hi Suresh,
Welcome to Cassandra!
Node density is an important topic with Cassandra. Depending on the node
type, data usage, and your operational expertise, you can go somewhere
between 1TB and 3TB of data size. If you just start, stay below of 1TB to
avoid troubles. Storing too much data on a
I'm afraid you cannot have a proper tabular formatting or an expand to
multiple rows (which changes significantly the semantics)
Indeed the result of the final func is returned by CQL as a whole column
and currently there is no way to change the output formatting
On Thu, Sep 27, 2018 at 6:55
On Thu, Sep 27, 2018 at 2:24 AM Anup Shirolkar <
anup.shirol...@instaclustr.com> wrote:
>
> Most of the things look ok from your setup.
>
> You can enable Debug logs for repair duration.
> This will help identify if you are hitting a bug or other cause of unusual
> behaviour.
>
> Just a remote
