Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
MapExecuteOnKeyRequest should reference requester's threadId #5857
ClientMapProxy and MapProxyImpl differ slightly in behaviour for the following methods:
In MapProxyImpl, these create an EntryOperation with the threadId set. This does not happen with ClientMapProxy. MapExecuteOnKeyRequest should hence take a threadId and set this on the generated EntryOperation.
This matters when a process explicitly locks a key in a distributed map, and then proceeds to invoke executeOnKey or submitToKey. This will work without issue for full members for the reasons described above, but may not work for clients.