t;
> -
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 23/10/2012, at 8:19 PM, Jason Wee wrote:
>
> check 10.50.10.21 for what is the system load.
>
> On Tue, Oct 23, 2012 at 10:41 AM, Jason Hill wrote:
Hello,
I'm on version 1.0.11.
I'm seeing this in my system log with occasional frequency:
INFO [GossipTasks:1] 2012-10-23 02:26:34,449 Gossiper.java (line 818)
InetAddress /10.50.10.21 is now dead.
INFO [GossipStage:1] 2012-10-23 02:26:34,620 Gossiper.java (line 804)
InetAddress /10.50.10.21 is
Hello,
I'm using:
[cqlsh 2.0.0 | Cassandra 1.0.10 | CQL spec 2.0.0 | Thrift protocol 19.20.0]
I have a column family with a key that is a blob so I query it like this:
SELECT FIRST 10 1..1344385804 FROM WHERE KEY =
'436170616369747943616c63756c61746f727c33';
Is there any way to avoid the
Thanks Jonathan that did the trick. I deleted the Statistics.db files
for the offending column family and was able to get Cassandra to
start.
Thank you,
Jason
That's a good point Tyler. I watched Top during this process and even
though the heap dump is small, I can see all of my memory resources
consumed while Cassandra tries to start. I have the heap dump and can
run the Memory Analyzer Tool in Eclipse on it, but I will confess, I'm
not sure what I am l
Hello friends,
I'm getting a:
ERROR 22:50:29,695 Fatal exception in thread Thread[SSTableBatchOpen:2,5,main]
java.lang.OutOfMemoryError: Java heap space
error when I start Cassandra. This node was running fine and after
some server work/upgrades it started throwing this error when I start
the Ca
