cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ronald Park <>
Subject Re: " (line 47) dropping message" errors
Date Sat, 21 Aug 2010 00:34:36 GMT
Oh, excellent.  Ok, my code does some retrying (including some sleep then
retry logic) when I get a TimedOut, so I think I'm actually just fine.
 Whew. :)   I had just noticed the dropped message in Cassandra's log today
but had seen the time outs in my log while it was running. I just didn't
connect the two together.

Thanks again,

On Fri, Aug 20, 2010 at 6:26 PM, Jonathan Ellis <> wrote:

> On Fri, Aug 20, 2010 at 5:02 PM, Ronald Park
> <> wrote:
> > Well this is bad news... Why is this logged only as a WARN?  Seems quite
> > SEVERE to me.
> That's as high as log4j goes, without going all the way to ERROR which
> we reserve for bugs.  (High load is not a bug.)
> > Fortunately for my app, I can go back to my source, recreate the data and
> > reload it at a slower rate (and cross my fingers that this rate is 'slow
> > enough')... unfortunately, it took me 20 hours to load the data (200M
> > records) at a rate of 3K/sec.  It looks like I only dropped about 600K
> > records out of 200M (.3%) ... but no way to tell which ones were dropped.
> :(
> Sure there is.  Your client will have gotten a TimedOutException if
> Cassandra wasn't able to meet your requested ConsistencyLevel.  And if
> it was, then no problem.

View raw message