How to do distributed locking (2016)

Re:How to do distributed locking (2016) by FooBarWidget on Saturday May 13, 2023 @02:42AM (#35926196)

I don't know why you say neither group understands each other when I literally said in my comment that my approach is probabillistic.

Also, how is configuring an infinite timeout (and checking whether the client is actually gone before manually breaking the lock lease) not an absolute guarantee?

[ Parent | on HN ]

Re:How to do distributed locking (2016) by klysm on Saturday May 13, 2023 @04:47PM (#35932543)

I guess it’s an absolute guarantee, but you lose liveness unless there is some other party handling those cases where the client is truly gone

[ Parent | on HN ]

Re:How to do distributed locking (2016) by diggs on Sunday May 14, 2023 @03:15AM (#35936029)

An infinite timeout works in theory, but it is impractical at scale.

[ Parent | on HN ]

Re:How to do distributed locking (2016) by FooBarWidget on Monday May 15, 2023 @03:05PM (#35953069)

Okay but then I really don't know what point you're trying to make. Either an infinite timeout, or non-absolute mutual exclusion guarantee: we have to pick either one. The right choice depends on the workload. There is no perfect solution that lets you have your cake and eat it too.

[ Parent | on HN ]