Hi,
Our environment will consist of cluster with size not bigger than 2 to 4
nodes per cluster(all
located in the same DC). We want to ensure that every node in the cluster
will own 100% of
the data. A node adding(or removing) procedure will be automated so we want
to ensure we're
In case anyone was following this issue, it ended up being something that
looked an awful lot like CASSANDRA-6053 — when the node was removed, it didn’t
successfully remove from the peers table from all nodes, and thus several of
them were doing their best to try to contact it despite it being
Hey Guys,
How can I define custom CQL3 functions (similar to dateOf, now, etc)?
Cheers,
Drew
Version is C 1.2.6. We use DSE 3.1.3
From: Robert Coli [mailto:rc...@eventbrite.com]
Sent: Friday, February 07, 2014 4:17 PM
To: user@cassandra.apache.org
Subject: Re: Hector Could not flush transport error
On Fri, Feb 7, 2014 at 4:05 PM, Senthil, Athinanthny X. -ND
Maybe that node was just trying to tell you that it really wanted to work
in a different data center :)
On Mon, Feb 10, 2014 at 10:08 AM, Sholes, Joshua
joshua_sho...@cable.comcast.com wrote:
In case anyone was following this issue, it ended up being something
that looked an awful lot like
Hello,
I posted this issue to the pig mailing list and I'm thinking the issue I'm
having is more related to cassandra?
When I run pig scripts against hadoop it works as advertised, however when
I try to have pig get data from cassandra it fails everytime.
Cassandra: [cqlsh 4.1.0 | Cassandra
Also, a major compaction doesn't flush the memtable. If the memtable is
still full, reads may take slightly longer as they may have to be merged
with any on-disk data before being served.
On 10 February 2014 21:18, Tupshin Harper tups...@tupshin.com wrote:
You don't mention disks and RAM, but
Is this your first cluster? Have you run older versions of Cassandra? Any
specific resource tuning?
Thanks all. We are unable to bootstrap nodes and are considering creating a
fresh cluster in hopes this is some how data related.
On Feb 10, 2014 5:33 PM, Brust, Corwin [Hollander]
More generally, a thrift api or other mechanism for Astyanax to get the
INTERNAL_IP seems necessary to use ConnectionPoolType.TOKEN_AWARE +
NodeDiscoveryType.TOKEN_AWARE in a multi-dc setup. Absent one I'm
confused how that combination is possible.
On 02/06/2014 03:17 PM, Ted Pearson wrote:
Hi Guys,
Im experimenting with using IN to reduce the number of quires I have to
execute. The following works in CQL:
i.e select log_entry from log_index where keyword in (‘keyword1’,
‘keyword2’, ‘keyword3’, etc…);
So I now want to work out how to convert this:
Hello Jacob,
You can try the bind marker for variadic param (new feature):
PreparedStatement p = session.prepare(select log_entry from log_index
where keyword *IN* ?);
session.execute(p.bind(Arrays.asList(keyword1,keyword2,...));
Regards
Duy Hai DOAN
On Mon, Feb 10, 2014 at 11:50 PM, Jacob
Perfect, thanks! I wonder if this is documented anywhere? Certainly I have no
idea how to search google using the keyword “in” :D
String[] words = TagsToArray.tagsToArray(keyword.toLowerCase());
PreparedStatement p = api.getCassandraSession().prepare(select log_entry
from log_index
I don't know if it's documented somewhere. Personnally I got the info by
following the Cassandra dev blog and reading each new release notes.
In each Cassandra release notes, you have a list of bug fixes but also new
features. Just read the corresponding JIRA to get the details.
Regards
Duy
Hi,
I was hoping someone could clarify a point about multi-DC replication.
Let's say I have 2 data centers configured with replication factor = 3 in
each DC.
My client app is sitting in DC 1 and is able to intelligently pick a
coordinator that will also be a replica partner.
So the client app
14 matches
Mail list logo
