After a rather painful debugging/db-restoring session, SmalltalkHub is back online! So...what happened? Well, the db got currupted due to a concurrency issue, which is now fixed [1], resulting in very unstable behavior. Fixing the issue and restoring the db got SmalltalkHub back on track. Did I lose any data? Nope. What's next? I'll keep a close eye on the DB for the coming days and make sure it runs smoothly. Cheers, Nico [1] http://smalltalkhub.com/#!/~NicolasPetton/SmalltalkHub/diff/Hub-NicolasPetto...

thanks Nicolas! Yes doing is always more difficult than the rest :) Stef On Jan 15, 2013, at 1:01 AM, Nicolas Petton wrote:

After a rather painful debugging/db-restoring session, SmalltalkHub is back online!

So...what happened?

Well, the db got currupted due to a concurrency issue, which is now fixed [1], resulting in very unstable behavior. Fixing the issue and restoring the db got SmalltalkHub back on track.

Did I lose any data?

Nope.

What's next?

I'll keep a close eye on the DB for the coming days and make sure it runs smoothly.

Cheers, Nico

[1] http://smalltalkhub.com/#!/~NicolasPetton/SmalltalkHub/diff/Hub-NicolasPetto...

Sure, the issue was that SMalltalkHub was using a session from a session pool and putting the session back to the pool while still using it for uploads. So the issue was not because of Mongo itself. Cheers, Nico "Esteban A. Maringolo" <emaringolo@gmail.com> writes:

Great Nicolas, thank you.

But the least I would expect is MongoDB to have concurrency issues! Can you give more details about it?

Regards!

-- View this message in context: http://forum.world.st/SmalltalkHub-update-tp4663339p4663485.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

-- Nicolas Petton http://nicolas-petton.fr