grep for Entry-28-Index.db in the logs, see what was going on before
the exceptions. (was it compacted?)
On Sat, May 15, 2010 at 12:43 AM, Mason Hale wrote:
> One of our Cassandra nodes is throwing multiple of these errors:
> ERROR [ROW-READ-STAGE:185] 2010-04-27 14:56:59,543 CassandraDaemon.jav
Sounds like you changed your partitioner type after it already had
data from the old one in it.
On Fri, May 14, 2010 at 6:12 PM, AJ Chen wrote:
> when starting cassandra, there is "Keys must be written in ascending order."
> error. and, when my application reads the datastore, it throws outofmem
rpctimeout should be sufficient
you can turn on debug logging to see how long it's actually taking the
destination node to do the write (or look at cfstats, if no other
writes are going on)
On Fri, May 14, 2010 at 11:55 AM, Sonny Heer wrote:
> Hey,
>
> I'm running a map/reduce job, reading from
Oh, very interesting. I assumed Hadoop would be smart enough to
load-balance the jobs it sends out. Guess not.
Can you submit a patch?
On Wed, May 12, 2010 at 12:32 PM, Joost Ouwerkerk wrote:
> I've been trying to improve the time it takes to map 30 million rows using a
> hadoop / cassandra cl
