Alexander Dejanovski
Alexander Dejanovski
There's dynamic sizing happening based on the data size in each DC. We should set a minimum size though to avoid such renderings.
I agree we should get rid of those to avoid confusion. Adding this issue to the backlog.
We happily accept PRs 😉
@fzhougithub, may I recommend to upgrade to a later Cassandra version, even if in the 2.1.x branch? There are multiple issues with 2.1.8, many related to repairs specifically.
Yes, we'd need to catch this type of exception and stop the repairs that are scheduled for a keyspace that doesn't exist anymore.
Hi @shalomsagges, are you still affected by this issue?
This is rather a Shiro issue IMO, but we could indeed possibly output a message.
Actually, we went into some efforts to display times in the local TZ in the UI 😅 I guess we could have a setting added to make everything displayed in...
Fair enough. I guess we can indicate that the timezone is local by default and allow users to set the times to UTC in the UI.
You'll find a sample in the documentation that will show you how to pass credentials to the driver in Reaper: http://cassandra-reaper.io/docs/configuration/backend_specific/ ``` cassandra: clusterName: "test" contactPoints: ["127.0.0.1"] port: 9042 keyspace:...