News for hackers. Stuff that matters.

A comment on Ways to shoot yourself in the foot with Redis. Parent comment

Re:Ways to shoot yourself in the foot with Redis by Racing0461 on Saturday July 29, 2023 @08:21PM (#36926332)
> falsely concludes

i disagree here. instance b did the right thing given the information it has. instance a should realize it no longer owns the lock and stop proceeding. but in reality it also signifies concurrency based limitations in the api itself (no ability to perform a do and then commit call). https://microservices.io/patterns/data/saga.html

[ Parent | on HN ]
Re:Ways to shoot yourself in the foot with Redis by 8organicbits on Saturday July 29, 2023 @10:44PM (#36927306)
I think we both agree that A did something wrong and that B followed the locking algorithm correctly. "Falsely" refers to a matter of fact: A is not dead.

You're right that A could try to stop, but I think it's more complicated than that. A is calling a third party API, which may not have a way to cancel an in-flight request. If A can't cancel, then A should refresh its claim on the lock. A must have done neither in the example.

[ Parent | on HN ]