Server: many locks found, blocking all operations (maybe on slow clients)
nicoloboschi opened this issue · 0 comments
nicoloboschi commented
JIRA: https://dev.blazingcache.org/jira/browse/BLAZ-14
Reporter: eolivelli @eolivelli
Comments from JIRA
Enrico Olivelli 2016-02-03T10:22:10.000+0100
The main cause is the lack of handlers for un-replied messages.
The fix introduces:
- better handling for channel close operations
- a new configuration option "slow.clients.timeout" (and runtime support for it) to impose a maximum timeout for clients to answer to messages, by default it will be 2 minutes (120000 ms)
Enrico Olivelli 2016-02-03T10:22:42.000+0100
Added JUnit test cases for this kind of errors and for bizantine clients who do not answer to fetch requests
Enrico Olivelli 2016-02-03T10:23:28.000+0100
Adding visibility of LocksManager in order to let embeeded servers to monitor locks