Romain Hardouin

As you can see, C*2.0 compatibility is kept: C*2.1 ``` >>> table_name_with_uuid = 'mytable-15165f11e3f634af9d3afacf98868599' >>> table_name = table_name_with_uuid.split('-')[0] >>> table_name 'mytable' ``` C*2.0 ``` >>> table_name_with_uuid = 'mytable' >>> table_name...

Snapshotting a table doesn't work with C*2.1 because of UUID (it works for whole keyspace). If we want to handle both 2.0 & 2.1 naming we can drop the `-`:...

Hi @efeg We've split our workload into multiple Kafka clusters (roughly one cluster per service instead of having one big cluster with non-spanning topics). In each cluster, each topic spans...

Hey sorry for the delay, it's been a while since [I pushed a draft on our fork ](https://github.com/linkedin/cruise-control/compare/master...teads:topic_leader_replica_distribution_goal__chm), I still have to: - make all tests green - make the...

@amuraru Unfortunately I wasn't able to put more time on it since my last commit

@amuraru Yes some help would be welcome :pray:

@bpux There is no silver bullet: sometimes we run the goal alone sometimes we can add another goal but usually we use multiple passes (we tend to do that without...

I see two options: 1. Generate safe command lines with sensitive data stripped out prior to log them 2. Use a specific logger Formatter that uses a regex to replace...

Rebased from trunk + formatting in a separate commit