Can you send us the stack trace which you can find in the hs_err_pid*.log?
is the system memory all used up (free)? any errors in the logs just before
the crash?
Regards,
On Mon, Mar 26, 2012 at 12:35 AM, Maciej Miklas
wrote:
> I have row cache - it's about 20GB big in this case.
> The proble
I have row cache - it's about 20GB big in this case.
The problem can be reproduced with our load test - we are using 20 reader
threads on single Cassandra node.
I will retest it with Java 6 - still it looks to me like JNA problem and
JDK in this case should not matter, but we will see.
On Thu, M
thanks - I will try it
On Thu, Mar 22, 2012 at 10:15 PM, Ben Coverston
wrote:
> Use a version of the Java 6 runtime, Cassandra hasn't been tested at all
> with the Java 7 runtime.
>
>
> On Thu, Mar 22, 2012 at 1:27 PM, Benoit Perroud wrote:
>
>> Sounds like a race condition in the off heap cachin
Use a version of the Java 6 runtime, Cassandra hasn't been tested at all
with the Java 7 runtime.
On Thu, Mar 22, 2012 at 1:27 PM, Benoit Perroud wrote:
> Sounds like a race condition in the off heap caching while calling
> Unsafe.free().
>
> Do you use cache ? What is your use case when you enc
Sounds like a race condition in the off heap caching while calling
Unsafe.free().
Do you use cache ? What is your use case when you encounter this error
? Are you able to reproduce it ?
2012/3/22 Maciej Miklas :
> Hi *,
>
> My Cassandra installation runs on flowing system:
>
> Linux with Kernel
What type of environment? We had issues with our cluster on 0.7.6-2 ... The
messages you see and highlighted, from what I recall aren't bad ... they are
good. Investigating our crash, it turns out that the OS killed our
Cassandra process and this was found in /var/log/messages
Since then, I have
What do you mean by crash ?
If there was some sort of error in cassandra (including java running out of
heap space) it will appear in the logs. Are there any error messages in the log.
If there was some sort of JVM error it will be outputted to std error and
probably end up on std out / conso
Hey Jonathan,
Thanks for the response. I applied the patch to 0.7.4 and things have
started working again nicely.
Looks like this fix is going in 0.7.5. Any idea when 0.7.5 will be released?
Thanks again!
On Wed, Mar 23, 2011 at 9:56 PM, Jonathan Ellis wrote:
> This looks like a bug
> (https://i
This looks like a bug
(https://issues.apache.org/jira/browse/CASSANDRA-2376), but not one
that would cause a crash. Actual process death is only caused by (a)
running out of memory or (2) JVM bugs.
On Wed, Mar 23, 2011 at 9:17 PM, Sanjeev Kulkarni wrote:
> Hey guys,
> I have a one node system(wit
I would scrub again w/ 0.7.4.
On Tue, Mar 15, 2011 at 6:38 PM, Sanjeev Kulkarni wrote:
> Hey Jonathan,
> Thanks for the reply.
> I was earlier running 0.7.2 and upgraded it to 0.7.3. Looks like I had to
> run the nodetool scrub command to sanitize the sstables because of the
> bloomfilter bug. I
Hey Jonathan,
Thanks for the reply.
I was earlier running 0.7.2 and upgraded it to 0.7.3. Looks like I had to
run the nodetool scrub command to sanitize the sstables because of the
bloomfilter bug. I did that and the Assert error went away but I'm getting
Java Heap Space Out of Memory error. I agai
Did you upgrade from an earlier version? Did you read NEWS.txt?
On Tue, Mar 15, 2011 at 4:21 PM, Sanjeev Kulkarni wrote:
> Hey guys,
> Have started facing a crash in my cassandra while reading. Here are the
> details.
> 1. single node. replication factor of 1
> 2. Cassandra version 0.7.3
> 3. Si
12 matches
Mail list logo
