Re: cqlsh COPY ... TO ... doesn't work if one node down

[Errno None] Tried connecting to > [('10.0.0.47', 9042)]. Last error: timed out > 2018-06-29 19:21:40,064 Error attempting to reconnect to 10.0.0.47, > scheduling retry in 512.0 seconds: [Errno None] Tried connecting to > [('10.0.0.47', 9042)]. Last error: timed out > :1:(4, 'Interrupted

Re: Frequency of rebuild_index

le? > Is there any documentation which says the index automatically > rebuilds/keeps itself up to date after updations and deletions. Also if > there anything specific to stratio-lucene-index. > > Regards > Akshit Jain > 9891724697 > > On Fri, Apr 27, 2018 at 9:59 AM, Anup

Re: Frequency of rebuild_index

If you want to use extensive search like functionality or special kind of secondary indexing you can explore the stratio-lucene-index option. Thanks, Anup On 3 May 2018 at 10:02, Anup Shirolkar <anup.shirol...@instaclustr.com> wrote: > Hi, > > when can the discrepancy in the i

Re: Frequency of rebuild_index

Hi, The secondary indices in Cassandra are maintained continuously as data is written. Also index rebuilding is kicked off automatically when you create a new index. So, there is no good reason to schedule nodetool rebuild_index regularly. However, if you find any discrepancy in the index and

Re: User Defined Types?

: > Hi All, > > Are there any known caveats for User Defined Types in Cassandra (version > 3.0)? > One of our teams wants to start using them. I wish to assess it and see if > it'd be wise (or not) to refrain from using UDTs. > > > Thanks! > -- Anup Shirolka

Re: Cassandra 3.7 - Problem with Repairs - all nodes failing

, Anup Shirolkar <anup.shirol...@instaclustr.com> wrote: > Hi Leena, > > The repairs are most likely failing because of some bug in Cassandra 3.7. > I don't have a JIRA reference handy but there are quite some issues in this > version. > > Considering your scenario, it is

Re: Large size KS management

Hi Aiman, Can you please clarify whether the mentioned size of 800GB is considering Replication Factor(RF) or without it ? If yes, what is the RF ? Also, what is the method used to measure keyspace data size e.g size of directory, nodetool command etc. It would be helpful to know about the

Re: Cassandra 3.7 - Problem with Repairs - all nodes failing

Hi Leena, The repairs are most likely failing because of some bug in Cassandra 3.7. I don't have a JIRA reference handy but there are quite some issues in this version. Considering your scenario, it is highly recommended that you should upgrade to 3.11.1. Although, you have mentioned that

Re: Nodetool info for heap usage

Hi, The nodetool output should be accurate and reliable. But using nodetool command for monitoring is not a very good idea. Nodetool has its own resource overhead each time it is invoked. You should ideally use a standard monitoring tool/method. Regards, Anup Shirolkar On Tue, 23 Oct 2018

Re: Upgrade to version 3

. https://github.com/apache/cassandra/blob/trunk/NEWS.txt Please see below mail archive for your case of 2.2 to 3.x : https://www.mail-archive.com/user@cassandra.apache.org/msg45381.html Regards, Anup Shirolkar On Thu, 18 Oct 2018 at 09:30, Mun Dega wrote: > Hello, > > If we are

Re: Cassandra DCOS | monitoring connection and user activity

/instrumenting/exporters/ https://grafana.com/dashboards/5408 http://thelastpickle.com/blog/2017/04/05/cassandra-graphite-measurements-filtered.html Regards, Anup Shirolkar On Wed, 31 Oct 2018 at 18:41, Caesar, Maik wrote: > Hello All, > > have someone experience with monitoring

Re: Merge Cassandra RACs?

unique rack situation, why have you run out of racks ? Are you currently installing each node on a new rack at the moment ? There could be simpler alternatives depending upon your rack/data centre situation. Regards, Anup Shirolkar On Fri, 26 Oct 2018 at 04:52, Ian Spence wrote

Re: Upgraded to 3.0.17, stop here or move forward?

config updates (patch existing config) - start Cassandra - *upgradesstables* *Not to forget*: Perform upgrade on one node at a time. Regards, Anup Shirolkar Instaclustr <https://www.instaclustr.com/> On Wed, 10 Oct 2018 at 00:30, Riccardo Ferrari wrote: > Hi list, > > We recent

Re: Upgraded to 3.0.17, stop here or move forward?

impact complete cluster performance. Hope this helps. Regards, Anup Shirolkar On Wed, 10 Oct 2018 at 20:11, Riccardo Ferrari wrote: > Thank you Anup, > > Yup, the upgradesstables is a step I generally take before (to make sure > I'm on the latest version) and after to m

Re: Odd CPU utilization spikes on 1 node out of 30 during repair

happens next time instead of just restarting? > > Cheers, > -- > Alex > > > - > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org -- Anup Shirolkar Co

Re: Odd CPU utilization spikes on 1 node out of 30 during repair

CPU at times. You can check per process CPU consumption to keep an eye on non-Cassandra processes. Regards, Anup Shirolkar On Wed, 26 Sep 2018 at 21:32, Oleksandr Shulgin < oleksandr.shul...@zalando.de> wrote: > On Wed, Sep 26, 2018 at 1:07 PM Anup Shirolkar < > anup.shirol...@