After running 3 days on Cassandra 1.0.7 it seems the problem has been
solved. One weird thing remains, on our 2 nodes (both 50% of the ring), the
first's usage is just over 25% of the second.
Anyone got an explanation for that?
2012/1/29 aaron morton
> Yes but…
>
> For every upgrade read the NE
A related question, is there any way to reverse a major compaction without
loosing performance? Do I just have to wait it out?
Micah Hausler
On Jan 30, 2012, at 7:50 PM, Roshan Pradeep wrote:
> Thanks Aaron for the perfect explanation. Decided to go with automatic
> compaction. Thanks again.
>
http://thelastpickle.com/2011/05/04/How-are-Memtables-measured/ - Gives some
background information (specific to 0.8 but still valid for 1.0 I believe).
Not quite sure why a warning message is logged but a ration of < 1 may occur
for column families with a very high update to insert ratio.
Dan
-
Created https://issues.apache.org/jira/browse/CASSANDRA-3819. Thanks!
Huy
> The schema change was that we created a new key space with composite type
> CFs, but later we had to change some definition/CF names, so we dropped
> the
> key space and recreated with new definition.
sounds like a b
but a ration of< 1 may occur
for column families with a very high update to insert ratio.
better to ask why minimum ratio is 1.0. What harm can be done with using
< 1.0 ratio?
I have been trying to figure out how to secure/encrypt the traffic between
the client (Hector) and the Cassandra Server. I looked at this link
https://issues.apache.org/jira/browse/THRIFT-106 But since thrift sits on a
layer after Hector, i am wondering how i can get Hector to use the right
Thrift
Hi,
I was mystified when I was not able to update a column ccc for a few keys in my
test_cf, but was able to update that for all other keys. Then, I noticed that
the column for that key is set to be deleted in future (year 6172 !) -
DEBUG [ReadStage:1191] 2012-01-31 22:21:48,374 SliceQueryFilte
Hello,
do you see any value in having a web service over cassandra, with actual
client-clients talking to it via https/ssl?
This way the cluster can be firewalled and therefore protected, plus you
get decent auth/auth right there.
Maxim
On 1/31/2012 5:21 PM, Xaero S wrote:
I have been try
Do you mean the load in nodetool ring is not even, despite the tokens been
evenly distributed ?
I would assume this is not the case given the difference, but it may be hints
given you have just done an upgrade. Check the system using nodetool cfstats to
see. They will eventually be delivered a
There is no way to reverse a compaction.
You can initiate a user compaction on a single file though, see nodetool (i
think) or the JMX interface.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 1/02/2012, at 4:10 AM, Micah Hausler wrote:
The ratio is the ratio of serialised bytes for a memtable to actual JVM
allocated memory. Using a ratio below 1 would imply the JVM is using less bytes
to store the memtable in memory than it takes to store it on disk (without
compression).
The ceiling for the ratio is 64.
The ratio is calcu
Send a delete with a higher time stamp, reduce the gc_grace_seconds on the CF,
get the CF to compact (manually or automatically) and then return the
gc_grace_seconds.
See the steps I took here to resolve a similar problem
http://thelastpickle.com/2011/12/15/Anatomy-of-a-Cassandra-Partition/
H
There was a recent post about performance that also talked about using Open VPN
to encrypt traffic from clients to server
http://www.mail-archive.com/user@cassandra.apache.org/msg20058.html
I've not looked at thrift encryption.
Cheers
-
Aaron Morton
Freelance Developer
@aaro
I added a row with a single column to my 1.0.8 single-node cluster:
RowKey: ----
=> (column=test, value=hi, timestamp=...)
I immediately deleted the row using both the CLI and CQL:
del Foo[lexicaluuid('----')];
dele
On Wed, Feb 1, 2012 at 12:58 AM, Todd Fast wrote:
> I added a row with a single column to my 1.0.8 single-node cluster:
>
> RowKey: ----
> => (column=test, value=hi, timestamp=...)
>
> I immediately deleted the row using both the CLI and CQL:
>
> del Foo[le
First, thanks! I'd read that before, but didn't associate doing a range
scan with using the CLI, much less doing "select count(*)" in CQL. Now I
know what to call the phenomenon.
Second, a followup question: So the row keys will be deleted after 1)
the GC grace period expires, and 2) I do a co
http://techblog.netflix.com/2012/01/announcing-astyanax.html
*
*
*What is Astyanax?*
Astyanax is a Java Cassandra client. It borrows many concepts from Hector
but diverges in the connection pool implementation as well as the client
API. One of the main design considerations was to provide a clean
a
Fixing the CC list
Regards,
On Tue, Jan 31, 2012 at 5:40 PM, Vijay wrote:
> http://techblog.netflix.com/2012/01/announcing-astyanax.html
> *
> *
> *What is Astyanax?*
> Astyanax is a Java Cassandra client. It borrows many concepts from Hector
> but diverges in the connection pool implementat
Thanks for the explanation.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/WARN-Memtable-live-ratio-tp7238582p7242021.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
I guess this is not really a WARN in that case.
On Tue, Jan 31, 2012 at 4:29 PM, aaron morton wrote:
> The ratio is the ratio of serialised bytes for a memtable to actual JVM
> allocated memory. Using a ratio below 1 would imply the JVM is using less
> bytes to store the memtable in memory than i
20 matches
Mail list logo
