please send an empty email to: user-unsubscr...@cassandra.apache.org to
unsubscribe yourself from the list.
regards.
Greg Bone wrote:
-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands,
Not in 3.11, though 4.0 adds preview repair which can sorta do this if
you're also running incremental repair.
Just run nodetool repair, use subranges if needed. If you stream data,
they're out of sync. If you don't stream data, they're in sync.
On Thu, Jul 9, 2020 at 3:16 PM Jai Bheemsen Rao
Hello,
I am trying to expand my C* cluster to a new region, followed by keyspace
expansion and nodetool rebuild -- sourceDC.
Once the rebuild process is complete, is there a way to identify if all the
data between two regions is in sync? Since the data size is large, I
cannot run select count(*).
Hi,
On behalf of the DataStax drivers team, I would like to announce the first
alpha release of the Quarkus extension for Apache Cassandra® [1].
The extension has been included in Quarkus Platform 1.6, released yesterday;
which means that you can now generate an application on code.quarkus.io
On Thu, Jul 9, 2020 at 9:02 AM Oleksandr Shulgin <
oleksandr.shul...@zalando.de> wrote:
> On Thu, Jul 9, 2020 at 5:54 PM Gil Ganz wrote:
>
> Another question, did changing the compaction strategy from one twcs to
>> the other trigger merging of old sstables?
>>
>
> I don't recall any unexpected
You could also pull TWCS out of the version of Cassandra you want to
deploy, fix the imports and change the package name. Then you've got the
same version as OSS, just under the name you're using in 2.1. Once you've
moved to 3.11, you can switch to the OSS version.
On Thu, Jul 9, 2020 at 9:09
Great, thank you very much!
On Thu, Jul 9, 2020 at 7:02 PM Oleksandr Shulgin <
oleksandr.shul...@zalando.de> wrote:
> On Thu, Jul 9, 2020 at 5:54 PM Gil Ganz wrote:
>
>> That sounds very interesting Alex, so just to be sure I understand, it
>> was like this
>> 1 - you had 2.1 cluster running
On Thu, Jul 9, 2020 at 5:54 PM Gil Ganz wrote:
> That sounds very interesting Alex, so just to be sure I understand, it was
> like this
> 1 - you had 2.1 cluster running with the 2.1 version jar
> 2 - you upgraded to 3.0, starting the cluster with the 3.0 version jar
> that has the same strategy
That sounds very interesting Alex, so just to be sure I understand, it was
like this
1 - you had 2.1 cluster running with the 2.1 version jar
2 - you upgraded to 3.0, starting the cluster with the 3.0 version jar that
has the same strategy name
3 - you changed the compaction strategy to use the
On Thu, Jul 9, 2020 at 3:38 PM Gil Ganz wrote:
> Hey
> I have a 2.11.4 cluster with tables that are defined with twcs, using
> jeff's jar
>
> https://github.com/jeffjirsa/twcs
>
> All working great, but now I want to upgrade to 3.11, and I have a
> problem, cassandra won't start, it fails on the
Hey
I have a 2.11.4 cluster with tables that are defined with twcs, using
jeff's jar
https://github.com/jeffjirsa/twcs
All working great, but now I want to upgrade to 3.11, and I have a problem,
cassandra won't start, it fails on the following error
ERROR [main] 2020-07-09 13:30:29,823
12 matches
Mail list logo
