Hi,
I'm volunteer to be contributor on Metrics or Tooling component. Are we
supposed/allowed to edit Confluence page directly?Btw I think that tooling
should be split, maybe one ticket per tool?
Thanks,
RomainLe mercredi 7 novembre 2018 à 22:51:30 UTC+1, sankalp kohli
a écrit :
This
Hi,
I think you have to look at how authenticator/authorizer/role_manager are
handled.e.g.
https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L103https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/auth/AllowAllAuthenticator.java
Best,Romain
Le Mercre
Yes you should provide more context."Lots of timeouts": read? write? both?Did
you run sstableupgrade? Java version ? (C* 3.0 requires Java 8u40 or later)What
is your data model? Lots of counters? Compression enabled on tables? "No
updates/deletes": no deletes but is there TTL on data?
etc.
Best
To be able to downgrade we should be able to pin both commitlog and sstables
versions, e.g. -Dcassandra.commitlog_version=3 -Dcassandra.sstable_version=jb
That would be awesome because it would decorrelate binaries version and data
version. Upgrades would be much less risky so I guess that adopti
Interesting, will you publish the backports on https://github.com/apple ?
Thanks,
Romain
Hi,
I use the "current 2.1.16" (commit cdd535fcac4ba79bb371e8373c6504d9e3978853) on
production in 5 DCs (82 nodes) out of 7 and it works well!I've just had to add
a MBean to track changes of the NTR queue length on top of cdd535f. This allow
to make correlations with other metrics and see the im
+1 for G1 with such a heap size. And don't set heap new size, let g1 decide.
Inviato da Yahoo Mail su Android
Il mar, 20 set, 2016 alle 9:01, Jeff Jirsa ha scritto:
Major changes in 3.0, but the big ones involve storage - parent ticket is
https://issues.apache.org/jira/browse/CASSANDRA-942
Hi,
You can force the Java version used by Cassandra here:
https://github.com/apache/cassandra/blob/cassandra-3.0/bin/cassandra.in.bat#L29
Best,
Romain
Le Samedi 3 septembre 2016 11h11, Andy Cobley a écrit :
Thanks Michael and Paulo,
Upon further investigation, this is NOT a cassand
Hi,
Only a repair between each DC (i.e. on the whole cluster) can guarantee that
your DCs are synced. You can make some checks like data size, estimation of
number of keys, etc. but it's not accurate at all.
Note: your question is intended to u...@cassandra.apache.org
Best,
Romain
Le Mercre
I don't use C* in such a context but out of curiosity did you set the
request_scheduler to RoundRobin or did you implement your own scheduler?
Romain
Le Vendredi 15 juillet 2016 8h39, jason zhao yang
a écrit :
Hi,
May I ask is there any plan of extending functionalities related to
Mult
I targeted the dev list because I would like to know why the developer (patch
by branimir and reviewed by benedict) mentions "Only supported with the
Murmur3Partitioner" whereas his patch uses IPartitioner interface. (I will try
to reach them on IRC if they don't see this message.)
We have running clusters which use RandomPartitioner that's why I wonder if we
could use this feature in the future.
Best,
Romain
Hi all,
cassandra.yaml mentions that the new token allocation algorithm is only
supported with the Murmur3Partitioner [1].
When looking at the commit [2] I see that IPartitioner interface is used.
I do see references to Murmur3Partitioner but only in tests classes.
What would prevent to use Rand
13 matches
Mail list logo