What happens when a leader goes dormant due to an event like GC and comes back up after its lock has expired? It will still assume it is the leader. Now you'll have two leaders in the cluster. Consul's LockIndex can be used as fencing tokens to solve this problem. But I don't think the current implementation addresses this issue.