On Fri, Mar 25, 2011 at 2:11 PM, ian douglas wrote:
> On 03/25/2011 10:12 AM, Jonathan Ellis wrote:
>>
>> On Fri, Mar 25, 2011 at 11:59 AM, ian douglas wrote:
>>>
>>> (we're running v0.60)
>>
>> I don't know if you could hear that from where you are, but our whole
>> office just yelled, "WTF!" :)
I don't know. Apache web server is a patchy web server, but crapsandra
just no way to put that in a good light.
On Friday, March 25, 2011, Dario Bravo wrote:
> People: Crapssandra.
> I'm starting a Cassandra project and starting to learn about this beautiful
> Cassandra, so I thougth that it wou
2011/3/23 ruslan usifov
> Hello
>
> Sometimes i seen in gc log follow message:
>
> 2011-03-23T14:40:56.049+0300: 14897.104: [GC 14897.104: [ParNew (promotion
> failed)
> Desired survivor size 41943040 bytes, new threshold 2 (max 2)
> - age 1:5573024 bytes,5573024 total
> - age 2:5
That would depend on how much data is generated per day. If it can still fit
in a row, the solution wold be to to just have rows keyed by date, like
20110326. This way you don't have to move data inside the cluster, the
selection logic will be in the client.
Even if the data is too large
Hi Peter -
Thanks for the response and adding the FAQ. Really great answers.
So if I understand correctly, the nodes getting the replica copies are
predetermined, based on the replication strategy.
One thing is still a bit unclear. So once a node establishes who its
replicants are, are t
> So if I understand correctly, the nodes getting the replica copies are
> predetermined, based on the replication strategy.
Yes, pre-determined as a function of ring layout (which nodes have
which tokens), the replication factor, and the replication strategy.
> One thing is still a bit unclear.
> So to resolve this i must tune young generation (HEAP_NEWSIZE) -Xmn, and
> tune in_memory_compaction_limit_in_mb config parameter?
More likely adjust the initial occupancy trigger and/or the heap size.
Probably just the latter. This is assuming you're on 0.7 with mostly
default JVM options. See
>> So to resolve this i must tune young generation (HEAP_NEWSIZE) -Xmn, and
>> tune in_memory_compaction_limit_in_mb config parameter?
>
> More likely adjust the initial occupancy trigger and/or the heap size.
> Probably just the latter. This is assuming you're on 0.7 with mostly
> default JVM opti
> What happened is this:
> You started your cluster with only one node, so at first, all data was on
> this.
> Then you added a second node. Cassandra then moved (approximatively)
> half of the data to the second node. In theory, at that
> point the data that was moved to the second node could be
Hi All,
I have sdd and normal disk .I am using sdd for data directory
should i also use sdd for saved_cache directory.
Thanks
Anurag
hehe, okay, maybe I'd chosen a bad name... does anybody think a better one?
If you check out the source, it can do a few new things, such as drop
keyspaces (except "system"), and show info on selected nodes...
Tomorrow I'll be adding a bunch of new features, I hope.
2011/3/26 Edward Capriolo
If you are using OPP you will need to understand how to balance the data around
the ring, start with RP until you have an idea why it's now working for you.
The RP will transform the key with a hash function, which is then compared to
the node tokens to locate the first replica for the data. Th
Thanks for the reply. The reason I want to go with OPP is to do range based
queries on time. All queries against the data are going to be time based.
With an RPP partitioning scheme, will it be efficient to do range based
queries ?
On Mar 26, 2011 9:12 PM, "aaron morton" wrote:
> If you are using
Hi,
Our cluster uses cassandra 0.7.4 (upgraded from 0.7.3) with
replication = 3. I found that error occurs on one node during hinted
handoff with following error (log #1 below).
When I tried out "scrub system HintsColumnFamily", I saw an ERROR in
log (log #2 below).
Do you think these errors are c
Similar case here
http://www.mail-archive.com/user@cassandra.apache.org/msg11358.html
Suggestion was to run repair if scrub raises an error.
Aaron
On 27 Mar 2011, at 16:17, Shotaro Kamio wrote:
> Hi,
>
> Our cluster uses cassandra 0.7.4 (upgraded from 0.7.3) with
> replication = 3. I found t
Hi Aaron,
I saw the discussion and I already tried to repair. But it doesn't
work since it's HintsColumnFamily. it's not replicated to other nodes.
Any suggestions are welcome.
Thanks,
Shotaro
On Sun, Mar 27, 2011 at 2:25 PM, aaron morton wrote:
> Similar case
> here http://www.mail-archive.
16 matches
Mail list logo