cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-4841) Exception thrown during nodetool repair -pr
Date Mon, 22 Oct 2012 18:34:14 GMT


Jonathan Ellis resolved CASSANDRA-4841.

    Resolution: Invalid

Sounds like you were GC storming then.  Grep for GCInspector or top compared with thread IDs
could confirm this.

Often this happens because sstable structures outgrew the space Cassandra reserves for it
in the heap.  You can reduce these with the (global) index_interval and (per-CF) bloom_filter_fp_chance
settings.  Unfortunately Cassandra is not yet able to self-tune this.
> Exception thrown during nodetool repair -pr
> -------------------------------------------
>                 Key: CASSANDRA-4841
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.6
>         Environment: Ubuntu 12.04 x64, 32GB RAM
>            Reporter: Michael Kjellman
>            Priority: Critical
> During a nodetool repair -pr an exception was thrown.
> root@scl-cas04:~# nodetool repair -pr
> Exception in thread "main" java.rmi.UnmarshalException: Error unmarshaling return header;
nested exception is:
>         at sun.rmi.transport.StreamRemoteCall.executeCall(
>         at sun.rmi.server.UnicastRef.invoke(
>         at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
>         at Source)
>         at$RemoteMBeanServerConnection.invoke(
>         at
>         at $Proxy0.forceTableRepairPrimaryRange(Unknown Source)
>         at
>         at
>         at
> Caused by:
>         at
>         at sun.rmi.transport.StreamRemoteCall.executeCall(
>         ... 9 more
> Logs:
> WARN 20:53:27,135 Heap is 0.9710037912028483 full.  You may need to reduce memtable and/or
cache sizes.  Cassandr
> a will now flush up to the two largest memtables to free up memory.  Adjust flush_largest_memtables_at
threshold i
> n cassandra.yaml if you don't want Cassandra to do this automatically
> regardless of configuration issues a repair shouldn't crash a node.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message