keith-turner commented on PR #5375:
URL: https://github.com/apache/accumulo/pull/5375#issuecomment-2694919918
Made changes in 551dde0 to use mutliple connections per tserver in the
manager. Seeing parallelism on the tserver side w/ this change.
This behavior is making me wonder about connection pooling plus one way
messages. Maybe a situation like the following could happen, want to test this.
1. Client thread T1 get connection C1 from pool and send s a one way rpc
RPC1.
2. Tserver thread T2 starts processing RPC1
3. Client thread T1 returns C1 to pool, eveything up to this point took a
few ms.
4. Client thread T2 gets connection C1 and calls RPC2, however RPC2 will
block until RPC1 is done on tsever
5. Tserver thread T2 finishes processing RPC1 after 10 seconds and then
starts working on RPC2
6. Client thread T2 finishes RPC2 call after 10+ seconds. It was delayed
a by the previously submitted one way
It may be that a connection obtained from the pool could actually have
multiple one way messages queued on it that must be processed before it will
actually do anything.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
