The problem is that i have defined too many racks in my cluster (because i have
multiple Cassandra nodes on a single server, so i defined each physical server
as a separate rack) and because i haven't heard of any rule of "one seed per
rack" before the tlp article, (actually the only rule about
Hi
If you are planning on setting up a new cluster with
allocate_tokens_for_keyspace, then yes, you will need one seed node per
rack. As Jon mentioned in a previous email, you must manually specify the
token range for *each* seed node. This can be done using the initial_token
setting.
The article
Good idea Jeff. I can add that in if you like? Do we have a ticket for it
or should I just raise one?
On Mon, 6 May 2019 at 03:49, Jeff Jirsa wrote:
> Picking an ideal allocation for N seed nodes and M vnodes per seed is
> probably something we should add as a little python script or similar in
Hi Jean,
Good question. I think that sentence is slightly confusing and here is why:
If the cluster has tokens are already evenly distributed and there is no
plans to expand the cluster, then applying the allocate_tokens_for_keyspace
setting has no real practical value.
If the cluster has tokens
Picking an ideal allocation for N seed nodes and M vnodes per seed is probably
something we should add as a little python script or similar in /tools/ to make
this easier. Then let the auto allocation stuff kick in after that.
> On May 5, 2019, at 8:23 AM, Jon Haddad wrote:
>
> I mean you'd w
I mean you'd want to set up the initial tokens for the first 3 nodes
of your cluster, which are usually the seed nodes.
On Sat, May 4, 2019 at 8:31 PM onmstester onmstester
wrote:
>
> So do you mean setting tokens for only one node (one of the seed node) is
> fair enough?
> I can not see any pr
Do separate queries for each partition you want. There's no benefit
in using the IN() clause here, and performance is significantly worse
with multi-partition IN(), especially if the partitions are small.
On Sun, May 5, 2019 at 4:52 AM Soheil Pourbafrani wrote:
>
> Hi,
>
> I want to run cqlsh qu
Hi Rhys,
I encountered this error after adding new SSTables to a cluster and running
nodetool refresh (v3.0.12).
The refresh worked, but after starting repairs on the cluster, I got the
"Validation failed in /X.X.X.X" error on the remote DC.
A rolling restart solved the issue for me.
Hope this he
Hi,
I want to run cqlsh query on cassandra table using IN
SELECT * from data WHERE nid = 'value' AND mm IN (201905,201904) AND
tid = 'value2' AND ts >= 155639466 AND ts <= 155699946 ;
The nid and mm columns are partition key and the ts is clustering key.
The problem is cassandra
