On Thu, Apr 21, 2011 at 10:49 AM, George P. Stathis <gstat...@traackr.com> wrote: > I gave the thread that name because that was the best way I could come up > with to describe the symptoms. We still have the problem, it just may end up > be timestamp related after all. >
No worries. > This does look similar, yes. I see there is no resolution currently. Well, if your use case is really to Put and Delete the same stuff right after the other, then yeah you will need a time resolution that more precise than milliseconds. Or you pass your own timestamps by doing the first puts are current time, then delete at current time +1, then put again if you want at current time +2, etc. > > We have also noticed this problem in our local systems (laptops) but > actually much less frequently. I'll check the EC2 dates as soon as AWS > recovers (http://twitter.com/#!/search/%23aws). Our dev setup is currently > hosed... Heh :P J-D
