Do you actually see the update occur if you wait for 10 seconds (as your subject implies), or do you just see intermittent failures when running the unit test? If it's the latter, are you sure that the update has a greater timestamp than the insert? I've seen similar unit tests fail because because the timestamp values were the same.
Jim On Mon, Sep 26, 2011 at 2:55 PM, Rick Whitesel (rwhitese) < rwhit...@cisco.com> wrote: > Hi All:**** > > ** ** > > We have a simple junit test that inserts a column, immediately updates that > column and then validates that the data updated. Cassandra is run embedded > in the unit test. Sometimes the test will pass, i.e. the updated data is > correct, and sometimes the test will fail. The configuration is set to:*** > * > > ** ** > > <CommitLogSync>periodic</CommitLogSync> and > <CommitLogSyncPeriodInMS>10000</CommitLogSyncPeriodInMS>**** > > ** ** > > We are running version 0.6.9. We plan to update to the latest version but > cannot until after the release we are wrapping up. We are using the client > batch mutate to create and update the data. From what I understand, the > commit log write will return immediately and the data will be store in > memory. If that is the case, then why would our test sometimes fail?**** > > ** ** > > -Rick Whitesel**** > > ** ** > > **** > > *Simplify, Standardize and Conserve***** > > ** ** > > ** ** > > [image: cid:01608604-FE45-42D2-AACA-4C66FCE5AB8C@cisco.com]**** > > ** ** > > *Rick Whitesel* > *Technical Lead* > *Customer Contact Business Unit** > * > rwhit...@cisco.com <nordb...@cisco.com> > Phone :*978-936-0479***** > > > 500 Beaver Brook Road > Boxboro, MA 01719 > Mailing address: > 1414 Massachusetts Avenue > Boxboro, MA 01719 > United States > www.cisco.com**** > > ** ** > > ** ** >
<<image001.gif>>
