Does anyone know what to do when such an event occurs?
Does anyone know how this could happen?
I would have tried repairing the node with nodetool repair but that takes much
too long… I need my cluster to work for our online system. At this point
nothing is working. It’s like the whole cluster
Although amending the query is a workaround for this (and duplicating the
columns in the selection is not something I imagine one would deliberately
do), this is still an ugly regression, so I've opened
https://issues.apache.org/jira/browse/CASSANDRA-9636 to fix it.
Thanks,
Sam
On Tue, Jun 23,
I agree. Thanks a lot.
On 23 Jun 2015, at 15:31 , Sam Tunnicliffe
s...@beobal.commailto:s...@beobal.com wrote:
Although amending the query is a workaround for this (and duplicating the
columns in the selection is not something I imagine one would deliberately do),
this is still an ugly
Hi Sam,
You have a real good gut feeling.
I went to see the query that I used since many months… which was working…. but
obviously there is something wrong with it.
The problem with it was *simply* that I placed twice the same field in the
select. I corrected in my code and now I don’t have the
Hi Jean,
I had to reboot a node. I killed the cassandra process on that node. You
should drain the node before killing java (or using any service stop
command). This is not what causes the issue yet it will help you to keep
consistence if you use counters, and make the reboot faster in any cases.
Btw, Hope you'll find the answers you could not ask in today online lesson
;-).
C*heers
2015-06-23 20:22 GMT+02:00 Alain RODRIGUEZ arodr...@gmail.com:
Hi,
I do not agree with Scenario 1 result Arun,
The 2 nodes don't have the data yet are available. IMHO what happens next
i a slow read
Scenario 1: Read query is fired for a key, data is found on one node and
not found on other two nodes who are responsible for the token
corresponding to key.
You read query will fail, as it expects to receive data from 2 nodes with
RF=3
Scenario 2: Read query is fired and all 3 replicas have
M more confused...Different responses. .Anyone who can explain with 100% surity
?
Thanks
Anuj
Sent from Yahoo Mail on Android
From:arun sirimalla arunsi...@gmail.com
Date:Wed, 24 Jun, 2015 at 12:00 am
Subject:Re: Read Consistency
Thanks good to know that.
On Tue, Jun 23, 2015 at 11:27
Regards to all the list.
We are working in a migration to Apache Cassandra (version 2.1.5) from
SQL Server 2008 for a new client, and I have two question about it.
1- Has Sqoop support to make this migration from SQL Server to Cassandra
or just the version included in DataStax Community
Thanks, Alex for the quick response.
On 23/06/15 15:34, Alex Popescu wrote:
Hi Marcos,
On Tue, Jun 23, 2015 at 12:23 PM, Marcos Ortiz mlor...@uci.cu
mailto:mlor...@uci.cuwrote:
MaxPermSize=256m; support was removed in 8.0
1. The MaxPermSize is just a warning.
2. This is the first
On Tue, Jun 23, 2015 at 12:13 PM, Marcos Ortiz mlor...@uci.cu wrote:
2- They used heavily C# in a Microsoft-based environment, so I need to
know if the .Net driver is ready to use for production
The DataStax C# driver has been used in production for quite a while by
numerous users. It is the
Anuj,
In the first scenario, the data from the single node holding data is
returned. The query will not fail if the consistency level is met, even if
the read was inconsistent.
On Tue, Jun 23, 2015 at 2:16 PM, Anuj Wadehra anujw_2...@yahoo.co.in
wrote:
Why would it fail and with what Thrift
Yes, that is what he means. CL is for how many nodes need to respond, not
agree.
On Tue, Jun 23, 2015 at 2:26 PM, arun sirimalla arunsi...@gmail.com wrote:
So do you mean with CL set to QUORUM, if data is only on one node, the
query still succeeds.
On Tue, Jun 23, 2015 at 11:21 AM, Philip
Thanks..So all of us agree that in scenario 1, data would be returned and that
was my initial understanding..
Anuj
Sent from Yahoo Mail on Android
From:Anuj Wadehra anujw_2...@yahoo.co.in
Date:Wed, 24 Jun, 2015 at 12:15 am
Subject:Re: Read Consistency
M more confused...Different
Hi Marcos,
On Tue, Jun 23, 2015 at 12:23 PM, Marcos Ortiz mlor...@uci.cu wrote:
MaxPermSize=256m; support was removed in 8.0
1. The MaxPermSize is just a warning.
2. This is the first time I've seen that error. Search revealed this
StackOverflow thread
Hi,
Here's an alternative if OpsCenter + proxy situation proves to be a pain:
http://sematext.com/spm/integrations/cassandra-monitoring.html
Proxy situation is super simple
https://sematext.atlassian.net/wiki/display/PUBSPM/SPM+FAQ#SPMFAQ-CanSPMclientsenddataoutfromserversthatarebehindaproxy
.
Hi,
Need to validate my understanding..
RF=3 , Read CL = Quorum
What would be returned to the client in following scenarios:
Scenario 1: Read query is fired for a key, data is found on one node and not
found on other two nodes who are responsible for the token corresponding to key.
Why would it fail and with what Thrift error? What if the data didnt exist on
any of the nodes..query wont fail if doesnt find data..
Not convinced..
Sent from Yahoo Mail on Android
From:arun sirimalla arunsi...@gmail.com
Date:Tue, 23 Jun, 2015 at 11:39 pm
Subject:Re: Read Consistency
Hi,
I do not agree with Scenario 1 result Arun,
The 2 nodes don't have the data yet are available. IMHO what happens next i
a slow read since it will have to perform read repair and coordinator will
send back the result and an 'OK' message.Consistency is not met when nor
enough nodes were up.
Thanks good to know that.
On Tue, Jun 23, 2015 at 11:27 AM, Philip Thompson
philip.thomp...@datastax.com wrote:
Yes, that is what he means. CL is for how many nodes need to respond, not
agree.
On Tue, Jun 23, 2015 at 2:26 PM, arun sirimalla arunsi...@gmail.com
wrote:
So do you mean with
Dear Alain,
Thank you for your reply.
Ok, yes I did not drain. The cluster was loaded with tons of records, and no
new records were added since few weeks. Each node had a load of about 160 GB as
seen in the “nodetool status. I killed the cassandradeamon, and restarted it.
After cassandra was
I'm using DevCenter 1.2.0 in KDE, particularly in Kubuntu 14.10 with KDE
4.14.1, and when I want to start the application, it raises this error:
$ ./DevCenter
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
MaxPermSize=256m; support was removed in 8.0
java:
So do you mean with CL set to QUORUM, if data is only on one node, the
query still succeeds.
On Tue, Jun 23, 2015 at 11:21 AM, Philip Thompson
philip.thomp...@datastax.com wrote:
Anuj,
In the first scenario, the data from the single node holding data is
returned. The query will not fail if
On Tue, Jun 23, 2015 at 12:58 PM, Marcos Ortiz mlor...@uci.cu wrote:
OK, I will do it.
As a side note, DevCenter 1.3 also has supported for reaching out to us
directly [1]
Unfortunately OpsCenter doesn't currently support running behind a proxy,
because of the issues you've discovered. Fixing this is on our roadmap
though, but I unfortunately can't give a specific date or release when we
will get to it. You will definitely see it in the release notes when we
release
On Sun, Jun 21, 2015 at 8:25 PM, John Wong gokoproj...@gmail.com wrote:
In the case of restoring from snapshots I have restored a 6-node replica
with just copying snapshot files (along with schema files), run nodetool
refresh, and should be able to complete in a few hours. But now with
Hi, All,
Does anyone know the roadmap of Cassandra 3.0?
Thanks
Boying
Hey there,
I have imported the following schema to my cassandra db
Hello all,
Please, i try to start cassandra remotely but it didn't work. i don't find
cassandra process when using ps aux|grep cassandra
ssh -t root@g-8 -x sshpass -p 'ubuntu' ssh -t root@10.147.243.163 -o
StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -x
Hi,
I’m using Datastax Java Driver V 2.1.6
I migrated my cluster to Cassandra V2.1.7
And now I have an error on my client that goes like:
2015-06-23 10:49:11.914 WARN 20955 --- [ I/O worker #14]
com.datastax.driver.core.RequestHandler : /192.168.2.201:9042 replied with
server error
Hi,
I have a cluster with 5 nodes running Cassandra 2.1.6.
I had to reboot a node. I killed the cassandra process on that node. Rebooted
the machine, and restarted Cassandra.
~/apache-cassandra-DATA/data:321nodetool status
Datacenter: datacenter1
===
Status=Up/Down
|/
Can you share the query that you're executing when you see the error and
the schema of the target table? It could be something related to
CASSANDRA-9532.
On Tue, Jun 23, 2015 at 10:05 AM, Jean Tremblay
jean.tremb...@zen-innovations.com wrote:
Hi,
I’m using Datastax Java Driver V 2.1.6
I
on the node 192.168.2.100, did you run repair after its status is UN?
On Wed, Jun 24, 2015 at 2:46 AM, Jean Tremblay
jean.tremb...@zen-innovations.com wrote:
Dear Alain,
Thank you for your reply.
Ok, yes I did not drain. The cluster was loaded with tons of records,
and no new records
Looking for this? Or something else?
http://planetcassandra.org/blog/cassandra-2-2-3-0-and-beyond/
On 2015/06/24 12:42, Lu, Boying wrote:
Hi, All,
Does anyone know the roadmap of Cassandra 3.0?
Thanks
Boying
Thanks a lot :)
From: Yoshi Kimoto [mailto:yy.kim...@gmail.com]
Sent: 2015年6月24日 12:12
To: user@cassandra.apache.org
Subject: Re: Is there any roadmap of Cassandra 3.0?
Looking for this? Or something else?
http://planetcassandra.org/blog/cassandra-2-2-3-0-and-beyond/
On 2015/06/24 12:42, Lu,
35 matches
Mail list logo
