Hello,
Thank you all for your responses.
Performance is not an issue at all as I described, so it shouldn't be
problematic. At least this is our current understanding. We will try it and
post back if something interesting comes up. Many thanks.
Regards,
Vasilis
On Tue, Oct 16, 2012 at 7:34 P
Gus, we've found the cause.
It was a problem in Cassandra, but it has been already fixed in cassandra
1.1.6.
Commit with the problem:
2c69e2ea757be9492a095aa22b5d51234c4b4102
You can see it at
https://issues.apache.org/jira/secure/attachment/12544204/CASSANDRA-4561-CS.patch
Commit with the fix:
ok, let me try asking the question a different way ...
How does cassandra use memory and how can I plan how much is needed? I
have a 1 GB memtable and 5 GB total heap and that's still not enough even
though the number of concurrent connections and garbage generation rate is
fairly low.
If I were
Did you run cleanup?
Andrey
On Fri, Oct 19, 2012 at 10:23 AM, Brian Tarbox wrote:
> I had a two node cluster that I expanded to four nodes. I ran the token
> generation script and moved all the nodes so that when I run "nodetool ring"
> each node reports 25% Effective-Ownership.
>
> However, my
I had a two node cluster that I expanded to four nodes. I ran the token
generation script and moved all the nodes so that when I run "nodetool
ring" each node reports 25% Effective-Ownership.
However, my load numbers map out to 39%, 30%, 15%, 17%.
How can that be?
Thanks.
I have a column family called "books", and am trying to delete all rows where
the "title" column is equal to "hatchet". This is the query I am using:
DELETE FROM books WHERE title = 'hatchet';
This query is failing with this error:
Bad Request: PRIMARY KEY part title found in SET part
I
Yes. That would be a good jira if it is not already listed. If node is
a seed node autobootstrap and replicate_token settings should trigger
a fatal non-start because your giving c* conflicting directions.
Edward
On Fri, Oct 19, 2012 at 8:49 AM, Thomas van Neerijnen
wrote:
> Hi all
>
> I recentl
Hi all
I recently tried to replace a dead node using
-Dcassandra.replace_token=, which so far has been good to me.
However on one of my nodes this option was ignored and the node simply
picked a different token to live at and started up there.
It was a foolish mistake on my part because it was se
Hi
When I sent the mail I'd had the new node on for about an hour, the old
node died about an hour before that.
The weirdness in the log files stopped yesterday afternoon, about 4 or 5
hours after I replaced the node so it seems to have resolved itself.
Seeing as there's no error to look at in the
I see, it helps a lot. Thank you for you info.
Oh, also Mr. Joe Celko :P
On Thu, Oct 18, 2012 at 7:10 PM, aaron morton wrote:
> Very slim reason to link to my favourite Joe Celko (
> http://en.wikipedia.org/wiki/Joe_Celko) quote:
>
> "
> 'LOL! My wife is an ordained Soto Zen priest. I would say
Hi,
Is it possible to reuse same compound primary key after delete? I guess it
works fine for non composite keys.
-Vivek
Ok. I did assume the same, here is what i have tried to fetch composite
columns via thrift and CQL query as well!
Not sure why thrift API is returning me column name as empty! (Tried with
Cassandra 1.1.5)
Here is the program:
/
12 matches
Mail list logo
