Re: Nodetool Repair --full

Worth noting that if you have racks == RF you only need to repair one rack to repair all the data in the cluster if you *don't* use -pr. Also note that full repairs on >=3.0 case anti-compactions and will mark things as repaired, so once you start repairs you need to keep repairing to ensure you do

Re: replace dead node vs remove node

Didn't read the blog but it's worth noting that if you replace the node and give it a *different* ip address repairs will not be necessary as it will receive writes during replacement. This works as long as you start up the replacement node before HH window ends. https://issues.apache.org/jira/bro

Re: Execute an external program

Correct. Note that both triggers and CDC aren't widely used yet so be sure to test. On 28 March 2018 at 13:02, Earl Lapus wrote: > > On Wed, Mar 28, 2018 at 8:39 AM, Jeff Jirsa wrote: > >> CDC may also work for newer versions, but it’ll happen after the mutation >> is applied >> >> -- >> Jeff J

Re: auto_bootstrap for seed node

Setting auto_bootstrap on seed nodes is unnecessary and irrelevant. If the node is a seed it will ignore auto_bootstrap and it *will not* bootstrap. On 28 March 2018 at 15:49, Ali Hubail wrote: > "it seems that we still need to keep bootstrap false?" > > Could you shed some light on what would h

Re: Shifting data to DCOS

Without looking at the code I'd say maybe the keyspaces are displayed purely because the directories exist (but it seems unlikely). The process you should follow instead is to exclude the system keyspaces for each node and manually apply your schema, then upload your CFs into the correct directory.

Re: Many SSTables only on one node

If there were no other messages about anti-compaction similar to: > > SSTable YYY (ranges) will be anticompacted on range [range] Then no anti-compaction needed to occur and yes, it was not the cause. On 5 April 2018 at 13:52, Dmitry Simonov wrote: > Hi, Evelyn! > > I've found the following me

Re: Shifting data to DCOS

Sorry for the delay. > Is the problem related to token ranges? How can I find out token range for > each node? > What can I do to further debug and root cause this? Very likely. See below. My previous cluster has 3 nodes but replication factor is 2. I am not > exactly sure how I would handle the

Re: about the tombstone and hinted handoff

I don't think that's true/maybe that comment is misleading. Tombstones AFAIK will be propagated by hints, and the hint system doesn't do anything to check if a particular row has been tombstoned. To the node receiving the hints it just looks like it's receiving a bunch of writes, it doesn't know th

Re: Token range redistribution

A new node always generates more tokens. A replaced node using replace_address[_on_first_boot] will reclaim the tokens of the node it's replacing. Simply removing and adding back a new node without replace address will end up with the new node having different tokens, which would mean data loss in

Re: Token range redistribution

That's assuming your data is perfectly consistent, which is unlikely. Typically that strategy is a bad idea and you should avoid it. On Thu., 19 Apr. 2018, 07:00 Richard Gray, wrote: > On 2018-04-18 21:28, kurt greaves wrote: > > replacing. Simply removing and adding back a ne

Re: Phantom growth resulting automatically node shutdown

This was fixed (again) in 3.0.15. https://issues.apache.org/jira/browse/CASSANDRA-13738 On Fri., 20 Apr. 2018, 00:53 Jeff Jirsa, wrote: > There have also been a few sstable ref counting bugs that would over > report load in nodetool ring/status due to overlapping normal and > incremental repairs

Re: SSTable count in Nodetool tablestats(LevelCompactionStrategy)

I'm currently investigating this issue on one of our clusters (but much worse, we're seeing >100 SSTables and only 2 in the levels) on 3.11.1. What version are you using? It's definitely a bug. On 17 April 2018 at 10:09, wrote: > Dear Community, > > > > One of the tables in my keyspace is using

Re: Memtable type and size allocation

Hi Vishal, In Cassandra 3.11.2, there are 3 choices for the type of Memtable > allocation and as per my understanding, if I want to keep Memtables on JVM > heap I can use heap_buffers and if I want to store Memtables outside of JVM > heap then I've got 2 options offheap_buffers and offheap_objects

Re: what's the read cl of list read-on-write operations?

> ​Given the rf is 3, r/w cl is quorum. > Initially, the list is empty, the user appends one element into the list: > list += [foo] > Then node A is down, and the user prepends another element: list = [bar] + list Then A comes back, assuming the list on A is still [foo], and the list on nodeB an

Re: Regular NullPointerExceptions from `nodetool compactionstats` on 3.7 node

Typically have seen that in the past when the node is overloaded. Is that a possibility for you? If it works consistently after restarting C* it's likely the issue. On 20 April 2018 at 19:27, Paul Pollack wrote: > Hi all, > > We have a cluster running on Cassandra 3.7 (we already know this is >

Re: Determining active sstables and table- dir

In 2.2 it's cf_id from system.schema_columnfamilies. If it's not then that's a bug. From 2.2 we stopped including table name in the SSTable name, so whatever directory contains the SSTables is the active one. Conversely, if you've dropped a table and re-added it, the directory without any SSTables

Re: Shifting data to DCOS

an anyone please suggest the best way to move data from one cluster to > another? > > Any help will be greatly appreciated. > > On Tue, Apr 17, 2018 at 6:52 AM, Faraz Mateen wrote: > >> Thanks for the response guys. >> >> Let me try setting token ranges manually an

Re: Version Upgrade

> > In other words, if I am running Cassandra 1.2.x and upgrading to 2.0.x, > 2.0.x will continue to read all the old Cassandra 1.2.x table. However, if > I then want to upgrade to Cassandra 2.1.x, I’d better make sure all tables > have been upgraded to 2.0.x before making the next upgrade. Corre

Re: compaction: huge number of random reads

If you've got small partitions/small reads you should test lowering your compression chunk size on the table and disabling read ahead. This sounds like it might just be a case of read amplification. On Tue., 8 May 2018, 05:43 Kyrylo Lebediev, wrote: > Dear Experts, > > > I'm observing strange be

Re: dtests failing with - ValueError: unsupported hash type md5

What command did you run? Probably worth checking that cqlsh is installed in the virtual environment and that you are executing pytest from within the virtual env. On 10 May 2018 at 05:06, Rajiv Dimri wrote: > Hi All, > > > > We have setup a dtest environment to run against Cassandra db version

Re: Suggestions for migrating data from cassandra

COPY might work but over hundreds of gigabytes you'll probably run into issues if you're overloaded. If you've got access to Spark that would be an efficient way to pull down an entire table and dump it out using the spark-cassandra-connector. On 15 May 2018 at 10:59, Jing Meng wrote: > Hi guys,

Re: row level atomicity and isolation

Atomicity and isolation are only guaranteed within a replica. If you have multiple concurrent requests across replicas last timestamp will win. You can get better isolation using LWT which uses paxos under the hood. On 16 May 2018 at 08:55, Rajesh Kishore wrote: > Hi, > > I am just curious to kn

Re: Invalid metadata has been detected for role

Can you post the stack trace and you're version of Cassandra? On Fri., 18 May 2018, 09:48 Abdul Patel, wrote: > Hi > > I had to decommission one dc , now while adding bacl the same nodes ( i > used nodetool decommission) they both get added fine and i also see them im > nodetool status but i am

Re: performance on reading only the specific nonPk column

Every column will be retrieved (that's populated) from disk and the requested column will then be sliced out in memory and sent back. On 21 May 2018 at 08:34, sujeet jog wrote: > Folks, > > consider a table with 100 metrics with (id , timestamp ) as key, > if one wants to do a selective metric r

Re: nodetool (2.1.18) - Xmx, ParallelGCThreads, High CPU usage

> > 1) nodetool is reusing the $MAX_HEAP_SIZE environment variable, thus if we > are running Cassandra with e.g. Xmx31G, nodetool is started with Xmx31G as > well This was fixed in 3.0.11/3.10 in CASSANDRA-12739 . Not sure why it didn't make i

Re: nodetool (2.1.18) - Xmx, ParallelGCThreads, High CPU usage

here: https://issues.apache.org/ > jira/browse/CASSANDRA-14475 > > > > Thanks, > > Thomas > > > > *From:* kurt greaves [mailto:k...@instaclustr.com] > *Sent:* Dienstag, 29. Mai 2018 05:54 > *To:* User > *Subject:* Re: nodetool (2.1.18) - Xmx, ParallelGCThrea

Re: nodetool (2.1.18) - Xmx, ParallelGCThreads, High CPU usage

(43 on our large machine) and running with Xmx128M or XmX31G > (derived from $MAX_HEAP_SIZE). For both Xmx, we saw the high CPU caused by > nodetool. > > > > Regards, > > Thomas > > > > *From:* kurt greaves [mailto:k...@instaclustr.com] > *Sent:* Dienstag

Re: Cassandra 3.0.X migarte to VPC

> > I meant migrating to gosspsnitch during adding new dc. New dc will be > empty so all the data will be streamed based on snitch property chosen Should work fine on the new DC, as long as the original DC is using a snitch that supports datacenters - then just don't mix and match snitches within

Re: Migrating to Reaper: Switching From Incremental to Reaper's Full Subrange Repair

Not strictly necessary but probably a good idea as you don't want two separate pools of SSTables unnecessarily. Also if you've set "only_purge_repaired_tombstones" you'll need to turn that off. On Wed., 13 Jun. 2018, 23:06 Fd Habash, wrote: > For those who are using Reaper … > > > > Currently, I

Re: Compaction strategy for update heavy workload

TWCS is probably still worth trying. If you mean updating old rows in TWCS "out of order updates" will only really mean you'll hit more SSTables on read. This might add a bit of complexity in your client if your bucketing partitions (not strictly necessary), but that's about it. As long as you're n

Re: Timestamp on hints file and system.hints table data

system.hints is not used in Cassandra 3. Can't explain the files though, are you referring to the files timestamp or the Unix timestamp in the file name? Is there a node that's been down for several months? On Wed., 13 Jun. 2018, 23:41 Nitan Kainth, wrote: > Hi, > > I observed a strange behavior

Re: Timestamp on hints file and system.hints table data

down for months. And yes, I am surprised to look at Unix > timestamp on files. > > > > On Jun 13, 2018, at 6:41 PM, kurt greaves wrote: > > system.hints is not used in Cassandra 3. Can't explain the files though, > are you referring to the files timestamp or the Unix ti

Re: Compaction strategy for update heavy workload

re's updates, you're going to risk having > data that's never deleted and really small sstables sticking around > forever. If you use really large buckets, what's the point of TWCS? > > Honestly this is such a small workload you could easily use STCS or > LCS and yo

Re:

> > 1) Am I correct to assume that the larger page size some user session has > set - the larger portion of cluster/coordinator node resources will be > hogged by the corresponding session? > 2) Do I understand correctly that page size (imagine we have no timeout > settings) is limited by RAM and i

Re: Timestamp on hints file and system.hints table data

a3d RAC1 > > > > On Thu, Jun 14, 2018 at 12:45 AM, kurt greaves > wrote: > >> Does the UUID on the filename correspond with a UUID in nodetool status? >> >> Sounds to me like it could be something weird with an old node that no >> longer exists, althoug

Re: Timestamp on hints file and system.hints table data

created. On 18 June 2018 at 13:56, learner dba wrote: > Yes Kurt, system log is flooded with hints sent and replayed messages. > > On Monday, June 18, 2018, 7:30:34 AM EDT, kurt greaves < > k...@instaclustr.com> wrote: > > > Not sure what to make of that. Are there

Re: 3.11.2 memory leak

At this point I'd wait for 3.11.3. If you can't, you can get away with backporting a few repair fixes or just doing sub range repairs on 3.11.2 On Wed., 20 Jun. 2018, 01:10 Abdul Patel, wrote: > Hi All, > > Do we kmow whats the stable version for now if u wish to upgrade ? > > On Tuesday, June 5

Re: Is it ok to add more than one node to a exist cluster

Don't bootstrap nodes simultaneously unless you really know what you're doing, and you're using single tokens. It's not straightforward and will likely lead to data loss/inconsistencies. This applies for all current versions. On 27 June 2018 at 10:21, dayu wrote: > Hi, > I have read a warnin

Re: Is it ok to add more than one node to a exist cluster

Normal ? >> >> Dayu >> >> >> >> At 2018-06-27 17:50:34, "kurt greaves" wrote: >> >> Don't bootstrap nodes simultaneously unless you really know what you're >> doing, and you're using single tokens. It's not straig

Re: Re: stream failed when bootstrap

Best off trying a rolling restart. On 28 June 2018 at 03:18, dayu wrote: > the output of nodetool describecluster > Cluster Information: > Name: online-xxx > Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch > Partitioner: org.apache.cassandra.dht.Murmur3Partitioner > Schema versions: >

Re: Re: Re: stream failed when bootstrap

cassandra and start cassandra command one by one, right? > Only one node is executed at a time > > Dayu > > > > At 2018-06-28 11:37:43, "kurt greaves" wrote: > > Best off trying a rolling restart. > > On 28 June 2018 at 03:18, dayu wrote: > >> the

Re: C* in multiple AWS AZ's

There is a need for a repair with both DCs as rebuild will not stream all replicas, so unless you can guarantee you were perfectly consistent at time of rebuild you'll want to do a repair after rebuild. On another note you could just replace the nodes but use GPFS instead of EC2 snitch, using the

Re: C* in multiple AWS AZ's

e downside? status would report rack of 1a, even though in 1e? > > Thanks in advance for the help/thoughts!! > > > On Thu, Jun 28, 2018 at 6:20 PM, kurt greaves > wrote: > >> There is a need for a repair with both DCs as rebuild will not stream all >> replicas,

Re: Inconsistent Quorum Read after Quorum Write

Shouldn't happen. Any chance you could trace the queries, or have you been able to reproduce it? Also, what version of Cassandra? On Wed., 4 Jul. 2018, 06:41 Visa, wrote: > Hi all, > > We recently experienced an unexpected behavior with C* consistency. > > For example, a table t consists of 4 co

[ANNOUNCE] LDAP Authenticator for Cassandra

We've seen a need for an LDAP authentication implementation for Apache Cassandra so we've gone ahead and created an open source implementation (ALv2) utilising the pluggable auth support in C*. Now, I'm positive there are multiple implementations floating around that haven't been open sourced, and

Re: default_time_to_live vs TTL on insert statement

The Datastax documentation is wrong. It won't error, and it shouldn't. If you want to fix that documentation I suggest contacting Datastax. On 11 July 2018 at 19:56, Nitan Kainth wrote: > Hi DuyHai, > > Could you please explain in what case C* will error based on documented > statement: > > You

Re: batchstatement

What is the primary key for the user_by_ext table? I'd assume it's ext_id, which would imply your update doesn't make sense as you can't change the primary key for a row - which would be the problem you're seeing. On Sat., 14 Jul. 2018, 06:14 Randy Lynn, wrote: > TL/DR: > - only 1 out of 14 stat

Re: Limitations of Hinted Handoff OverloadedException exception

The coordinator will refuse to send writes/hints to a node if it has a large backlog of hints (128 * #cores) already and the destination replica is one of the nodes with hints destined to it. It will still send writes to any "healthy" node (a node with no outstanding hints). The idea is to not fur

Re: 3.11.2 memory leak

Likely in the next few weeks. On Mon., 23 Jul. 2018, 01:17 Abdul Patel, wrote: > Any idea when 3.11.3 is coming in? > > On Tuesday, June 19, 2018, kurt greaves wrote: > >> At this point I'd wait for 3.11.3. If you can't, you can get away with >> backporting a

Re: Hinted Handoff

> > Does Cassandra TTL out the hints after max_hint_window_in_ms? From my > understanding, Cassandra only stops collecting hints after > max_hint_window_in_ms but can still keep replaying the hints if the node > comes back again. Is this correct? Is there a way to TTL out hints? No, but it won't

Re: Data Corruption due to multiple Cassandra 2.1 processes?

Yeah that's not ideal and could lead to problems. I think corruption is only likely if compactions occur, but seems like data loss is a potential not to mention all sorts of other possible nasties that could occur running two C*'s at once. Seems to me that 11540 should have gone to 2.1 in the first

Re: Configuration parameter to reject incremental repair?

No flag currently exists. Probably a good idea considering the serious issues with incremental repairs since forever, and the change of defaults since 3.0. On 7 August 2018 at 16:44, Steinmaurer, Thomas < thomas.steinmau...@dynatrace.com> wrote: > Hello, > > > > we are running Cassandra in AWS an

Re: Data Corruption due to multiple Cassandra 2.1 processes?

ort referencing 11540 or re-open 11540? > > > > Thanks for your help. > > > > Thomas > > > > *From:* kurt greaves > *Sent:* Montag, 13. August 2018 13:24 > *To:* User > *Subject:* Re: Data Corruption due to multiple Cassandra 2.1 processes? > >

Re: 90million reads

Not a great idea to make config changes without testing. For a lot of changes you can make the change on one node and measure of three is an improvement however. You'd probably be best to add nodes (double should be sufficient), do tuning and testing afterwards, and then decommission a few nodes i

Re: JBOD disk failure

If that disk had important data in the system tables however you might have some trouble and need to replace the entire instance anyway. On 15 August 2018 at 12:20, Jeff Jirsa wrote: > Depends on version > > For versions without the fix from Cassandra-6696, the only safe option on > single disk

Re: JBOD disk failure

e: > Thank you for the answers. We are using the current version 3.11.3 So this > one includes CASSANDRA-6696. > > So if I get this right, losing system tables will need a full node > rebuild. Otherwise repair will get the node consistent again. > > > > Regards, > &g

Re: JBOD disk failure

As far as I'm aware, yes. I recall hearing someone mention tying system tables to a particular disk but at the moment that doesn't exist. On Fri., 17 Aug. 2018, 01:04 Eric Evans, wrote: > On Wed, Aug 15, 2018 at 3:23 AM kurt greaves wrote: > > Yep. It might require

Re: Configuration parameter to reject incremental repair?

Yeah I meant 2.2. Keep telling myself it was 3.0 for some reason. On 20 August 2018 at 19:29, Oleksandr Shulgin wrote: > On Mon, Aug 13, 2018 at 1:31 PM kurt greaves wrote: > >> No flag currently exists. Probably a good idea considering the serious >> issues with increme

Re: bigger data density with Cassandra 4.0?

I believe there are caveats that it will only really help if you're not using vnodes, or you have a very small cluster, and also internode encryption is not enabled. Alternatively if you're using JBOD vnodes will be marginally better, but JBOD is not a great idea (and doesn't guarantee a massive im

Re: 2.2 eats memory

I'm thinking it's unlikely that top is lying to you. Are you sure that you're measuring free memory versus available memory? Cassandra will utilise the OS page cache heavily, which will cache files in memory but leave the memory able to be reclaimed if needed. Have you checked the output of free? I

Re: bigger data density with Cassandra 4.0?

7;ve misunderstood. On 28 August 2018 at 01:37, Dinesh Joshi wrote: > Although the extent of benefits depend on the specific use case, the > cluster size is definitely not a limiting factor. > > Dinesh > > On Aug 27, 2018, at 5:05 AM, kurt greaves wrote: > > I believe

Re: Re: bigger data density with Cassandra 4.0?

Cassandra do)? > > Sent using Zoho Mail <https://www.zoho.com/mail/> > > > Forwarded message > From : kurt greaves > To : "User" > Date : Wed, 29 Aug 2018 12:03:47 +0430 > Subject : Re: bigger data density with Cassandra 4.0? >

Re: Nodetool refresh v/s sstableloader

Removing dev... Nodetool refresh only picks up new SSTables that have been placed in the tables directory. It doesn't account for actual ownership of the data like SSTableloader does. Refresh will only work properly if the SSTables you are copying in are completely covered by that nodes tokens. It

Re: URGENT: disable reads from node

Note that you'll miss incoming writes if you do that, so you'll be inconsistent even after the repair. I'd say best to just query at QUORUM until you can finish repairs. On 29 August 2018 at 21:22, Alexander Dejanovski wrote: > Hi Vlad, you must restart the node but first disable joining the clu

Re: Recommended num_tokens setting for small cluster

For 10 nodes you probably want to use between 32 and 64. Make sure you use the token allocation algorithm by specifying allocate_tokens_for_keyspace On Thu., 30 Aug. 2018, 04:40 Jeff Jirsa, wrote: > 3.0 has a (optional?) feature to guarantee better distribution, and the > blog focuses on 2.2. >

Re: stuck with num_tokens 256

If you have problems with balance you can add new nodes using the algorithm and it'll balance out the cluster. You probably want to stick to 256 tokens though. To reduce your # tokens you'll have to do a DC migration (best way). Spin up a new DC using the algorithm on the nodes and set a lower numb

Re: stuck with num_tokens 256

eyspaces) for new clusters which i'm going to > setup? > Is the Allocation algorithm, now recommended algorithm and mature enough > to replace the Random algorithm? if its so, it should be the default one at > 4.0? > > > On Sat, 22 Sep 2018 13:41:47 +0330 *kurt grea

Re: stuck with num_tokens 256

No, that's not true. On Sat., 22 Sep. 2018, 21:58 onmstester onmstester, wrote: > > If you have problems with balance you can add new nodes using the > algorithm and it'll balance out the cluster. You probably want to stick to > 256 tokens though. > > > I read somewhere (don't remember the ref)

Re: node replacement failed

I don't like your cunning plan. Don't drop the system auth and distributed keyspaces, instead just change them to NTS and then do your replacement for each down node. If you're actually using auth and worried about consistency I believe 3.11 has the feature to be able to exclude nodes during a re

Re: TWCS + subrange repair = excessive re-compaction?

Not any faster, as you'll still have to wait for all the SSTables to age off, as a partition level tombstone will simply go to a new SSTable and likely will not be compacted with the old SSTables. On Tue, 25 Sep 2018 at 17:03, Martin Mačura wrote: > Most partitions in our dataset span one or two

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 > th

[ANNOUNCE] StratIO's Lucene plugin fork

Hi all, We've had confirmation from Stratio that they are no longer maintaining their Lucene plugin for Apache Cassandra. We've thus decided to fork the plugin to continue maintaining it. At this stage we won't be making any additions to the plugin in the short term unless absolutely necessary, an

Re: Tombstone removal optimization and question

Yes it does. Consider if it didn't and you kept writing to the same partition, you'd never be able to remove any tombstones for that partition. On Tue., 6 Nov. 2018, 19:40 DuyHai Doan Hello all > > I have tried to sum up all rules related to tombstone removal: > > > --

Re: cqlsh problem

;>>>> >>>>>>>> 2016-03-17 22:35 GMT+08:00 Vishwas Gupta < >>>>>>>> vishwas.gu...@snapdeal.com>: >>>>>>>> >>>>>>>>> Have you started the Cassandra service? >>>>>>>>> >>>>>>>>> sh cassandra >>>>>>>>> On 17-Mar-2016 7:59 pm, "Alain RODRIGUEZ" >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi, did you try with the address of the node rather than 127.0.0.1 >>>>>>>>>> >>>>>>>>>> Is the transport protocol used by cqlsh (not sure if it is thrift >>>>>>>>>> or binary - native in 2.1) active ? What is the "nodetool info" >>>>>>>>>> output ? >>>>>>>>>> >>>>>>>>>> C*heers, >>>>>>>>>> --- >>>>>>>>>> Alain Rodriguez - al...@thelastpickle.com >>>>>>>>>> France >>>>>>>>>> >>>>>>>>>> The Last Pickle - Apache Cassandra Consulting >>>>>>>>>> http://www.thelastpickle.com >>>>>>>>>> >>>>>>>>>> 2016-03-17 14:26 GMT+01:00 joseph gao : >>>>>>>>>> >>>>>>>>>>> hi, all >>>>>>>>>>> cassandra version 2.1.7 >>>>>>>>>>> When I use cqlsh to connect cassandra, something is wrong >>>>>>>>>>> >>>>>>>>>>> Connection error: ( Unable to connect to any servers', >>>>>>>>>>> {'127.0.0.1': OperationTimedOut('errors=None, last_host=None,)}) >>>>>>>>>>> >>>>>>>>>>> This happens lots of times, but sometime it works just fine. >>>>>>>>>>> Anybody knows why? >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> -- >>>>>>>>>>> Joseph Gao >>>>>>>>>>> PhoneNum:15210513582 >>>>>>>>>>> QQ: 409343351 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> -- >>>>>>>> Joseph Gao >>>>>>>> PhoneNum:15210513582 >>>>>>>> QQ: 409343351 >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> -- >>>>>> Joseph Gao >>>>>> PhoneNum:15210513582 >>>>>> QQ: 409343351 >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> -- >>>> Joseph Gao >>>> PhoneNum:15210513582 >>>> QQ: 409343351 >>>> >>> >>> >>> >>> -- >>> -- >>> Joseph Gao >>> PhoneNum:15210513582 >>> QQ: 409343351 >>> >> >> > > > -- > -- > Joseph Gao > PhoneNum:15210513582 > QQ: 409343351 > -- Kurt Greaves k...@instaclustr.com www.instaclustr.com

Re: Increasing replication factor and repair doesn't seem to work

ta was synced or how to get the data correctly synced without > decommissioning the node and re-adding it. > -- Kurt Greaves k...@instaclustr.com www.instaclustr.com

Re: Increasing replication factor and repair doesn't seem to work

Owns (effective) Host ID >>>> Rack >>>> UN 10.142.0.14 6.4 GB 256 100.0% >>>> c3a5c39d-e1c9-4116-903d-b6d1b23fb652 default >>>> UN 10.142.0.13 5.55 GB256 100.0% >>>> d0d9c30e-150

Re: Internal Handling of Map Updates

>> www.codecentric.de | blog.codecentric.de | www.meettheexperts.de | >> www.more4fi.de >> >> Sitz der Gesellschaft: Solingen | HRB 25917| Amtsgericht Wuppertal >> Vorstand: Michael Hochgürtel . Mirko Novakovic . Rainer Vehns >> Aufsichtsrat: Patric Fedlmeier (Vorsitzender) . Klaus Jäger . Jürgen >> Schütz >> >> Diese E-Mail einschließlich evtl. beigefügter Dateien enthält >> vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht >> der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, >> informieren Sie bitte sofort den Absender und löschen Sie diese E-Mail und >> evtl. beigefügter Dateien umgehend. Das unerlaubte Kopieren, Nutzen oder >> Öffnen evtl. beigefügter Dateien sowie die unbefugte Weitergabe dieser >> E-Mail ist nicht gestattet >> > > > > -- > Tyler Hobbs > DataStax <http://datastax.com/> > -- Kurt Greaves k...@instaclustr.com www.instaclustr.com

Re: Internal Handling of Map Updates

tlich geschützte Informationen. Wenn Sie nicht >>>> der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, >>>> informieren Sie bitte sofort den Absender und löschen Sie diese E-Mail und >>>> evtl. beigefügter Dateien umgehend. Das unerlaubte Kopieren, Nutzen oder >>>> Öffnen evtl. beigefügter Dateien sowie die unbefugte Weitergabe dieser >>>> E-Mail ist nicht gestattet >>>> >>> >>> >>> >>> -- >>> Tyler Hobbs >>> DataStax <http://datastax.com/> >>> >> >> >> >> -- >> Matthias Niehoff | IT-Consultant | Agile Software Factory | Consulting >> codecentric AG | Zeppelinstr 2 | 76185 Karlsruhe | Deutschland >> tel: +49 (0) 721.9595-681 | fax: +49 (0) 721.9595-666 | mobil: +49 (0) >> 172.1702676 >> www.codecentric.de | blog.codecentric.de | www.meettheexperts.de | >> www.more4fi.de >> >> Sitz der Gesellschaft: Solingen | HRB 25917| Amtsgericht Wuppertal >> Vorstand: Michael Hochgürtel . Mirko Novakovic . Rainer Vehns >> Aufsichtsrat: Patric Fedlmeier (Vorsitzender) . Klaus Jäger . Jürgen >> Schütz >> >> Diese E-Mail einschließlich evtl. beigefügter Dateien enthält >> vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht >> der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, >> informieren Sie bitte sofort den Absender und löschen Sie diese E-Mail und >> evtl. beigefügter Dateien umgehend. Das unerlaubte Kopieren, Nutzen oder >> Öffnen evtl. beigefügter Dateien sowie die unbefugte Weitergabe dieser >> E-Mail ist nicht gestattet >> > -- Kurt Greaves k...@instaclustr.com www.instaclustr.com

Re: Interesting use case

etween setting a really short ttl and doing a delete? > > > > I know there are a lot of questions in there but we’ve been going back and > forth on this for a while and I’d really appreciate any help you could give. > > > > Thanks, > > John > -- Kurt Greaves k...@instaclustr.com www.instaclustr.com

Re: Interesting use case

Sorry, I did mean larger number of rows per partition. On 9 June 2016 at 10:12, John Thomas wrote: > The example I gave was for when N=1, if we need to save more values I > planned to just add more columns. > > On Thu, Jun 9, 2016 at 12:51 AM, kurt Greaves > wrote: > &

Re: Interesting use case

woops was obviously tired, what I said clearly doesn't make sense. On 10 June 2016 at 14:52, kurt Greaves wrote: > Sorry, I did mean larger number of rows per partition. > > On 9 June 2016 at 10:12, John Thomas wrote: > >> The example I gave was for when N=1, if we nee

Re: Streaming from 1 node only when adding a new DC

replaced, but when rebuilding a new DC, it should > probably select sources "randomly" (rather than always selecting the same > source for a specific range). > What do you think ? > > Best Regards, > Fabien > -- Kurt Greaves k...@instaclustr.com www.instaclustr.com

Re: nodetool repair with -pr and -dc

air.py -k [keyspace] -c [columnfamily name] -v -H >>>> localhost -p -D* DC1* >>>> >>>> but looks like the merkle tree is being calculated on nodes which are >>>> part of other *DC2.* >>>> >>>> why does this happen? i thought it should only look at the nodes in >>>> local cluster. however on nodetool the* -pr* option cannot be used >>>> with *-local* according to docs @https://docs.datastax.com/en/ >>>> cassandra/2.0/cassandra/tools/toolsRepair.html >>>> >>>> so i am may be missing something, can someone help explain this please. >>>> >>>> thanks >>>> anishek >>>> >>> >>> >> > -- Kurt Greaves k...@instaclustr.com www.instaclustr.com

Read Repairs and CL

s based off the CL of the query. However I don't think that makes sense at other CLs. Anyway, I just want to clarify what CL the read for the read repair occurs at for cases where the overall query CL is not ALL. Thanks, Kurt. -- Kurt Greaves k...@instaclustr.com www.instaclustr.com

Re: Tombstoned error and then OOM

Executor.runWorker(Unknown > Source) ~[na:1.7.0_80] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown > Source) ~[na:1.7.0_80] > at java.lang.Thread.run(Unknown Source) ~[na:1.7.0_80] > > -- IB > > > > > > -- Kurt Greaves k...@instaclustr.com www.instaclustr.com

Re: Tombstoned error and then OOM

; > Here the status is integer column which is indexed. > > -- IB > > ------ > *From:* kurt Greaves > *To:* user@cassandra.apache.org; INDRANIL BASU > *Sent:* Tuesday, 4 October 2016 10:38 PM > *Subject:* Re: Tombstoned error and then OOM > >

Re: are there any free Cassandra -> ElasticSearch connector / plugin ?

ested Elassandra. But that is based on Cassandra 2.2. >> I would like to use Cassandra 3.7 and up... >> >> >> >> -eric ho >> >> >> On Thu, Oct 13, 2016 at 3:04 PM, vincent gromakowski < >> vincent.gromakow...@gmail.com> wrote: >&

Re: Repair in Multi Datacenter - Should you use -dc Datacenter repair or repair with -pr

s > either. > > > What is the best way to perform repairs on multiple data centers on large > tables. > > 1. Can we run Datacenter repair using -dc option for each data center? Do > we need to run repair on each node in that case or will it repair all nodes > within

Re: Cassandra installation best practices

Mehdi, Nothing as detailed as Oracle's OFA currently exists. You can probably also find some useful information here: https://docs.datastax.com/en/landing_page/doc/landing_page/planning/planningAbout.html Kurt Greaves k...@instaclustr.com www.instaclustr.com On 18 October 2016 at 07:38,

Re: Introducing Cassandra 3.7 LTS

certainly been discussion regarding the tick-tock cadence, and it seems safe to say it will change. There hasn't been any official announcement yet, however. Kurt Greaves k...@instaclustr.com www.instaclustr.com

Re: non incremental repairs with cassandra 2.2+

e you're using subranges with incremental repairs. This will generate a lot of anticompactions as you'll only repair a portion of the SSTables. You should use forceRepairAsync for incremental repairs so that it's possible for the repair to act on the whole SSTable, minimising ant

Re: non incremental repairs with cassandra 2.2+

Welp, that's good but wasn't apparent in the codebase :S. Kurt Greaves k...@instaclustr.com www.instaclustr.com On 20 October 2016 at 05:02, Alexander Dejanovski wrote: > Hi Kurt, > > we're not actually. > Reaper performs full repair by subrange but does incrementa

Re: time series data model

Ah didn't pick up on that but looks like he's storing JSON within position. Is there any strong reason for this or as Vladimir mentioned can you store the fields under "position" in separate columns? Kurt Greaves k...@instaclustr.com www.instaclustr.com On 20 October 201

Re: time series data model

eems workable, I assume you're using DTCS/TWCS, and aligning the time windows to your day bucket. (If not you should do that) Kurt Greaves k...@instaclustr.com www.instaclustr.com On 20 October 2016 at 07:29, wxn...@zjqunshuo.com wrote: > Hi All, > I'm trying to migrate my time s

Re: non incremental repairs with cassandra 2.2+

probably because i was looking the wrong version of the codebase :p

Re: Cluster Maintenance Mishap

ter. If you did, they wouldn't have assumed the token ranges and you shouldn't have any issues. You can just copy the original data back (including system tables) and they should assume their own ranges again, and then you can repair to fix any missing replicas. Kurt Greaves k...@instaclustr.com www.instaclustr.com

Re: How to throttle up/down compactions without a restart

e too much disk bandwidth. If you're needing to alter this in peak periods you may be starting to overload your nodes with writes, or potentially something else is not ideal like memtables flushing too frequently. Kurt Greaves k...@instaclustr.com www.instaclustr.com On 21 October 2016 at

Re: Question about compaction strategy changes

s your read queries won't benefit from the smaller window size. Kurt Greaves k...@instaclustr.com www.instaclustr.com

Re: Question about compaction strategy changes

​More compactions meaning "actual number of compaction tasks". A compaction task generally operates on many SSTables (how many depends on the chosen compaction strategy). The number of pending tasks does not line up with the number of SSTables that will be compacted. 1 task may compact many SSTable

Re: Question about compaction strategy changes

result in SSTables that don't expire because some small portion may be live data. Plus mixed with the small number of compaction candidates, it could take a long time for these types of SSTables to be compacted (possibly never). Kurt Greaves k...@instaclustr.com www.instaclustr.com

  1   2   3   4   >