Combining eagerLockSingleNode with the KeyAffinityService
Combining eagerLockSingleNode with the KeyAffinityService can bring some interesting advantages. The next diagram shows this:  By using KeyAffinityService one can generate keys that would always map to the local node. If eagerLockSingleNode=true, then the remote lock acquisition happens locally: this way one can benefit from eager locking semantics and having the same performance as non eager locking. The optimisation is affected by cluster topology changes, so keys might get relocated. But for clusters where topology changes are rather rare this can bring a lot of value.