Hi Brian,
Happy to know that problem was (temporary?) solved.
We're migrating from i2.xl (32GB ram, Local SSD) to m4.xl (16gb, gp2) so we
> have a mix there, Cassandra JVM set to 10GB
To prevent these unpredictable mixes of hardware I use to update hardware
by adding a new data center, switchin
Thanks Thomas for clarifying.
After reading all the threads I see some possible work arounds for this issue.
I'm still not exactly sure what the recommended work around is for this issue
with 3x with multiple repairs. ???
Marshall
On 2017-10-07 10:41, "Steinmaurer, Thomas"
wrote:
> Mar
Marshall,
-pr should not be used with incremental repairs, which is the default since
2.2. But even when used with full repairs (-full option), this will cause
troubles when running nodetool repair -pr from several nodes concurrently. So,
unfortunately, this does not seem to work anymore and ma
On cassandra 3.11 were getting an error (see error below) when doing multiple
repairs with -pr option. Performing this type of repair worked fine on
Cassandra 2.x. My questions are:
Is this a valid operation (nodetool repair -pr .. simultaneously on
multiple nodes) to do?
If question
I now finished a implementation where I just save the pagination state to a
separate table and retrieve it to get to the next page.
So far it seems to work pretty well. But I have to do more thorough
testing.
Greetings.
On Wed 4. Oct 2017 at 19:42, Jon Haddad wrote:
> Seems pretty overengineere
