Details
-
Improvement
-
Resolution: Won't Do
-
Major
-
None
-
1.0.3
-
Security Level: Public
-
None
Description
get(tmo) should not change the underlying state of the command to being timed out. It should simply respond with a TimeoutException but allow the command to continue.
Specifically, when the arg-tmo (timeout passed as an argument) expires, the underlying command is marked as timed out. For example, if one waits for 50ms on the command and a response has not been received within that time, the command is now dead ('TIMEDOUT', or similar) and waiting again will not help.
It is understandable that some code might rely on the old behavior, so at the very least, this should be documented in 'BIG RED LETTERS' in the get(tmo) method.
Attachments
Issue Links
- blocks
-
JCBC-114 Command Futures never receive results after rebalance-out (or other sorts of topology/network changes)
- Closed