Details
-
Bug
-
Resolution: Won't Do
-
Major - P3
-
None
-
*Location*: https://docs.mongodb.org/manual/tutorial/perform-two-phase-commits/
*User-Agent*: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36
*Referrer*: https://docs.mongodb.org/manual/tutorial/analyze-query-plan/
*Screen Resolution*: 1366 x 768
*repo*: docs
*source*: tutorial/perform-two-phase-commits
*Location*: https://docs.mongodb.org/manual/tutorial/perform-two-phase-commits/ *User-Agent*: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36 *Referrer*: https://docs.mongodb.org/manual/tutorial/analyze-query-plan/ *Screen Resolution*: 1366 x 768 *repo*: docs *source*: tutorial/perform-two-phase-commits
Description
Hello,
I think there's some inconsistency in this topic.
If first applications, let's name it "app1" finds a transaction (t1) with state set to "initial" and the second application (app2) does so at the same time, then the next step (updating balance at source/destination) will be performed twice.
And here again, there's no guarantee that app1 will finish this step before app2 (cause it doesn't include "$isolated"), so the balance may be changed two times.
Best regards,
Pawel