On Tue, Nov 1, 2011 at 6:36 AM, Rusty Klophaus wrote:
> Whew, that is some top-shelf debugging. Glad to hear you were able to
> track down the issue.
>
Fix at https://github.com/igrigorik/em-synchrony/pull/79. After that
change it all works nicely.
Elias
___
Hi Elias,
Whew, that is some top-shelf debugging. Glad to hear you were able to track
down the issue.
Best,
Rusty
On Tue, Nov 1, 2011 at 1:49 AM, Elias Levy wrote:
> On Mon, Oct 31, 2011 at 11:14 PM, Elias Levy
> wrote:
>
>> On Mon, Oct 31, 2011 at 2:01 PM, Rusty Klophaus wrote:
>>
>>> Thank
On Mon, Oct 31, 2011 at 11:14 PM, Elias Levy wrote:
> On Mon, Oct 31, 2011 at 2:01 PM, Rusty Klophaus wrote:
>
>> Thanks for your excellent description of the problem. We haven't seen
>> this before to my knowledge, and this isn't expected behavior.
>> Also, if you can share your code, or if you
On Mon, Oct 31, 2011 at 2:01 PM, Rusty Klophaus wrote:
> Thanks for your excellent description of the problem. We haven't seen this
> before to my knowledge, and this isn't expected behavior.
> Also, if you can share your code, or if you have a small script that can
> reproduce the failure, that
Hi Elias,
Thanks for your excellent description of the problem. We haven't seen this
before to my knowledge, and this isn't expected behavior.
Can you answer a few questions to help us troubleshoot?
- Can you send me the exact error message you saw when the client failed
to deserialize the
I am finding that there appears to be some sort of race condition when
reading recently written objects (as in concurrently). I am using Riak
1.0.0 with the leveldb backend through the multi backend in a 3 node
cluster. Writes are done with W=2 and reads with R=2. The client is using
the riak cl
