cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tristan Seligmann (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4832) AssertionError: keys must not be empty
Date Fri, 19 Oct 2012 00:08:04 GMT


Tristan Seligmann commented on CASSANDRA-4832:

I modified my application to avoid inserting the empty column in question (which was a bug
anyway; if that particular column was empty, the application should not have been doing an
insert at all) and the problem has gone away, so it seems like my hypothesis is at least partially
correct. I'm going to attempt to reproduce this in a more controlled environment now that
my immediate issue in production has been resolved.
> AssertionError: keys must not be empty
> --------------------------------------
>                 Key: CASSANDRA-4832
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.1.6
>         Environment: Debian 6.0.5
>            Reporter: Tristan Seligmann
> I'm getting errors like this logged:
>  INFO 07:08:32,104 Compacting [SSTableReader(path='/var/lib/cassandra/data/Fusion/quoteinfo/Fusion-quoteinfo.quoteinfo_search_value_idx-hf-114-Data.db'),
> ERROR 07:08:32,108 Exception in thread Thread[CompactionExecutor:5,1,main]
> java.lang.AssertionError: Keys must not be empty
>         at
>         at
>         at org.apache.cassandra.db.compaction.CompactionTask.execute(
>         at org.apache.cassandra.db.compaction.CompactionManager$1.runMayThrow(
>         at
>         at java.util.concurrent.Executors$
>         at java.util.concurrent.FutureTask$Sync.innerRun(
>         at
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at
> I'm not really sure when this started happening; they tend to be logged during a repair
but I can't reproduce the error 100% reliably.

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