Roy Dahan
Roy Dahan
@dkropachev please check if we want to add some documentation about previous behavior vs new. Then, we can close this one.
I don't think it's related to warmup. @Annamikhlin do you see a correlation between the failures and the host/s the test ran on?
+1 for your work. One more thing we need to understand in this task if it makes sense that we can't run this test with disruptive nemesis. If we maintain...
Sounds like a good idea to me. I think there was such a task long ago on Shlomo's backlog but he never reached it.
Actually I meant @dkropachev as he implements the client side of it and I wanted him to review and provide his feedback.
If this issue isn't progressing anywhere, I suggest we will remove create_index nemesis from parallel_schema_topology_changes scenarios. Any objections?
Ok, so meanwhile I'll add a SkipPerIssue for create_index as part of parallel nemesis. BTW, we don't have in these cases create_MV because it's defined as disruptive (doing reboot in...
We need to think what to do in the case when we terminate a node and expect it to be almost immediate operation. If it adds a significant amount of...
Let's try to have a quick implementation only for coverage collection. It's a 60MB file, should be fairly quick. (We also need to make sure we dump the metrics before...
Every 3 weeks.