Sam, Entry processor is indeed executed within a lock, this is required to achieve atomicity. So if there is high contention on a single key, requests will wait for each other. And this is yet another reason to make entry processor implementation as lightweight as possible so that it does not acquire lock for a long time.
Scan query should not fail with an exception if there is a concurrent update. Do you have the trace? -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
