News for hackers. Stuff that matters.

A comment on Jepsen: MongoDB 4.2.6. Parent comment

Re:Jepsen: MongoDB 4.2.6 by fendy3002 on Sunday May 24, 2020 @07:41PM (#23295982)
Not op, I think what he means is the session, even when already failed once, can still be used (without error) in the next operation without being invalidated.

Without promise.all, I think it can be replicated like this:

    try{
      await someOp(session);
    catch { }
    await someOtherOp(session);
He expected what the session to be invalidated during someOtherOp.
[ Parent | on HN ]
Re:Jepsen: MongoDB 4.2.6 by inglor on Monday May 25, 2020 @04:56AM (#23299317)
That is correct and what I meant. Thanks, and there doesn't have to be a `try/catch` because it is possible to "fork" control with promises.

They implemented a "disposer" incorrectly (I added this to several other libraries and made a Q&A about it here https://stackoverflow.com/questions/28915677/what-is-the-pro... )

[ Parent | on HN ]