Hi Everyone, This is a modest user-facing feature that I want to highlight in case anyone has any input. In order to validate if a real cluster may modify its topology or consistency level (e.g. from local to global), this ticket introduces a facility for injecting latency to internode messages. This is particularly helpful for high-availability topologies, and in particular for LWTs (where performance may be unpredictable due to contention), so that real traffic may be modified to experience gradually increasing latency in order to validate a topology (or the impact of a global consistency level) before any transition is undertaken.
The user-visible changes include new config parameters, new JMX end points for modifying these parameters, and new consistency levels that may be supplied to mark queries as suitable for latency injection (so that applications may nominate queries for this mechanism)
