On 03/27/2013 01:33 PM, Jukka Zitting wrote:
Hi,
On Tue, Mar 26, 2013 at 4:22 PM, Tudor Rogoz <[email protected]> wrote:
The attached tests (from the initial mail) will reproduce the issue on a
single mongo instance.
I tried running the test (without modifications, accessing a local
non-clustered mongod instance) a few times (killing it after ten or so
minutes) but couldn't yet reproduce the problem. Do you still see it
with the latest trunk?
I just made a pull, and is not reproducing on my side, too.It was probably
fixed somehow in the latest commits.
Thanks,
Tudor
BR,
Jukka Zitting
