ChaosMonkey with one destructive and one volatility (flush-compact-split-etc.) threads steps on its own toes and logs a lot of exceptions.
A simple solution would be to catch most (or all), like NotServingRegionException, and log less (not a full callstack for example, it's not very useful anyway).
A more complicated/complementary one would be to keep track which regions the destructive thread affects and use other regions for volatile one.
|Field||Original Value||New Value|
|Assignee||Sergey Shelukhin [ sershe ]|
|Status||Open [ 1 ]||Patch Available [ 10002 ]|
|Status||Patch Available [ 10002 ]||Resolved [ 5 ]|
|Fix Version/s||0.99.0 [ 12325675 ]|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||0.98.0 [ 12323143 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|3d 6h 43m||1||Sergey Shelukhin||20/Dec/13 01:40|
|7d 5h 13m||1||Sergey Shelukhin||27/Dec/13 06:54|
|421d 16h 38m||1||Enis Soztutar||21/Feb/15 23:32|