cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kyle Gibson <kyle.gib...@frozenonline.com>
Subject Re: Occasionally getting old data back with ConsistencyLevel.ALL
Date Sat, 20 Aug 2011 03:20:40 GMT
The cron script doesn't do much. It pulls new IPNs (usually only 1 in
a given 5 minute period), inserts a row, and then sends an email.

As for failure handling in the script itself, I rely on python
exception handling, and whenever an exception occurs I do get an email
with the exception details. No such exception occurs when this
duplication occurs.

As for being SURE that the processed flag is set, no, I suppose I am
not 100% absolutely positive. I did try running the following: insert,
sleep for a second, get, check to see if it was set, if not, send me
an email and try setting it again. Sometimes this would work, and then
sometimes even the second insert would fail. Again, with no
exceptions.

Do you mean the cassandra log, or just logging in the script itself?

Thanks

On Fri, Aug 19, 2011 at 2:30 PM, Peter Schuller
<peter.schuller@infidyne.com> wrote:
>> Is it possible for instance that sometimes your cron job takes longer
>> than five minutes?
>
> Or just a lack of failure handling in the cron job for that matter.
> Are you *SURE* the the "processed" flag truly got set? Do you have a
> log statement (written *AFTER* successful write to Cassandra) that
> indicates the items you specifically say are processed twice, were in
> fact written twice to Cassandra?
>
> --
> / Peter Schuller (@scode on twitter)
>

Mime
View raw message