Details
-
Improvement
-
Status: Resolved
-
Low
-
Resolution: Not A Problem
-
None
-
None
Description
There are a lot of catch-wrap-throw pattern occurances in code with InterruptedException. I cleaned up some of them but not all - in some places I don't know enough about code to decide if it's correct thing to do.
Important: I also fixed possibility of wrong behaviour in case of spurious wakeup in AsyncOneResponse.
Attachments
Attachments
Issue Links
- is related to
-
CASSANDRA-5557 Correctly handle interruptions of Thread.sleep()
- Resolved
- is superceded by
-
CASSANDRA-5690 Fix AsyncOneResponse
- Resolved
This changes the semantics of what was going on. I can see using Futures.getUnchecked etc, to clean the code up some. I'm not sure I understand the intention of this patch, as it makes this non interruptable, which is completely different, and to me seems wrong. But perhaps it went over my head.