Dear Cassandra developers, we are developing a tool to detect exception-related bugs in Java. Our prototype has spotted the following throw statement whose exception class and error message indicate different error conditions.
Version: Cassandra-3.11 (commit: 123113f7b887370a248669ee0db6fdf13df0146e)
RuntimeException is usually used to represent errors in the program logic (think of one of its subclasses, NullPointerException), while the error message indicates that an interrupt has occurred. This mismatch could be a problem. For example, the callers may miss the possibility that StorageService.rebuild() can be interrupted because it does not throw any InterruptedException. Or, the callers trying to handle other RuntimeException may accidentally (and incorrectly) handle the interrupt.
If throwing a RuntimeException is preferred, maybe it can wrap the cause exception so that the inner call stack is preserved.