Rehashing into a running cluster causes lock timeouts and lock cleanup errors

We are seeing some severe issues with a new node joining a cluster running transactions. Specifically, when a new node added to the system, some transactions running against the previous nodes will fail due to locks never being released. There will be a lot of lock timeouts as well.

All of our caches are in DIST mode. The number of owners is 3. We are also making liberal use of the new "eagerLockSingleNode" flag.

The attached test case illustrates the lock timeout problem.