Excuse me if I jump into an old thread, but from my experience, I have a
very clear opinion about situations like that as I encountered them before:
Tests are there to give *certainty*.
*Would you like to pass a crossing with a green light if you cannot be sure
if green really means green?*
Do you
Hi,
I dont see any any update on this thread. We will go ahead and make
Dtest a blocker for cutting releasing for anything after 3.10.
Please respond if anyone has an objection to this.
Thanks,
Sankalp
On Mon, Nov 21, 2016 at 11:57 AM, Josh McKenzie
wrote:
> Caveat: I'm strongly in favor
The point Ben is saying is that for auth keyspace, default of RF=1 is not
good for any type of cluster whether it is small or large.
Hi,
In reply to Dikang Gu:
For the run where we incorporated the change from CASSANDRA-11571 the
stack trace was like this (from JMC):
*Stack Trace* *Sample Count* *Percentage(%)*
org.apache.cassandra.db.compaction.LeveledCompactionStrategy.getNextBackgroundTask(int)
229 11.983
-org.apach
As I haven't received a single reply on that, I went over to implement and
test it on my own with our production cluster. I had a real pain with
bringing up a new node, so I had to move on.
Result:
Works like a charm. I ran many dtests that relate in any way with storage,
stream, bootstrap, ... wi
