Re: SSTableMetadata Util

Pranay, 3.11.3 should include all the C* binaries in /usr/bin. Maybe try reinstalling? Sounds like something got messed up along the way. Kurt On Tue, 2 Oct 2018 at 12:45, Pranay akula wrote: > Thanks Christophe, > > I have installed using rpm package I actually ran locate command to find >

Re: SSTableMetadata Util

Thanks Christophe, I have installed using rpm package I actually ran locate command to find the sstable utils I could find only those 4 Probably I may need to manually copy them. Regards Pranay On Mon, Oct 1, 2018, 9:01 PM Christophe Schmitz wrote: > Hi Pranay, > > The sstablemetadata is

Re: SSTableMetadata Util

Hi Pranay, The sstablemetadata is still available in the tarball file ($CASSANDRA_HOME/tools/bin) in 3.11.3. Not sure why it is not available in your packaged installation, you might want to manually copy the one from the package to your /usr/bin/ Additionaly, you can have a look at

Re: Cassandra loading data from another table

Have a look at using Spark on Cassandra. It's commonly used for data movement / data migration / reconciliation (on top of analytics). You will get much better performances. Christophe Schmitz - Instaclustr - Cassandra | Kafka | Spark Consulting On Tue, 2 Oct

SSTableMetadata Util

Hi, I am testing apache 3.11.3 i couldn't find sstablemetadata util All i can see is only these utilities in /usr/bin -rwxr-xr-x. 1 root root2042 Jul 25 06:12 sstableverify -rwxr-xr-x. 1 root root2045 Jul 25 06:12 sstableutil -rwxr-xr-x. 1 root root2042 Jul 25

Re: [EXTERNAL] Re: Rolling back Cassandra upgrades (tarball)

sstable version alone isn’t sufficient - there can be other surprises that will break the lower version (commitlog format change, new types or concepts like UDTs that may appear in the schema, etc) I think 3.11 to 3.0 still works but I’m not certain of it personally -- Jeff Jirsa > On Oct

Re: [EXTERNAL] Re: Rolling back Cassandra upgrades (tarball)

Adding to the thread: - SSTable format is identical between 3.0.x and 3..11.x, so your SSTable files are compatible, in this case. BTW an easy way to check that is to look at the SSTables filename convention; first letters ('mc' in this case) indicate the SSTable storage format

Re: Cassandra loading data from another table

Christophe, thanks for your insights,Sorry, I forgot to mention that currently both tableA and tableB are being updated by application (all newly inserted/updated records should be identical on A and B), exporting from tableB and COPY it back later on will result in older data overwrites

Re: Cassandra loading data from another table

Hi Richard, You could consider exporting your few thousands record of Table B in a file, with *COPY TO*. Then *TRUNCATE* Table B, copy the SSTable files of TableA to the data directory of Table A (make sure you *flush* the memtables first), then run nodetool *refresh*. Final step is to load the

Cassandra loading data from another table

I have a tableA with about a few ten millions record, and I have tableB with a few thousands record,TableA and TableB have exact same schema (except that tableB doesnt have TTL) I want to load all data to tableB from tableA EXCEPT for those already on tableB (we don't want data on tableB to be

Re: Metrics matrix: migrate 2.1.x metrics to 2.2.x+

That's great too, thank you. Datadog 350 metric limit is a PITA for tables once you get over 10 tables, but I guess we can use bean_regex to do specific targetted metrics for the important tables anyway. On Mon, Oct 1, 2018 at 4:21 AM Alain RODRIGUEZ wrote: > Hello Carl, > > Here is a message

Re: Re: Re: how to configure the Token Allocation Algorithm

Hello again :), I thought a little bit more about this question, and I was actually wondering if something like this would work: Imagine 3 node cluster, and create them using: For the 3 nodes: `num_token: 4` Node 1: `intial_token: -9223372036854775808, -4611686018427387905, -2,

RE: [EXTERNAL] Re: Rolling back Cassandra upgrades (tarball)

Version choices aside, I am an advocate for forward-only (in most cases). Here is my reasoning, so that you can evaluate for your situation: - upgrades are done while the application is up and live and writing data (no app downtime) - the upgrade usually includes a change to the sstable version

Re: How default_time_to_live would delete rows without tombstones in Cassandra?

Hello Alain, thanks for clarifying this topic. You had alerted that this should be explored indeed, so there is nothing to apologize for. I've asked this in stackoverflow too ( https://stackoverflow.com/q/52282517/3517383), so if you want to answer there I will mark yours as the correct one, if

Fwd: Re: Re: how to configure the Token Allocation Algorithm

Thanks Alex, You are right, that would be a mistake. Sent using Zoho Mail Forwarded message From : Oleksandr Shulgin To : "User" Date : Mon, 01 Oct 2018 13:53:37 +0330 Subject : Re: Re: how to configure the Token Allocation Algorithm Forwarded message

Re: Re: how to configure the Token Allocation Algorithm

On Mon, Oct 1, 2018 at 12:18 PM onmstester onmstester wrote: > > What if instead of running that python and having one node with non-vnode > config, i remove the first seed node and re-add it after cluster was fully > up ? so the token ranges of first seed node would also be assigned by >

Fwd: Re: how to configure the Token Allocation Algorithm

Thanks Alain, What if instead of running that python and having one node with non-vnode config, i remove the first seed node and re-add it after cluster was fully up ? so the token ranges of first seed node would also be assigned by Allocation Alg Forwarded message

Re: unsubscribe

Hello, You're still subscribed to this mailing list I am afraid :). In case you missed it: To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org C*heers. Le lun. 1 oct. 2018 à 08:04, Gabriel Lindeborg <

Re: how to configure the Token Allocation Algorithm

Hello, Your process looks good to me :). Still a couple of comments to make it more efficient (hopefully). *- Improving step 2:* I believe you can actually get a slightly better distribution picking the tokens for the (first) seed node. This is to prevent the node from randomly calculating its

Re: Metrics matrix: migrate 2.1.x metrics to 2.2.x+

Hello Carl, Here is a message I sent to my team a few months ago. I hope this will be helpful to you and more people around :). It might not be exhaustive and we were moving from C*2.1 to C*3+ in this case, thus skipping C*2.2, but C*2.2 is similar to C*3.0 if I remember correctly in terms of

RE: Cassandra 2.1.21 ETA?

Michael, can you please elaborate on your SocketServer question. Is this for Thrift only or also affects the native protocol (CQL)? Yes, we basically have iptables rules in place disallowing remote access from machines outside the cluster. Thanks again, Thomas > -Original Message- >

Re: Multi dc reaper

Hi Abdul, the thing with multi DC Cassandra clusters is usually that JMX is not accessible on the cross DC link, which means that one Reaper in a DC cannot reach the nodes in remote DCs directly. That's when you need to start Reaper instances in each DC which will sync up through the Cassandra

unsubscribe

AB SVENSKA SPEL 621 80 Visby Norra Hansegatan 17, Visby Växel: +4610-120 00 00 https://svenskaspel.se Please consider the environment before printing this email - To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org