Re: Getting error while issuing Cassandra stress

Well this certainly looks like the case to me. Changing the RF did the trick. The test ran fine, but I could still observe the same exception here and there when threads are high. On 24 Jan 2016 10:12 pm, "Carlos Alonso" wrote: > Before closing this. > > Would the reason possibly be that with Si

Re: Getting error while issuing Cassandra stress

Before closing this. Would the reason possibly be that with SimpleStrategy and RF=1 the data is only on one node on a single DC, and when the driver was connecting to the other DC, LOCAL_ONE could not be achieved? Regards. Carlos Alonso | Software Engineer | @calonso

Re: Getting error while issuing Cassandra stress

Hi Alan, You have hit bulls eye! I used a custom yaml file for configuring keyspace, used NTT and multiple replications for each cluster, defined table schema and query and it seemed to work great!! I have some apprehensions here though. The tests that I have done did not yield results that I exp

Re: Getting error while issuing Cassandra stress

> > telnet 10.41.55.18 7199 # doesnt connect > Trying 10.41.55.18... > telnet: connect to address 10.41.55.18: Connection refused > > Could this be the reason? > I don't think so. But I have not a clue on what's going on... Did you tried this ? - Try increasing the RF / Strategy in the stress to

Re: Getting error while issuing Cassandra stress

Alright, I uninstalled the DSE from all the nodes in the cluster and reinstalled them again from scratch. Ran nodetool status and output is U/N for all nodes again. Tried running cassandra-stress and it doesnt work. I can see in the system.peer table that token ranges has been distributed, furthe

Re: Getting error while issuing Cassandra stress

> > Should I use nodetool repair utility > That wouldn't help, this an anti-entropy mechanism (see https://docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsRepair.html#toolsRepair__description_unique_27 ). It is something really important too often left aside. Yet, your issue here is not

Re: Getting error while issuing Cassandra stress

Getting same exception again. Should I use nodetool repair utility? On Sat, Jan 23, 2016 at 3:10 AM, Sebastian Estevez < sebastian.este...@datastax.com> wrote: > https://github.com/brianmhess/cassandra-loader > > All the best, > > > [image: datastax_logo.png] > > Sebast

Re: Getting error while issuing Cassandra stress

Hi Bhuvan, I guess this info will be useful --> https://docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsCStress_t.html#task_ds_rnm_r53_gk__view-schema-help You could try defining you own settings for the schema (NetworkTopologyStrategy, RF of your choice). Yet SimpleStrategy should work

Re: Getting error while issuing Cassandra stress

https://github.com/brianmhess/cassandra-loader All the best, [image: datastax_logo.png] Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png] [image: facebook.png]

Re: Getting error while issuing Cassandra stress

Yes im specifying -node parameter to stress, otherwise it throws network connection failed. Can you point me to a sample java application to test pushing data from external server? Let's see if that works On Sat, Jan 23, 2016 at 2:55 AM, Sebastian Estevez < sebastian.este...@datastax.com> wrote:

Re: Getting error while issuing Cassandra stress

> > when i opened my cassandra-rackdc.properties i saw that DC names were DC1 > & DC2, rack name was RAC1 . Please note that this is the default > configuration, I have not modified any file. cassandra-rackdc.properties is only respected based on your snitch

Re: Getting error while issuing Cassandra stress

I had a look at the jira below: https://issues.apache.org/jira/browse/CASSANDRA-7905 when i opened my cassandra-rackdc.properties i saw that DC names were DC1 & DC2, rack name was RAC1 . Please note that this is the default configuration, I have not modified any file. There is another point of co

Re: Getting error while issuing Cassandra stress

Sorry I missed that. Both your nodetool status and keyspace replication settings say Cassandra and Analytics for the DC names. I'm not sure where you're seeing DC1, DC2, etc. and why you suspect that is the problem. All the best, [image: datastax_logo.png] Sebastián

Re: Getting error while issuing Cassandra stress

Thanks for the response Alain, cqlsh> create keyspace mykeyspace WITH replication = {'class':'NetworkTopologyStrategy', 'Analytics':2, 'Cassandra':3} cqlsh> use mykeyspace; cqlsh:mykeyspace>create table mytable (id int primary key, name text, address text, phone text); cqlsh:mykeyspace> insert int

Re: Getting error while issuing Cassandra stress

Hi Sebastian, I had attached nodetool status output in previous mail, pasting it again : $ nodetool status Datacenter: Analytics = Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- Address Load Tokens Owns Host ID Rack UN 10.41.55.17 428.5 KB 256 ? 39d6d585-e641-4046-9d

Re: Getting error while issuing Cassandra stress

The output of `nodetool status` would help us diagnose. All the best, [image: datastax_logo.png] Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png] [image: facebook.

Re: Getting error while issuing Cassandra stress

Hi, The the exact command you ran (stress-tool with options) could be useful to help you on that. However, Im able to create keyspace, tables and insert data using cqlsh and > it is replicating fine to all the nodes. Having the schema might be useful too. Did you ran the cqlsh and the stress-t

Getting error while issuing Cassandra stress

Hi, i have created a POC cluster with 2 DC , each having 4 nodes with DSE 4.8.1 installed. On issuing cassandra stress im getting an error and data is not being inserted: *com.datastax.driver.core.exceptions.UnavailableException: Not enough replica available for query at consistency LOCAL_ONE (1