Jeff, good to hear from you.
Based on what you're saying, we can avoid regular repairs on these tables.
We can live with the read repairs because the bulk of these tables are
being used strictly for analytics queries by Spark jobs or for ad-hoc
queries by members of the technical team. They're no
> On Nov 5, 2020, at 10:18 AM, Mitch Gitman wrote:
>
Hi!
>
> Now, we could comfortably run all the repairs we need to within our off-hours
> window if we just left out all our tables that are insert-only. By
> insert-only, I mean that we have certain classes of tables that we're only
>
With all the years I've been working with Cassandra, I'm embarrassed that I
have to ask this question.
We have some tables that are taking longer to repair than we're comfortable
with. We're on Cassandra 3.11, so we have to run full repairs as opposed to
incremental repairs, which to my understand
