News for hackers. Stuff that matters.

A comment on How to Do Distributed Locking (2016).

Re:How to Do Distributed Locking (2016) by DigitalTerminal on Thursday June 20, 2019 @04:08AM (#20230874)
In Azure, we solve this with leasing blobs and always renewing, and additionally checking ETags when writing.
[ Parent | on HN ]
Re:How to Do Distributed Locking (2016) by tybit on Thursday June 20, 2019 @04:18AM (#20230919)
That’s cool. S3 is generally fantastic but as far as I know has no similar option to this. I wonder if they’ll ever have a strong consistency mode.
[ Parent | on HN ]
Re:How to Do Distributed Locking (2016) by appwiz on Thursday June 20, 2019 @07:23AM (#20231692)
Within AWS, consider DynamoDB with the fantastic DynamoDB Lock Client[1]. It’s a “general purpose distributed locking library built on top of DynamoDB. It supports both coarse-grained and fine-grained locking.”

  [1] https://github.com/awslabs/dynamodb-lock-client
[ Parent | on HN ]
Re:How to Do Distributed Locking (2016) by ts330 on Thursday June 20, 2019 @05:09AM (#20231117)
interested to know your approach to long leases lasting more than 60 seconds (if you have this?). do you go for continual renewing (and bailing out if you get too close to the timeout without getting a renewal). or do you go for infinite with your own break logic?
[ Parent | on HN ]