I ran with the latest from the 1.2 branch, and although the NPE and index out
of bounds exception went away, these still stuck around.
I'll see if I can figure out something to put into JIRA...
On Jul 25, 2013, at 12:32 AM, Sylvain Lebresne wrote:
> Obvisously, that should not happen. That bei
Obvisously, that should not happen. That being said, we did fix a bug
yesterday that could produce that kind of trace:
https://issues.apache.org/jira/browse/CASSANDRA-5799. It will be part of
1.2.7 that should be released tomorrow, though the artifacts that are being
voted on are at
https://reposit
It is pretty much every row that hits the large threshold. I don't think I can
delete every row that hits that…
you can see the db size in the stack trace, do you want a different type of
size?
On Jul 24, 2013, at 11:07 AM, Jason Wee wrote:
> Would it possible to delete this row and reinsert
Would it possible to delete this row and reinsert this row? By the way, how
large is that one row?
Jason
On Wed, Jul 24, 2013 at 9:23 AM, Paul Ingalls wrote:
> I'm getting constant exceptions during compaction of large rows. In fact,
> I have not seen one work, even starting from an empty DB.
I'm getting constant exceptions during compaction of large rows. In fact, I
have not seen one work, even starting from an empty DB. As soon as I start
pushing in data, when a row hits the large threshold, it fails compaction with
this type of stack trace:
INFO [CompactionExecutor:6] 2013-07-
