Edit:
1. dc2 node has been removed.
nodetool status shows only active nodes.
2. Repair done on all nodes.
3. Cassandra restarted
Still it doesn't solve the problem.
On Thu, Apr 28, 2016 at 9:00 AM, Siddharth Verma <
verma.siddha...@snapdeal.com> wrote:
> Hi, If the info could be used
> we ar
Hi, If the info could be used
we are using two DCs
dc1 - 3 nodes
dc2 - 1 node
however, dc2 has been down for 3-4 weeks, and we haven't removed it yet.
spark slaves on same machines as the cassandra nodes.
each node has two instances of slaves.
spark master on a separate machine.
If anyone could
No.We are not saving them.I have never read that in DataStax documentation.
ThanksAnuj
Sent from Yahoo Mail on Android
On Thu, 28 Apr, 2016 at 12:45 AM,
sean_r_dur...@homedepot.com wrote:
What about the commitlogs? Are you saving those off anywhere in between the
snapshot and the crash?
What about the commitlogs? Are you saving those off anywhere in between the
snapshot and the crash?
Sean Durity
From: Anuj Wadehra [mailto:anujw_2...@yahoo.co.in]
Sent: Monday, April 25, 2016 10:26 PM
To: User
Subject: Inconsistent Reads after Restoring Snapshot
Hi,
We have 2.0.14. We use RF=
Hi,
I dont know, if someone has faced this problem or not.
I am running a job where some data is loaded from cassandra table. From
that data, i make some insert and delete statements.
and execute it (using forEach)
Code snippet:
boolean deleteStatus= connector.openSession().execute(delete).wasAppl
Hi,
You can’t batch LWT if they don’t work on the same partition. So in your below
queries all the values of “id” must be the same.
--
Jacques-Henri Berthemet
From: y2k...@gmail.com [mailto:y2k...@gmail.com] On Behalf Of Jimmy Lin
Sent: mercredi 27 avril 2016 18:14
To: user@cassandra.apache.org
Hi Robert,
This could be related to:
https://issues.apache.org/jira/plugins/servlet/mobile#issue/CASSANDRA-9242
(Maybe you can try to comment this option and try again)
Le 27 avr. 2016 15:21, "Robert Sicoie" a écrit :
> Hi guys,
>
> I'm upgrading from cassandra 2.1 to cassandra 3.0.5 and mx4j su
hi all,
we like to consider using light weight transaction like the following:
begin batch:
update table set x=y where id=A if not exists;
update table set x=y where id=B if not exists;
update table set x=y where id=C if not exists;
update table set x=y where id=D if not exists;
apply batch
(using
Hi guys,
I'm upgrading from cassandra 2.1 to cassandra 3.0.5 and mx4j support
seems to be broker. An empty html page is shown:
> GET / HTTP/1.1
> Host: localhost:8081
> User-Agent: curl/7.43.0
> Accept: */*
>
* HTTP 1.0, assume close after body
< HTTP/1.0 200 OK
< expires: now
< Server: MX4J-H
