Israel Fruchter
Israel Fruchter
Also if we have code that assume that taking a node down is immediately, that code part should be fixed (I don't think we have such delicate code)
@soyacz was trying it out in https://github.com/scylladb/scylla-cluster-tests/pull/6696 but for now we are dropping it, it's a bit more complicated than we estimated
@soyacz this was raise again in the context of doing scylla code coverage runs with SCT, and that we'll need to make sure we dump and save the coverage information...
> where coverage information is stored? we didn't yet have runs with it on SCT, we were discussing it with @eliransin, that recently pushed all of the support for that...
@soyacz it's not defined anywhere that it's not supported, so until then it should be working. on previous version it did work, this should be raise as core issue
not a SCT issue for sure
sounds like reconfiguration of the logging, something that was probably sovled by moving to syslog-ng in https://github.com/scylladb/scylla-cluster-tests/pull/4137 I don't know if that branch has those.
I've check and this branch is still using rsyslog, and we don't have a guard there to protect from configuration of logging multiple times, hence the multiple logs.
> should we try to backport #4137 to that branch? Good luck with that, it can take a while, since I don't know how many fixes to syslog-ng was on...
> > @pehala - @temichus is on PTO, please take it with someone in his team or just implement it: > > `rf_rack_valid_keyspaces: true` in scylla.yaml , it's important for...