Re: Streaming Process: How can we speed it up?

need to do a quick replacement for > one reason or another. As you mention, the main disadvantage we ran into is > that the node doesn’t get cleaned up through the replacement process like a > newly streamed node does (plus the extra operational complexity). > > Cheers > Ben >

Re: Streaming Process: How can we speed it up?

Hello and thanks for your responses, OK, so increasing stream_throughput_outbound_megabits_per_sec makes no difference. Any ideas why streaming is limited to only two of the three nodes available? As an alternative to slow streaming I tried this: - install C* on a new node, stop the service an

Re: Flush activity and dropped messages

g more tables (that are actively written to) than your max queue > length will necessarily cause stalls every time you run out of commit log > space. > > In 2.1, none of these concerns apply. > > > On 24 August 2016 at 23:40, Vasileios Vlachos > wrote: > >> Hello,

Re: Flush activity and dropped messages

re tables (that are actively written to) than your max queue > length will necessarily cause stalls every time you run out of commit log > space. > > In 2.1, none of these concerns apply. > > > On 24 August 2016 at 23:40, Vasileios Vlachos > wrote: > >> Hello, &

Flush activity and dropped messages

Hello, We have an 8-node cluster spread out in 2 DCs, 4 nodes in each one. We run C* 2.0.17 on Ubuntu 12.04 at the moment. Our C# application often throws logs, which correlate with dropped messages (counter mutations usually) in our logs. We think that if a specific mutaiton stays in the

Re: StatusLogger output

Anyone else any idea on how to interpret StatusLogger output? As Sean said, this may not help in determining the problem, but it would definitely help my general understanding. Thanks, Bill On Thu, Mar 24, 2016 at 5:24 PM, Vasileios Vlachos < vasileiosvlac...@gmail.com> wrote: > Thanks

Re: StatusLogger output

Any nodes going down > at the time? > > > > > > Sean Durity > > > > *From:* Vasileios Vlachos [mailto:vasileiosvlac...@gmail.com] > *Sent:* Thursday, March 24, 2016 8:13 AM > *To:* user@cassandra.apache.org > *Subject:* Re: StatusLogger output > >

Re: StatusLogger output

Just to clarify, I can see line 29 which seems to explain the format (first number ops, second is data), however I don't know they actually mean. Thanks, Vasilis On Thu, Mar 24, 2016 at 11:45 AM, Vasileios Vlachos < vasileiosvlac...@gmail.com> wrote: > Hello, > > Enviro

StatusLogger output

Hello, Environment: - Cassandra 2.0.17, 8 nodes, 4 per DC - Ubuntu 12.04, 6-Cores, 16GB of RAM (we use VMWare) Every node seems to be dropping messages (anywhere from 10 to 300) twice a day. I don't know it this has always been the case, but has definitely been going for the past month or so. Whe

Re: How do I upgrade from 2.0.16 to 2.0.17 in my case????

Thanks Michael, I'll try that then. I need to figure out how to do it with Ubuntu's upstart because I've not done it before. On 7 Jan 2016 4:25 pm, "Michael Shuler" wrote: > On 01/07/2016 07:52 AM, Vasileios Vlachos wrote: > > Hello, > > > > My p

How do I upgrade from 2.0.16 to 2.0.17 in my case????

Hello, My problem is described CASSANDRA-10872 . I upgraded a second node on the same cluster in case there was something special with the first node but I experienced identical behaviour. Both cassandra-env.sh and cassandra-rackdc.properties

Re: Thousands of pending compactions using STCS

this behavior. The number of pending compactions was artificially > high, and not meaningful. As long as they number of –Data.db sstables > remains normal, compaction is keeping up and you’re fine. > > - Jeff > > From: Vasileios Vlachos > Reply-To: "user@cass

Re: Upgrade instructions don't make sense

Exactly, thanks! On 23 Nov 2015 11:26 pm, "Vasileios Vlachos" wrote: > If you want to go from 2.0 to 2.1 and you are NOT using vnodes on your > current cluster (that is version 2.0), then make sure you disable them on > the new 2.1 config during the upgrade. Otherwise just l

Re: Upgrade instructions don't make sense

If you want to go from 2.0 to 2.1 and you are NOT using vnodes on your current cluster (that is version 2.0), then make sure you disable them on the new 2.1 config during the upgrade. Otherwise just leave the setting as is. That's how I understand it personally. We are going to upgrade at some po

Re: Downtime-Limit for a node in Network-Topology-Replication-Cluster?

n for your help. On Tue, Oct 27, 2015 at 10:49 PM, Robert Coli wrote: > On Sat, Oct 24, 2015 at 2:02 PM, Vasileios Vlachos < > vasileiosvlac...@gmail.com> wrote: > >> >>> All other means of repair are optimizations which require a certain >>> amount of luck

Re: Downtime-Limit for a node in Network-Topology-Replication-Cluster?

can that be the only way irrespective of everything else. Thanks in advance for your input! On Sat, Oct 24, 2015 at 10:02 PM, Vasileios Vlachos < vasileiosvlac...@gmail.com> wrote: > >> All other means of repair are optimizations which require a certain >> amount of luc

Re: Downtime-Limit for a node in Network-Topology-Replication-Cluster?

> > > All other means of repair are optimizations which require a certain amount > of luck to happen to result in consistency. > Is that true regardless of the CL one uses? So, for example if writing QUORUM and reading QUORUM, wouldn't an increased read_repair_chance probability be sufficient? If

Re: Downtime-Limit for a node in Network-Topology-Replication-Cluster?

; current-live data? > > It's ok if the insertions/deletions of current-live data become a little > slow during the process, but data-consistency must be maintained. If that > is the case, I think we are good. > > > Thanks and Regards, > Ajay > > On Sat, Oct 24, 2015

Re: Downtime-Limit for a node in Network-Topology-Replication-Cluster?

ks and Regards, > Ajay > > On Sat, Oct 24, 2015 at 4:14 PM, Vasileios Vlachos < > vasileiosvlac...@gmail.com> wrote: > >> Hello Ajay, >> >> Have a look in the *max_hint_window_in_ms* : >> >> >> http://docs.datastax.com/en/cassandra/2.0/cassand

Re: Downtime-Limit for a node in Network-Topology-Replication-Cluster?

Hello Ajay, Have a look in the *max_hint_window_in_ms* : http://docs.datastax.com/en/cassandra/2.0/cassandra/configuration/configCassandra_yaml_r.html My understanding is that if a node remains down for more than *max_hint_window_in_ms*, then you will need to repair that node. Thanks, Vasilis

Re: Upgrade Limitations Question

t; Descriptor.java. Looks like for your old and new versions, you'd be looking > for something like: > > for 1.2.1: > $ find -name "*-ib-*" -ls > > for 2.0.1: > $ find -name "*-jb-*" -ls > > > On Wed, Sep 16, 2015 at 10:02 AM, Vasileios Vlacho

Re: Upgrade Limitations Question

Hello Rob and thanks for your reply, At the end we had to wait for the upgradesstables ti finish on every node. Just to eliminate the possibility of this being the reason of any weird behaviour after the upgrade. However, this process might take a long time in a cluster with a large number of node

Re: Upgrade Limitations Question

Any thoughts anyone? On 9 Sep 2015 20:09, "Vasileios Vlachos" wrote: > Hello All, > > I've asked this on the Cassandra IRC channel earlier, but I am asking the > list as well so that I get feedback from more people. > > We have recently upgraded from Cass

Upgrade Limitations Question

Hello All, I've asked this on the Cassandra IRC channel earlier, but I am asking the list as well so that I get feedback from more people. We have recently upgraded from Cassandra 1.2.19 to 2.0.16 and we are currently in the stage where all boxes are running 2.0.16 but nt upgradesstables has not

Re: Replacing dead node and cassandra.replace_address

I think you should be able to see the streaming process by running nodetool netstats. I also think system.log displays similar information about stemming/when stemming is finished. Shouldn't the state of the node change to UP when bootstrap is completed as well? People, correct me if I'm wrong her

CL not satisfied when new node is joining?

Hello, We have a demo cassandra cluster (version 1.2.18) with two DCs and 4 nodes in total. Our client is using the Datastax C# driver (version 1.2.7). RF='DC1':2, 'DC2':2. The consistency level is set to LOCAL_QUORUM and all traffic is coming directly from the application servers in DC1, which th

Re: Best way to alert/monitor "nodetool status” down.

burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com> -- Kind Regards, Vasileios Vlachos IT Infrastructure Engineer MSc Internet & Wireless Computing BEng Electronics Engineering Cisco Certified Network Associate (CCNA)

Re: Should one expect to see hints being stored/delivered occasionally?

situation any better. Apart from increasing the GC logging, I don't see any other way of debugging this further. Thanks for your input, Vasilis On 20/01/15 22:53, Robert Coli wrote: On Sat, Jan 17, 2015 at 3:32 PM, Vasileios Vlachos mailto:vasileiosvlac...@gmail.com>> wrote: Is

Should one expect to see hints being stored/delivered occasionally?

Hello, I thought hints are being stored on /node_A/ every time /node_B/ is unavailable for whatever the reason. I also thought that these hints are being delivered from /node_A/ to /node_B/ when /node_B/ is back and this is true for a /period = max_hint_window_in_ms/. After that hints are dro

Re: Node stuck during nodetool rebuild

as able to successfully complete. The default value for > phi_convict_threshold is 8 with 12 being the maximum recommended value. > > > Mark > > > On Tue, Aug 5, 2014 at 7:22 PM, Robert Coli wrote: > >> On Tue, Aug 5, 2014 at 1:28 AM, Vasileios Vlachos < >> vasileiosvla

Re: Node stuck during nodetool rebuild

ase the phi_convict_threshold in cassandra.yaml from 8 to 10, after > which the rebuild was able to successfully complete. The default value for > phi_convict_threshold is 8 with 12 being the maximum recommended value. > > > Mark > > > On Tue, Aug 5, 2014 at 7:22 PM

Node stuck during nodetool rebuild

Hello All, We are on 1.2.18 (running on Ubuntu 12.04) and we recently tried to add a second DC on our demo environment, just before trying it on live. The existing DC1 has two nodes which approximately hold 10G of data (RF=2). In order to add the second DC, DC2, we followed this procedure: On DC1

Re: Multi-DC Environment Question

hint attributes on a per CF basis, but I was looking for a more generic one to begin with. Any help would be much appreciated. Thanks in advance, Vasilis On Wed, Jun 4, 2014 at 1:42 PM, Vasileios Vlachos < vasileiosvlac...@gmail.com> wrote: > Hello Matt, > > nodetool status: >

Re: Multi-DC Environment Question

assignment looks like ? > > Thanks > > Matt > > > On Wed, Jun 4, 2014 at 8:31 AM, Vasileios Vlachos < > vasileiosvlac...@gmail.com> wrote: > >> I should have said that earlier really... I am using 1.2.16 and Vnodes >> are enabled. >> >> Thanks, >> >> Vasilis >> >> -- >> Kind Regards, >> >> Vasileios Vlachos >> >> >

Re: Multi-DC Environment Question

I should have said that earlier really... I am using 1.2.16 and Vnodes are enabled. Thanks, Vasilis -- Kind Regards, Vasileios Vlachos

Re: Multi-DC Environment Question

hanks, Vasilis On 03/06/14 18:52, Robert Coli wrote: On Fri, May 30, 2014 at 4:08 AM, Vasileios Vlachos mailto:vasileiosvlac...@gmail.com>> wrote: Basically you sort of confirmed that if down_time > max_hint_window_in_ms the only way to bring DC1 up-to-date is anti-entropy

Re: Multi-DC Environment Question

o send the data that was not able to be replicated > initially. > > http://www.datastax.com/dev/blog/modern-hinted-handoff > > -Tupshin > On May 29, 2014 6:22 PM, "Vasileios Vlachos" > wrote: > > Hello All, > > We have plans to add a second DC to our live Cassandra envir

Multi-DC Environment Question

n the outage is < max_hint_window_in_msinstead? Thanks in advance! Vasilis -- Kind Regards, Vasileios Vlachos

Re: Adding datacenter for move to vnodes

Fri, Feb 7, 2014 at 6:41 PM, Robert Coli wrote: > On Fri, Feb 7, 2014 at 5:18 AM, Vasileios Vlachos < > vasileiosvlac...@gmail.com> wrote: > >> Say you have 6 nodes with 300G each. So you decommission N1 and you bring >> it back in with Vnodes. Is that going to stream

Re: Adding datacenter for move to vnodes

y 1. Might not be an issue on a dev > or demo cluster but it will certainly be in a production environnement. > > > > > 2014-02-07 0:28 GMT+01:00 Andrey Ilinykh : > >> My understanding is you can't mix vnodes and regular nodes in the same >> DC. Is it correct? >&

Re: Adding datacenter for move to vnodes

Hello, My question is why would you need another DC to migrate to Vnodes? How about decommissioning each node in turn, changing the cassandra.yaml accordingly, delete the data and bring the node back in the cluster and let it bootstrap from the others? We did that recently with our demo cluster.

Re: Unreachable Nodes

ll restart => entire cluster down => down time. It is precisely *not* > a rolling restart. > > To conclude I would say that your cluster seems healthy now (from what I > can see), you have no more ghost nodes and nothing to do. Just wait a week > or so and look for gossipinfo again

Unreachable Nodes

Hello All, A while ago we had 3 cassandra nodes on Amazon. At some point we decided to buy some servers and deploy cassandra there. The problem is that since then we have a list of dead IPs listed as UNREACHABLE nodes when we run describe cluster on cassandra-cli. I have seen other posts which de

Re: Replication Factor and Consistency Level Confusion

> Writing any key in range 11-15 with consistency TWO will fail (C is down > and 11-15 is its primary range) > Writing any key in range 6-10 with consistency TWO will fail (C is down > and it is the replica for this range) > > I hope this explains it. > > -Ursprüng

Replication Factor and Consistency Level Confusion

Hello All, We have a 3-node cluster and we created a keyspace (say Test_1) with Replication Factor set to 3. I know is not great but we wanted to test different behaviors. So, we created a Column Family (say cf_1) and we tried writing something with Consistency Level ANY, ONE, TWO, THREE, QUORUM a

Re: Using Cassandra to store binary files?

r project needs changed and Cassandra has now begun playing a more > >>critical role as it has matured (since the 0.7 days), in retrospect HDFS > >>might have been a better option long term as I really will never need > >>indexing etc on my binary blobs and the convenience

Using Cassandra to store binary files?

Hello All, We need to store about 40G of binary files in a redundant way and since we are already using Cassandra for other applications we were thinking that we could just solve that problem using the same Cassandra cluster. Each individual File will be approximately 1MB. We are thinking that th

Re: Thrift version and OOM errors

Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 5/07/2012, at 4:58 PM, Tristan Seligmann wrote: > > On Jul 4, 2012 2:02 PM, "Vasileios Vlachos" > wrote: > > > > Any ideas what could be causing strange message lengths? &

Re: Thrift version and OOM errors

, Vasilis On Wed, Jul 4, 2012 at 12:55 PM, Vasileios Vlachos < vasileiosvlac...@gmail.com> wrote: > Hello Aaron, thanks for your email. > > - That's pretty small, try m1.xlarge. > > Yes, this is small. We are aware of that, but that doesn't seem to be the > act

Re: Thrift version and OOM errors

th a stock 1.0.X install and a pre-built client ? > > Cheers > > > ----- > Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 3/07/2012, at 9:57 AM, Vasileios Vlachos wrote: > > Hello All, > > We are using

Re: Thrift version and OOM errors

???). Thanks, Vasilis On Mon, Jul 2, 2012 at 10:57 PM, Vasileios Vlachos < vasileiosvlac...@gmail.com> wrote: > Hello All, > > We are using Cassandra 1.0.7 on AWS on mediums (that is 3.8G RAM, 1 Core), > running Ubuntu 12.04. We have three nodes in the cluster and we hit only &

Thrift version and OOM errors

Hello All, We are using Cassandra 1.0.7 on AWS on mediums (that is 3.8G RAM, 1 Core), running Ubuntu 12.04. We have three nodes in the cluster and we hit only one node from our application. Thrift version is 0.6.1 (we changed from 0.8 because we thought there was a compatibility problem between th

Re: Cassandra running out of memory?

your application will need. Hope that helps. - Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 13/04/2012, at 2:19 AM, Vasileios Vlachos wrote: Hello Aaron, Thank you for getting back to me. I will change to m1.large first to see how long it

Re: Cassandra running out of memory?

experimenting I would suggest using the larger instances > so you can make some progress. Once you have a feel for how things work you > can then try to match the instances to your budget. > > Hope that helps. > > - > Aaron Morton > Freelance Developer >