Re: Reg:- CQL SOLR Query Not gives result

This is a question for datastax support, not the Apache mailing list. Folks here are more than happy to help with open source, Apache Cassandra questions, if you've got one. On Thu, May 11, 2017 at 9:06 PM @Nandan@ wrote: > Hi , > > In my table, I am having few

Reg:- CQL SOLR Query Not gives result

Hi , In my table, I am having few records and implemented SOLR for partial search but not able to retrieve data. SELECT * from revall_book_by_title where solr_query = 'language:中'; SELECT * from revall_book_by_title where solr_query = 'language:中*'; None of them are working. Any suggestions.

Re: cassandra 3.10

Hi Dhruva, There are definitely some performance improvements to Storage Engine in Cassandra 3.10 which make it worth the upgrade. Note that Cassandra 3.11 has further bug fixes and it may be worth considering a migration to that version. Regarding the issue of building a Cassandra 3.10 RPM, it

Re: Nodes stopping

I'm switching the instances to machines with 61G of RAM, in this case would you still recommend using 8G of heap space?Here is a gist of my heap settings from jvm.optionshttps://gist.github.com/dlsteuer/40e80280029897e6bb5fd12f2a86cbbe On May 11 2017, at 3:08

Re: Nodes stopping

Hi Daniel, Could you paste the exact GC options in use? Also 30 GB is not much. I would not use more than 8 GB for the JVM and probably CMS in those conditions for what it is worth. The thing is if memtables, bloom filter, caches, indexes, etc are off heap, then you probably ran out of Native

Re: Drop tables takes too long

Hi We were trying to overcome OOM crashes. Fair enough :-). We changed settings to default on one node. GC times became about two times > smaller on that node. > That's encouraging! Looks like even if the number of tables is really high, there is still space for optimization. Have you made

Re: Nodes stopping

Thank you, it's an Out of memory crash according to dmesg. I have the heap size set to 15G in the jvm.options for cassandra, and there is 30G on the machine. On May 11 2017, at 2:22 pm, Cogumelos Maravilha wrote:

Re: Nodes stopping

I had 2 nodes go down today, here is the ERRORs from the system log on both nodeshttps://gist.github.com/dlsteuer/28c610bc733a2bff22c8d3953ef8c218For some context, I'm trying to get regular repairs going but am having issues with it. On May 11 2017, at 2:10 pm,

Re: Nodes stopping

Can you grep ERROR system.log On 11-05-2017 21:52, Daniel Steuernol wrote: > There is nothing in the system log about it being drained or shutdown, > I'm not sure how else it would be pre-empted. No one else on the team > is on the servers and I haven't been shutting them down. There also is >

Re: Nodes stopping

Maybe this article helps you. http://stackoverflow.com/questions/26285133/who-sends-a-sigkill-to-my-process-mysteriously-on-ubuntu-server On Thu, May 11, 2017 at 1:52 PM, Daniel Steuernol wrote: > There is nothing in the system log about it being drained or shutdown, I'm

Re: AWS Cassandra backup/Restore tools

Blake is correct. OpsCenter 6.0 and up doesn't work with OSS C*. @Nitan: We have made some substantial changes to the Opscenter 6.1 backup service, specifically when it comes to S3 backups. Having said this, I am not going to be sale-sy here. If folks need some help or need more clarity to know

Re: AWS Cassandra backup/Restore tools

Also , Opscenter backup/restore does not work for large databases Sent from my iPhone > On May 11, 2017, at 3:41 PM, Blake Eggleston wrote: > > OpsCenter 6.0 and up don't work with Cassandra. > >> On May 11, 2017 at 12:31:08 PM, cass savy (casss...@gmail.com) wrote: >>

Re: Nodes stopping

There is nothing in the system log about it being drained or shutdown, I'm not sure how else it would be pre-empted. No one else on the team is on the servers and I haven't been shutting them down. There also is no java memory dump on the server either. It appears that the process just died.

Re: Cassandra Snapshots and directories

I did not get your question completely, with "snapshot files are mixed with files and backup files". When you call nodetool snapshot, it will create a directory with snapshot name if specified or current timestamp at /data///backup/. This directory will have all sstables, metadata files and

Re: AWS Cassandra backup/Restore tools

OpsCenter 6.0 and up don't work with Cassandra. On May 11, 2017 at 12:31:08 PM, cass savy (casss...@gmail.com) wrote: AWS Backup/Restore process/tools for C*/DSE C*: Has anyone used Opscenter 6.1 backup tool to backup/restore data for larger datasets online ? If yes, did you run into issues

Re: Nodes stopping

What do you mean by "no obvious error in the logs", do you see node was drained or shutdown. Are you sure, no other process is calling nodetool drain or shutdown, OR pre-empting cassandra process? On Thu, May 11, 2017 at 1:30 PM, Daniel Steuernol wrote: > > I have a 6

Re: repair question (-dc option)

If there was no node down during that period, and you are using LOCAL_QUORUM read/write, then yes above command works. On Thu, May 11, 2017 at 11:59 AM, Gopal, Dhruva wrote: > Hi – > > I have a question on running a repair after bringing up a node that was > down

Re: Nodetool cleanup doesn't work

ok thank you On Thu, May 11, 2017 at 1:11 PM, Jeff Jirsa wrote: > No, it's not expected, but it's pretty obvious from reading the code > what'll happen. Opened https://issues.apache.org/jira/browse/CASSANDRA- > 13526 > > > > > > On Thu, May 11, 2017 at 12:53 PM, Jai Bheemsen

Nodes stopping

I have a 6 node cassandra cluster running, and frequently a node will go down with no obvious error in the logs. This is starting to happen quite often, almost daily now. Any suggestions on how to track down what is causing the node to stop?

Re: Nodetool cleanup doesn't work

No, it's not expected, but it's pretty obvious from reading the code what'll happen. Opened https://issues.apache.org/jira/browse/CASSANDRA-13526 On Thu, May 11, 2017 at 12:53 PM, Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > Yes I have many keyspaces which are not spread

Re: Nodetool cleanup doesn't work

Yes I have many keyspaces which are not spread across all the data centers(expected by design). In this case, is this the expected behavior cleanup will not work for all the keyspaces(nodetool cleanup)? is it going to be fixed in the latest versions? P.S: Thanks for the tip, I can workaround this

RE: Repairs on 2.1.12

The repair on the DC has completed in 308 hours. What would be helpful is if anyone has a good way of monitoring a manual ‘antientropy’ repair. Thanks Mark 801-705-7115 office From: kurt greaves [mailto:k...@instaclustr.com] Sent: Thursday, May 11, 2017 1:06 AM To: Mark Furlong

AWS Cassandra backup/Restore tools

AWS Backup/Restore process/tools for C*/DSE C*: Has anyone used Opscenter 6.1 backup tool to backup/restore data for larger datasets online ? If yes, did you run into issues using that tool to backup/restore data in PROD that caused any performance or any other impact to the cluster? If no,

Re: Nodetool cleanup doesn't work

If you didn't explicitly remove a keyspace from one of your datacenters, the next most likely cause is that you have one keyspace that's NOT replicated to one of the datacenters. You can work around this by running 'nodetool cleanup ' on all of your other keyspaces individually, skipping the one

repair question (-dc option)

Hi – I have a question on running a repair after bringing up a node that was down (brought down gracefully) for a few days within a data center. Can we just run nodetool repair –dc on a single node (within that DC – specifically the downed node, after it is brought online) and have that

Re: LCS, range tombstones, and eviction

Hi Stefano, Based on what I understood reading the docs, if the ratio of garbage  collectable tomstones exceeds the "tombstone_threshold", C* should start  compacting and evicting. If there are no other normal compaction tasks to be run, LCS will attempt to compact the sstables it estimates it

Re: Node containing all data of the cluster

Thank you Varun and DuyHai! 2017-05-10 20:57 GMT-03:00 Varun Gupta : > Hi Igor, > > You can setup cluster with configuration as below. > > Replication: DC1: 3 and DC2: 1. > > If you are using datastax java driver, then use dcaware load balancing > policy and pass DC1, as input.

Re: Nodetool cleanup doesn't work

Thanks Jeff, I have a C* cluster spread across multiple datacenter. reason for cleanup : I added multiple nodes to cluster and need to run cleanup on old nodes so that the redundant data is cleaned-up. On Thu, May 11, 2017 at 11:08 AM, Jeff Jirsa wrote: > > > On 2017-05-10

Re: Nodetool cleanup doesn't work

On 2017-05-10 22:44 (-0700), Jai Bheemsen Rao Dhanwada wrote: > Hello, > > I am running into an issue where *nodetool cleanup *fails to cleanup data. > We are running 2.1.16 version of Cassandra. > > > [user@host ~]$ nodetool cleanup > Aborted cleaning up atleast one

Re: Strange Cassandra startup error

On 2017-05-11 07:26 (-0700), William Boutin wrote: > I've been running apache-cassandra 2.2.6 for a few years. Recently when I > configured a new cassandra node and started Cassandra via "service start > cassandra" on LINUX 6.5, I got the following exception.

Re: DSE 5.0 Upgrade

Hi Cass Savy I would suggest directing your question to Datastax, or you could look at an open source alternative such as Apache Cassandra :) Ben On Wed, 10 May 2017 at 22:50 cass savy wrote: > Team, > > 1. What is the stable version for DSE 5.0 to upgrade from DSE 4.8.x?

Re: Cassandra 2.1.13: Using JOIN_RING=False

A rough guess on the best way to do this with cql, without looking too deeply into it: You would likely have to implement a custom load balancing policy within the driver that only uses coordinator nodes and/or modify refreshNodeListAndTokenMap() behaviour in ControlConnection.java (there should

Re: Reg:- Apache Solr with DSE Query

Hi Nandan I would suggest referring your question to Datastax, otherwise you could look at some open source alternatives such as: https://github.com/strapdata/elassandra https://github.com/Stratio/cassandra-lucene-index Cheers Ben On Thu, 11 May 2017 at 03:06 @Nandan@

Re: Cassandra 2.1.13: Using JOIN_RING=False

1. The coordinator still store system data and hints, but they should not store any user data since they are not part of ring. 2. We are using coordinator for thrift client. For cql based drivers, they needs to talk to nodes in the ring, so I think coordinator mode won't work for them. -Dikang

Re: NoSE: Automated schema design for Cassandra

Thanks for the feedback! I did change column families to tables. I agree the documentation could use some work. If you're interested in seeing what the input and output look like, here's a sample: https://michael.mior.ca/projects/nose/rubis So far we haven't had any schemas used directly for

Strange Cassandra startup error

I've been running apache-cassandra 2.2.6 for a few years. Recently when I configured a new cassandra node and started Cassandra via "service start cassandra" on LINUX 6.5, I got the following exception. After cleaning out my data_file_directories I was able to successfully restart. Any ideas?

LCS, range tombstones, and eviction

Hi all, I am trying to wrap my head around how C* evicts tombstones when using LCS. Based on what I understood reading the docs, if the ratio of garbage collectable tomstones exceeds the "tombstone_threshold", C* should start compacting and evicting. I am quite puzzled however by what might

Reg:- Apache Solr with DSE Query

Hi, Details are as below:- 1) Have table:- video_info 2) PRIMARY KEY:- video_id UUID 3) having records around 5. 4) Table is having around 30-35 columns 5) Using DSE 4.8 Need clarifications and suggestions:- 1) I need to search by few 3-4 columns like Video_title, video_actor etc.. 2) If I

Cassandra Snapshots and directories

Hi, I am going through this guide to do backup/restore of cassandra data to a new cluster: http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_backup_snapshot_restore_t.html#task_ds_cmf_11r_gk When creating a snapshot I get the snapshot files mixed in with the normal data files and

Re: Difference between yum and git

Thanks Jonathan, Joaquin, Sorry, I found logback.xml caused the difference. I changed logging level TRACE and the maxFileSize of debug.log in conf/logback.xml. logback.xml of C* by yum (changed): logginglevel: TRACE maxFileSize of debug.log: 500MB logback.xml of C* by git (default):

Re: Repairs on 2.1.12

to clarify, what exactly was your repair command, and in reference to a ring did you mean the DC or the cluster, and has the repair been running for 2 weeks or is that in reference to the "ring"? It would be helpful if you provided the relevant logs as well, also, the cassandra version you are