I think it is fair to run a flakey test again. If it is determine it flaked
out due to a conflict with another test or something ephemeral in a long
process it is not worth blocking a release.
Just deleting it is probably not a good path.
I actually enjoy writing fixing, tweeking, tests so pinge
It isn’t, but you are supposed to change it.
The reason it cannot be set higher by default is that out of the box
single-node clusters should still work,
and setting the default RF to higher than 1 would break this, as it performs
some queries at quorum CL.
--
AY
On 3 December 2016 at 06:47:1
Yup the core issue is that system_auth is not great from a HA perspective
at the moment for new users.
Given the general opinion is that RF=N is not appropriate / too rife for
abuse. Would something similar to min(rf=N, X per DC) be more appropriate?
The only thing with that is implementing that r
Yes. There really isn't a good answer for this at the moment. Unless we
implement some kind of staged node addition process where you can add an entire
set of nodes at once (we discussed some ideas at NGCC two years ago, but I
don't think it has gone anywhere) you run into problems with any stra
