You can always go as suggested by the error message, check the cassandra syslog and collect information about the repair activity.
$ cd /var/log/cassandra/ $ cat system.log | grep repair
Please note that I am testing for some purposes cassandra 2.1.15 and still run into a problem. Since the consideration, since this is not a serious mistake, does not affect the repair process, I think that it will be adhered to for some time.
source share