You're assuming per DC has same total num_tokens, right?
If I add a new node into DC1, will it change the tokens owned by DC2 and DC3?
2018-04-12 0:59 GMT+08:00 Jeff Jirsa :
> When you add DC3, they'll get tokens (that aren't currently in use in any
> existing DC). Either you assign tokens (let's
DC are independent of each other. Adding nodes to DC1 won't have any token
effect owned by other DC.
On Thu, Apr 26, 2018 at 1:04 AM, Jinhua Luo wrote:
> You're assuming per DC has same total num_tokens, right?
> If I add a new node into DC1, will it change the tokens owned by DC2 and
> DC3?
>
How to guarantee the tokens independent between DC? They forms one
ring, and they must be (re-)assigned when needed.
Use offset per DC? But it seems that the DC list must be fixed in advanced?
To make sure the tokens are evenly distributed into the ring among the
DC(s), are there chances to change
Hello,
yet another question/issue with repair.
Cassandra 2.1.18, 3 nodes, RF=3, vnode=256, data volume ~ 5G per node only. A
repair (nodetool repair -par) issued on a single node at this data volume takes
around 36min with an AVG of ~ 15MByte/s disk throughput (read+write) for the
entire time-
version: cassandra-3.0.9
conf/cassnadra.yaml changes:
>
> - seeds: "host421"
> listen_address: host421
> rpc_address: host421
>
Java client:
package database.tools;
>
> import java.net.InetSocketAddress;
> import java.util.Map;
> import java.util.Map.Entry;
>
> import com.datastax.driv
host421 != bluej421
My guess is 192.168.3.232 != {host421,bluej421} somewhere.
If DNS hostnames are being used, the DNS infrastructure needs to be spot
on, forward and reverse. If the DNS infrastructure is /etc/hosts, those
hosts entries need to be spot on for the entire cluster, forward and
rever
Sorry, my mistake. Everything is bluej421. I tried to (but in hind sight
should not have) edit the append to make the host more generic. The actual
experiment uses bluej421 everywhere.
cqlsh from the same host works fine with the same exact host specified as
CQLSH_HOST.
I just now installed a
OK, thanks for the extra info.
Hmm.. `unconfigured table schema_keyspaces`
Seems like an incomplete upgrade to 3.0.9 (and now 3.11.2) from some
earlier version, which used schema_columnfamilies, I think?
--
Michael
On 04/26/2018 08:55 AM, Lou DeGenaro wrote:
> Sorry, my mistake. Everything is
On 04/26/2018 09:03 AM, Michael Shuler wrote:
> Seems like an incomplete upgrade to 3.0.9 (and now 3.11.2) from some
> earlier version, which used schema_columnfamilies, I think?
Similar error on:
https://datastax-oss.atlassian.net/browse/JAVA-1092
--
Michael
---
I did not realize that the 3.0.9 cassandra.yaml file is not compatible with
3.11??
I started fresh and edited the 3.11 cassandra.yaml file. Here are the
exact changes:
diff cassandra.yaml cassandra.yaml.orig
425c425
< - seeds: "bluej421"
---
> - seeds: "127.0.0.1"
599c599
< l
On 04/26/2018 09:17 AM, Lou DeGenaro wrote:
>
> I started fresh and edited the 3.11 cassandra.yaml file. Here are the
> exact changes:
>
> diff cassandra.yaml cassandra.yaml.orig
> 425c425
> < - seeds: "bluej421"
> ---
>> - seeds: "127.0.0.1"
> 599c599
> < listen_address: blu
Good call! Java client was using Cassandra 2.11 lib jars in classpath.
Switching to Cassandra 3.11 jars in Java client classpath works!
Thx!
Lou.
On Thu, Apr 26, 2018 at 10:30 AM, Michael Shuler
wrote:
> On 04/26/2018 09:17 AM, Lou DeGenaro wrote:
> >
> > I started fresh and edited the 3.11 ca
I can't say for sure, because I haven't measured it, but I've seen a
combination of readahead + large chunk size with compression cause serious
issues with read amplification, although I'm not sure if or how it would
apply here. Likely depends on the size of your partitions and the
fragmentation o
On Thu, Apr 26, 2018 at 1:34 AM, Jinhua Luo wrote:
> How to guarantee the tokens independent between DC?
Cassandra wont let you have duplicate tokens - it wont start if you do it
by mistake, and it won't do it automatically.
> They forms one
> ring, and they must be (re-)assigned when needed.
Wait, isn’t this the Apache Cassandra mailing list? Shouldn’t this be on the
pickle users list or something?
(Just kidding, everyone. I think there should be room for reaper and DataStax
inquiries here.)
Sean Durity
From: Joaquin Casares [mailto:joaq...@thelastpickle.com]
Sent: Tuesday, April
Hi Thomas,
I don't think I have seen compaction ever being faster.
For me, tables with small values usually are around 5 MB/s with a single
compaction. With larger blobs (few KB per blob) I have seen 16MB/s. Both
with "nodetool setcompactionthroughput 0".
I don't think its disk related either. I
Hi,
How frequently one should run nodetool rebuild_index and what's its impact
on performance in terms of iops,cpu utilisation etc.
Regards
Hi,
The secondary indices in Cassandra are maintained continuously as data is
written. Also index rebuilding is kicked off automatically when you create
a new index. So, there is no good reason to schedule nodetool rebuild_index
regularly.
However, if you find any discrepancy in the index and dat
18 matches
Mail list logo
