Re: Unsubscribe
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, e-mail: user-h...@cassandra.apache.org
Re: Validate data consistency after nodetool rebuild
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 Dhanwada < jaibheem...@gmail.com> wrote: > 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(*). Is there a better way to validate? > > C* Version : 3.11.X >
Unsubscribe
Validate data consistency after nodetool rebuild
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(*). Is there a better way to validate? C* Version : 3.11.X
Quarkus extension for Apache Cassandra alpha release
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 [2] and start coding your reactive Apache Cassandra application in just a few clicks. We cover the extension's main features in a Quarkus blog post [3] published yesterday. We were also kindly invited to present our work during the Quarkus Hackathon Office Hours event yesterday [4]. The extension is available on Maven Central [5]. The code is open-source, Apache-licensed and available on GitHub [6]. Try it out and please don’t hesitate to open feature requests and bug reports there [7]. Thanks, Alex Dutra [1] https://quarkus.io/guides/cassandra [2] https://code.quarkus.io/ [3] https://quarkus.io/blog/quarkus-cassandra-extension-released/ [4] https://www.youtube.com/watch?v=vyq_sEKN7NY [5] https://search.maven.org/search?q=g:com.datastax.oss.quarkus [6] https://github.com/datastax/cassandra-quarkus [7] https://github.com/datastax/cassandra-quarkus/issues - To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
Re: Upgrading cassandra cluster from 2.1 to 3.X when using custom TWCS
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 action from changing the strategy, but of > course you should verify on a test system first if you have one. > > Should be exactly the same between the two, AFAIK. (Sorry my repo may not work on modern 3.0/3.11 branches.)
Re: Upgrading cassandra cluster from 2.1 to 3.X when using custom TWCS
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 AM Gil Ganz wrote: > 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 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 built in one? >>> >> >> Correct. >> >> Another question, did changing the compaction strategy from one twcs to >>> the other trigger merging of old sstables? >>> >> >> I don't recall any unexpected action from changing the strategy, but of >> course you should verify on a test system first if you have one. >> >> Cheers, >> -- >> Alex >> >>
Re: Upgrading cassandra cluster from 2.1 to 3.X when using custom TWCS
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 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 built in one? >> > > Correct. > > Another question, did changing the compaction strategy from one twcs to >> the other trigger merging of old sstables? >> > > I don't recall any unexpected action from changing the strategy, but of > course you should verify on a test system first if you have one. > > Cheers, > -- > Alex > >
Re: Upgrading cassandra cluster from 2.1 to 3.X when using custom TWCS
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 name > 3 - you changed the compaction strategy to use the built in one? > Correct. Another question, did changing the compaction strategy from one twcs to the > other trigger merging of old sstables? > I don't recall any unexpected action from changing the strategy, but of course you should verify on a test system first if you have one. Cheers, -- Alex
Re: Upgrading cassandra cluster from 2.1 to 3.X when using custom TWCS
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 built in one? Another question, did changing the compaction strategy from one twcs to the other trigger merging of old sstables? gil On Thu, Jul 9, 2020 at 4:51 PM Oleksandr Shulgin < oleksandr.shul...@zalando.de> wrote: > 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 following error >> > > I guess you'll have to hop through 3.0 first. We did upgrade from 2.1 to > 3.0 by including a twcs.jar built against 3.0 and then altering the table > compaction to use the built-in one, then finally removing the custom jar. > > We had to tweak it a bit for 3.0.15 at the time: > https://github.com/a1exsh/twcs/tree/cassandra-3.0.x > > Regards, > -- > Alex > >
Re: Upgrading cassandra cluster from 2.1 to 3.X when using custom TWCS
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 following error > I guess you'll have to hop through 3.0 first. We did upgrade from 2.1 to 3.0 by including a twcs.jar built against 3.0 and then altering the table compaction to use the built-in one, then finally removing the custom jar. We had to tweak it a bit for 3.0.15 at the time: https://github.com/a1exsh/twcs/tree/cassandra-3.0.x Regards, -- Alex
Upgrading cassandra cluster from 2.1 to 3.X when using custom TWCS
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 CassandraDaemon.java:774 - Exception encountered during startup java.lang.NoClassDefFoundError: org/apache/cassandra/io/sstable/SSTableReader at java.lang.Class.getDeclaredMethods0(Native Method) ~[na:1.8.0-zing_19.12.102.0] at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) ~[na:1.8.0-zing_19.12.102.0] at java.lang.Class.privateGetMethodRecursive(Class.java:3048) ~[na:1.8.0-zing_19.12.102.0] at java.lang.Class.getMethod0(Class.java:3018) ~[na:1.8.0-zing_19.12.102.0] at java.lang.Class.getMethod(Class.java:1784) ~[na:1.8.0-zing_19.12.102.0] at org.apache.cassandra.schema.LegacySchemaMigrator.compactionFromRow(LegacySchemaMigrator.java:558) ~[apache-cassandra-3.11.7.jar:3.11.7] at org.apache.cassandra.schema.LegacySchemaMigrator.decodeTableParams(LegacySchemaMigrator.java:493) ~[apache-cassandra-3.11.7.jar:3.11.7] at org.apache.cassandra.schema.LegacySchemaMigrator.decodeTableMetadata(LegacySchemaMigrator.java:381) ~[apache-cassandra-3.11.7.jar:3.11.7] at org.apache.cassandra.schema.LegacySchemaMigrator.readTableMetadata(LegacySchemaMigrator.java:274) ~[apache-cassandra-3.11.7.jar:3.11.7] at org.apache.cassandra.schema.LegacySchemaMigrator.readTable(LegacySchemaMigrator.java:245) ~[apache-cassandra-3.11.7.jar:3.11.7] at org.apache.cassandra.schema.LegacySchemaMigrator.lambda$readTables$7(LegacySchemaMigrator.java:238) ~[apache-cassandra-3.11.7.jar:3.11.7] at java.util.ArrayList.forEach(ArrayList.java:1257) ~[na:1.8.0-zing_19.12.102.0] at org.apache.cassandra.schema.LegacySchemaMigrator.readTables(LegacySchemaMigrator.java:238) ~[apache-cassandra-3.11.7.jar:3.11.7] at org.apache.cassandra.schema.LegacySchemaMigrator.readKeyspace(LegacySchemaMigrator.java:187) ~[apache-cassandra-3.11.7.jar:3.11.7] at org.apache.cassandra.schema.LegacySchemaMigrator.lambda$readSchema$4(LegacySchemaMigrator.java:178) ~[apache-cassandra-3.11.7.jar:3.11.7] at java.util.ArrayList.forEach(ArrayList.java:1257) ~[na:1.8.0-zing_19.12.102.0] at org.apache.cassandra.schema.LegacySchemaMigrator.readSchema(LegacySchemaMigrator.java:178) ~[apache-cassandra-3.11.7.jar:3.11.7] at org.apache.cassandra.schema.LegacySchemaMigrator.migrate(LegacySchemaMigrator.java:78) ~[apache-cassandra-3.11.7.jar:3.11.7] at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:263) [apache-cassandra-3.11.7.jar:3.11.7] (This is with the jar in place, if the jar is not there there is an error about unknown compaction startegy) I know I can convert the table to a regular size tier before the upgrade, but I would like to avoid this, as it will merge a lot of sstables into one. Has anybody upgraded a cluster with tables defined like this? Is there maybe another way to make the jar compatible with 3.X just for the sake of the upgrade so I can start my server and then move to the built in twcs. Gil
