Is there a way to see who is connected to Cassandra based on a Cassandra user?
Calling all super heros.
I have a long standing Cassandra 2.1.12 ring that has an occasional node that
gets restarted and then is flagged with the invalid gossip generation error
leaving him down in nodetool status but the logs make it look like the nodes is
ok.
It’s only when I look at the ot
factor in Cassandra 2.1
On Wed, Aug 30, 2017 at 6:40 PM, Chuck Reynolds
mailto:creyno...@ancestry.com>> wrote:
How many users do you have (or expect to be found in system_auth.users)?
5 users.
What are the current RF for system_auth and consistency level you are using in
cqlsh?
135 in one D
TRACING ON)?
Tracing timeout even though I increased it to 120 seconds.
From: Oleksandr Shulgin
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, August 30, 2017 at 10:19 AM
To: User
Subject: Re: system_auth replication factor in Cassandra 2.1
On Wed, Aug 30, 2017 at 5:50 PM, Chuc
p of your own users & superusers, the link
above also has info on this.
Thanks,
Sam
On 30 August 2017 at 16:50, Chuck Reynolds
mailto:creyno...@ancestry.com>> wrote:
So I’ve read that if your using authentication in Cassandra 2.1 that your
replication factor should match the number of
So I’ve read that if your using authentication in Cassandra 2.1 that your
replication factor should match the number of nodes in your datacenter.
Is that true?
I have two datacenter cluster, 135 nodes in datacenter 1 & 227 nodes in an AWS
datacenter.
Why do I want to replicate the system_auth
ou running the query with? Does the query timeout even
with a consistency of one?
On 30/08/2017, at 9:49 AM, Chuck Reynolds
mailto:creyno...@ancestry.com>> wrote:
We have that keyspace replicated to the same number of nodes in the ring.
Right now I can’t even run select * from system_aut
We have that keyspace replicated to the same number of nodes in the ring.
Right now I can’t even run select * from system_auth.users without it timeing
out.
From: Akhil Mehra
Reply-To: "user@cassandra.apache.org"
Date: Tuesday, August 29, 2017 at 3:46 PM
To: user
Subject: Re: UnauthorizedExc
I’m receiving the following error when quering a table that I know the user has
super user rights to.
It only happens about 10% of the time.
com.datastax.driver.core.exceptions.UnauthorizedException: User test has no
SELECT permission on or any of its parents.
I’m running queries based on the token ranges to initiate read repairs across
datacenter.
Example query with CONSISTENCY set to ALL
SELECT token(test_guid), test_guid FROM test_table WHERE
token(test_guid)>6546138161478345924 AND token(test_guid)<6571069709219758671;
Is there a way to tell if r
Anyone?
From: "Chuck (me) Reynolds"
Reply-To: "user@cassandra.apache.org"
Date: Tuesday, August 22, 2017 at 9:40 AM
To: "user@cassandra.apache.org"
Subject: Upgrade requirements for upgrading from cassandra 2.1.x to 2.2.x
Where can I find requirements to upgrade from Cassandra 2.1.x to 2.2.x?
Where can I find requirements to upgrade from Cassandra 2.1.x to 2.2.x?
I would like to know things like do I have to do an SStable upgrade or not.
Thanks
Tell me more.
On 8/8/17, 10:44 PM, "James Tobin" wrote:
Hello, I'm working with an employer that is looking to hire someone to
become their lead on Apache Cassandra in the Netherlands.
Consequently I had hoped that some members of this mailing list may
like to discuss further off
instead they have twice as much, it sounds like it's balancing by # of
tokens instead, which may be an indication that you're somehow using
SimpleStrategy, or your NetworkTopologyStrategy is somehow misconfigured for
one or more keyspaces.
Can you paste your keyspace replication strate
y, August 7, 2017 at 2:39 PM
To: cassandra mailto:user@cassandra.apache.org>>
Subject: Re: Different data size between datacenters
You're using NetworkTopologyStrategy and not SimpleStrategy, correct?
On Mon, Aug 7, 2017 at 11:50 AM, Chuck Reynolds
mailto:creyno...@ancestry.com>&g
same number of token/vnodes in both data centers?
From: Chuck Reynolds [mailto:creyno...@ancestry.com]
Sent: Monday, August 07, 2017 1:51 PM
To: user@cassandra.apache.org
Subject: Different data size between datacenters
I have a cluster that spans two datacenters running Cassandra 2.1.12. 135
nod
Aug 7, 2017 at 11:50 AM, Chuck Reynolds
mailto:creyno...@ancestry.com>> wrote:
I have a cluster that spans two datacenters running Cassandra 2.1.12. 135
nodes in my data center and about 185 in AWS.
The size of the second data center (AWS) is quite a bit smaller. Replication
is the sam
I have a cluster that spans two datacenters running Cassandra 2.1.12. 135
nodes in my data center and about 185 in AWS.
The size of the second data center (AWS) is quite a bit smaller. Replication
is the same in both datacenters. Is there a logical explanation for this?
thanks
I have a need to create another datacenter and upgrade my existing Cassandra
from 2.1.13 to Cassandra 3.0.9.
Can I do this as one step? Create a new Cassandra ring that is version 3.0.9
and replicate the data from an existing ring that is Cassandra 2.1.13?
After replicating to the new ring if
I have a large Cassandra 2.1.13 ring (60 nodes) in AWS that has consistently
random high read times. In general most reads are under 10 milliseconds but
with in the 30 request there is usually a read time that is a couple of seconds.
Instance type: r4.8xlarge
EBS GP2 volumes, 3tb with 9000 IOPS
es (update property file if need be)
4. create new cluster in DC2,
5. use sstableloader to stream DC1 data to DC2.
On Wed, Mar 8, 2017 at 8:13 AM, Chuck Reynolds
mailto:creyno...@ancestry.com>> wrote:
I’m running C* 2.1.13 and I have two rings that are replicating data from our
data center t
I’m running C* 2.1.13 and I have two rings that are replicating data from our
data center to one in AWS.
We would like to keep both of them for a while but we have a need to disconnect
them. How can this be done?
22 matches
Mail list logo
