Yep, and the author even (briefly) describes it. But you can&#x27;t do it without moving some of the logic into the storage service, to check fencing tokens. Zookeeper exposes various kinds of IDs that can be used to do fencing; apparently (I haven&#x27;t read the details) Redlock doesn&#x27;t.<p>Interestingly, even though HBase uses Zookeeper for coordination, it does <i>not</i> use it for fencing. Instead, fencing is handled by atomic &quot;log-rolling&quot; operations on the HDFS namenode, which can be configured to use its own quorum-based journal.  (The equivalent of a &quot;token&quot; is the monotonically-increasing namenode operation sequence number.) So the principle is the same: the system responsible for doing mutual exclusion, and the system that actually stores the data, must be coupled.