Hi,
I found this blog quite helpful:
https://www.instaclustr.com/deep-diving-into-cassandra-stress-part-1/
on 1, not sure if I understand your question correctly, but I would not
start the stress test process on a Cassandra node which will be under test.
on 3, the tool has already with an option
Hello Folks,
Does any body refer good documentation on Cassandra stress test.
I have below questions.
1) Which server is good to start the test, Cassandra server or Application
server.
2) I am using Datastax Java driver, is any good documentation for stress test
specific to this driver.
3
Have you read through the docs for stress? You can have it use your own
queries and data model.
http://cassandra.apache.org/doc/latest/tools/cassandra_stress.html
On Sun, Nov 26, 2017 at 1:02 AM Akshit Jain wrote:
> Hi,
> What is the best way to stress test the cassandra cluster with rea
Hi,
What is the best way to stress test the cassandra cluster with real life
workloads which is being followed currently?
Currently i am using cassandra stress-tool but it generated blob data /yaml
files provides the option to use custom keyspace.
But what are the different parameters values
The user and password should be in -mode section, for example:
./cassandra-stress user profile=table.yaml ops\(insert=1\) -mode native
cql3 user=** password=**
http://docs.datastax.com/en/cassandra/3.0/cassandra/tools/toolsCStress.html
/Jay
On 7/27/17 2:46 PM, Greg Lloyd wrote:
> I am trying to
I am trying to use the cassandra stress tool with the user
profile=table.yaml arguments specified and do authentication at the same
time. If I use the user profile I get an error Invalid parameter user=* if
I specify a user and password.
Is it not possible to specify a yaml and use authenticat
om
2017-04-24 15:08 GMT+02:00 LuckyBoy :
> unsubscribe
>
> On Thu, Apr 13, 2017 at 7:26 AM, eugene miretsky <
> eugene.miret...@gmail.com> wrote:
>
>> Hi,
>>
>> I'm trying to do a stress test on a a table with a collection column, but
>>
unsubscribe
On Thu, Apr 13, 2017 at 7:26 AM, eugene miretsky
wrote:
> Hi,
>
> I'm trying to do a stress test on a a table with a collection column, but
> cannot figure out how to do that.
>
> I tried
>
> table_definition: |
> CREATE TABLE list (
> c
Hi,
Collections are not supported in cassandra-stress tool.
I suggest you use Jmeter with cassandra java driver to do your stress test
with collection or Spark.
2017-04-13 16:26 GMT+02:00 eugene miretsky :
> Hi,
>
> I'm trying to do a stress test on a a table with a collecti
Hi,
I'm trying to do a stress test on a a table with a collection column, but
cannot figure out how to do that.
I tried
table_definition: |
CREATE TABLE list (
customer_id bigint,
items list,
PRIMARY KEY (customer_id));
columnspec:
- name: customer_id
size: fix
Your insert settings look unrealistic since I doubt you would be
writing 50k rows at a time. Try to set this to 1 per partition and
you should get much more consistent numbers across runs I would think.
select: fixed(1)/10
On Wed, Mar 4, 2015 at 7:53 AM, Nisha Menon wrote:
> I have been usin
I have been using the cassandra-stress tool to evaluate my cassandra
cluster for quite some time now. My problem is that I am not able to
comprehend the results generated for my specific use case.
My schema looks something like this:
CREATE TABLE Table_test(
ID uuid,
Time timestamp,
I have been using the cassandra-stress tool to evaluate my cassandra
cluster for quite some time now. My problem is that I am not able to
comprehend the results generated for my specific use case.
My schema looks something like this:
CREATE TABLE Table_test(
ID uuid,
Time timestamp,
smaller loads (ie
>> when a client cannot fully saturate a single node).
>>
>> Main thing to expect is that latency will plateau and remain fairly
>> constant as load/nodes increase while throughput potential will linearly
>> (empirically at least) increase.
>>
>
fairly
>> constant as load/nodes increase while throughput potential will linearly
>> (empirically at least) increase.
>>
>> You should really attempt it with the native binary + prepared
>> statements, running cql over thrift is far from optimal. I would recommend
>&g
increase while throughput potential will linearly
> (empirically at least) increase.
>
> You should really attempt it with the native binary + prepared statements,
> running cql over thrift is far from optimal. I would recommend using the
> cassandra-stress tool if you want to stress test
+ prepared statements,
running cql over thrift is far from optimal. I would recommend using the
cassandra-stress tool if you want to stress test Cassandra (and not your
code)
http://www.datastax.com/dev/blog/improved-cassandra-2-1-stress-tool-benchmark-any-schema
===
Chris Lohfink
On Sun, Dec 7, 2014 at
mall (on that hardware you won't keep up with
> compaction), and your tests are again testing scenarios you wouldn't
> actually see in production.
>
> On Sat Dec 06 2014 at 7:09:18 AM kong wrote:
>
>> Hi,
>>
>> I am doing stress test on Datastax Cassandra
th small sample sizes of ~1 million).
>
> If you expect to sustain write volumes like this, you'll find these
> clusters are sized too small (on that hardware you won't keep up with
> compaction), and your tests are again testing scenarios you wouldn't
> actually see in p
ple sizes of ~1 million).
If you expect to sustain write volumes like this, you'll find these
clusters are sized too small (on that hardware you won't keep up with
compaction), and your tests are again testing scenarios you wouldn't
actually see in production.
On Sat Dec 06 2014 at 7:
Hi,
I am doing stress test on Datastax Cassandra Community 2.1.2, not using the
provided stress test tool, but use my own stress-test client code instead(I
write some C++ stress test code). My Cassandra cluster is deployed on Amazon
EC2, using the provided Datastax Community AMI( HVM instances
o reproduce them. But
> offhand, I don't see any to throttle back the load created by the
> stress test.
I'm not aware of one built-in. It would be a useful patch IMO, to
allow setting a target rate.
--
/ Peter Schuller (@scode, http://worldmodscode.wordpress.com)
, but I
thought it made sense to use the official benchmark tool as people might
more readily believe those results and/or be able to reproduce them. But
offhand, I don't see any to throttle back the load created by the
stress test.
On Mon, Dec 19, 2011 at 09:47:32PM -0800, Peter Schuller w
> Thanks for your input. Can you tell me more about what we should be
> looking for in the gc log? We've already got the gc logging turned
> on and, and we've already done the plotting to show that in most
> cases the outliers are happening periodically (with a period of
> 10s of seconds to a fe
Peter,
Thanks for your input. Can you tell me more about what we should be
looking for in the gc log? We've already got the gc logging turned
on and, and we've already done the plotting to show that in most
cases the outliers are happening periodically (with a period of
10s of seconds to a fe
> I'm trying to understand if this is expected or not, and if there is
Without careful tuning, outliers around a couple of hundred ms are
definitely expected in general (not *necessarily*, depending on
workload) as a result of garbage collection pauses. The impact will be
worsened a bit if you are
sing the official java "stress" tool. The problem, at least
for this purpose, is that the stress tool only reports *average*
response times over the measurement intervals.This effectively
hides the large value if they are infrequent relative to measurement
interval. I've mod
Have you run repair on the nodes ? Maybe some data was lost and not repaired
yet ?
Philippe
2011/8/23 Chris Marino
> Hi, we're running some performance tests against some clusters and I'm
> curious about some of the numbers I see.
>
> I'm running the stress t
Hi, we're running some performance tests against some clusters and I'm
curious about some of the numbers I see.
I'm running the stress test against two identically configured clusters, but
after I run at stress test, I get different Load values across the
clusters?
The difference
do? What is the usage of this
> >> tool... Please explain
> >>
> >> On Fri, Jul 22, 2011 at 6:39 PM, Jonathan Ellis
> wrote:
> >>>
> >>> What does nodetool ring say?
> >>>
> >>> On Fri, Jul 22, 2011 at 12:43 AM, Nilabj
; I too wanna know what this stress tool do? What is the usage of this
>> tool... Please explain
>>
>> On Fri, Jul 22, 2011 at 6:39 PM, Jonathan Ellis wrote:
>>>
>>> What does nodetool ring say?
>>>
>>> On Fri, Jul 22, 2011 at 12:43 AM, Nilab
es nodetool ring say?
>>
>> On Fri, Jul 22, 2011 at 12:43 AM, Nilabja Banerjee
>> wrote:
>> > Hi All,
>> >
>> > I am following this following link "
>> > http://www.datastax.com/docs/0.7/utilities/stress_java " for a stress
>> test.
Banerjee
> wrote:
> > Hi All,
> >
> > I am following this following link "
> > http://www.datastax.com/docs/0.7/utilities/stress_java " for a stress test.
> > I am getting this notification after running this command
> >
> > xxx.xxx.xxx.xx=
> > I am following this following link "
> > http://www.datastax.com/docs/0.7/utilities/stress_java " for a stress
> test.
> > I am getting this notification after running this command
> >
> > xxx.xxx.xxx.xx= my ip
> >
> > contrib/stress/bin/
What does nodetool ring say?
On Fri, Jul 22, 2011 at 12:43 AM, Nilabja Banerjee
wrote:
> Hi All,
>
> I am following this following link "
> http://www.datastax.com/docs/0.7/utilities/stress_java " for a stress test.
> I am getting this notification after running this c
is less than CL nodes
> UP when the request starts.
>
> It seems odd to get it in this case because the default replication factor
> used by stress test is 1. How many nodes do you have and have you made any
> changes to the RF ?
>
> Also check the server side logs
UnavailableException is raised server side when there is less than CL nodes UP
when the request starts.
It seems odd to get it in this case because the default replication factor used
by stress test is 1. How many nodes do you have and have you made any changes
to the RF ?
Also check the
Have you checked the logs on the nodes to see if there are any
errors?
On 7/21/11 10:43 PM, Nilabja Banerjee wrote:
Hi All,
I am following this following link " http://www.datastax.com/docs/0.7/utilities/stress_java
" for a stress test. I
Hi All,
I am following this following link " *
http://www.datastax.com/docs/0.7/utilities/stress_java *" for a stress test.
I am getting this notification after running this command
*xxx.xxx.xxx.xx= my ip*
*contrib/stress/bin/stress -d xxx.xxx.xxx.xx*
*Created keyspaces. Sleep
meout-during-stress-test-tp6262430p6265925.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
output of cfstats. Does cfhistograms provide better info?
>
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Timeout-during-stress-test-tp6262430p6263859.html
> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
> Nabble.com.
0 req per sec.
Not sure how to intepret the iostats output with things happening async in
cassandra. Can you give little description on how to interpret it?
I have posted output of cfstats. Does cfhistograms provide better info?
--
View this message in context:
http://cassandra-user-incubator-apache-
gt; then
> > mean cassandra is down for clients in this scenario? That would be bad.
> >
> > --
> > View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Timeout-during-stress-test-tp6262430p6263270.html
> > Sent from th
Avg CPU only 20%, No GC issues that I see. I
> would expect cassandra to be able to process more with 6 nodes, 12 core, 96
> GB RAM and 4 GB heap.
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Timeout-during-stress-test-
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Timeout-during-stress-test-tp6262430p6263470.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
? That would be bad.
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Timeout-during-stress-test-tp6262430p6263270.html
> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
> Nabble.com.
It looks like hector did retry on all the nodes and failed. Does this then
mean cassandra is down for clients in this scenario? That would be bad.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Timeout-during-stress-test-tp6262430p6263270.html
cache hit rate: 0.002453626459907744
>Row cache: disabled
>Compacted row minimum size: 87
>Compacted row maximum size: 5839588
>Compacted row mean size: 552698
>
>
>
>
> -
ntext:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Timeout-during-stress-test-tp6262430p6263087.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
I am running stress test using hector. In the client logs I see:
me.prettyprint.hector.api.exceptions.HTimedOutException: TimedOutException()
at
me.prettyprint.cassandra.service.ExceptionsTranslatorImpl.translate(ExceptionsTranslatorImpl.java:32)
at
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/What-need-to-be-monitored-while-running-stress-test-tp6255765p6257932.html
> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
> Nabble.com.
concurrent_readers and concurrent_writers see the comments in
cong/cassandra.yaml.
I could not find this KS definition in the hector code base so not sure why
they chose those values.
Aaron
On 9 Apr 2011, at 11:10, mcasandra wrote:
> I am starting a stress test using hector on 6 node machine 4GB h
What is a storage proxy latency?
By query latency you mean the one in cfstats and cfhistorgrams?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/What-need-to-be-monitored-while-running-stress-test-tp6255765p6257932.html
Sent from the cassandra-u
The storage proxy latencies are the primary metric: in particular, the
latency histograms show the distribution of query times.
On Fri, Apr 8, 2011 at 5:27 PM, mcasandra wrote:
> What are the key things to monitor while running a stress test? There is
> tons
> of details in nodetol
What are the key things to monitor while running a stress test? There is tons
of details in nodetoll tpstats/netstats/cfstats. What in particular should I
be looking at?
Also, I've been looking at iostat and await really goes high but cfstats
shows low latency in microsecs. Is latency in cf
I am starting a stress test using hector on 6 node machine 4GB heap and 12
core. In hectore readme this is what I got by default:
create keyspace StressKeyspace
with replication_factor = 3
and placement_strategy = 'org.apache.cassandra.locator.SimpleStrategy';
use StressKeys
On Fri, Feb 4, 2011 at 5:23 PM, Sameer Farooqui wrote:
> Brandon,
>
> Thanks for the response. I have also noticed that stress.py's progress
> interval gets thrown off in low memory situations.
>
> What did you mean by "contrib/stress on 0.7 instead". I don't see that dir
> in the src version of
Brandon,
Thanks for the response. I have also noticed that stress.py's progress
interval gets thrown off in low memory situations.
What did you mean by "contrib/stress on 0.7 instead". I don't see that dir
in the src version of 0.7.
- Sameer
On Thu, Feb 3, 2011 at 5:22 PM, Brandon Williams w
On Thu, Feb 3, 2011 at 7:02 PM, Sameer Farooqui wrote:
> Hi guys,
>
> I was playing around with the stress.py test this week and noticed a few
> things.
>
> 1) Progress-interval does not always work correctly. I set it to 5 in the
> example below, but am instead getting varying intervals:
>
Gener
Hi guys,
I was playing around with the stress.py test this week and noticed a few
things.
1) Progress-interval does not always work correctly. I set it to 5 in the
example below, but am instead getting varying intervals:
*techlabs@cassandraN1:~/apache-cassandra-0.7.0-src/contrib/py_stress$ pytho
I returned to periodic commit log fsync.
Jonathan Shook gmail.com> writes:
>
> Would you share with us the changes you made, or problems you found?
>
Would you share with us the changes you made, or problems you found?
On Wed, Jan 26, 2011 at 10:41 AM, Oleg Proudnikov wrote:
> Hi All,
>
> I was able to run contrib/stress at a very impressive throughput. Single
> threaded client was able to pump 2,000 inserts per second with 0.4 ms latency.
> M
Hi All,
I was able to run contrib/stress at a very impressive throughput. Single
threaded client was able to pump 2,000 inserts per second with 0.4 ms latency.
Multithreaded client was able to pump 7,000 inserts per second with 7ms latency.
Thank you very much for your help!
Oleg
Look at iostat -x 10 10 when he active par tof your test is running. there
should be something called svc_t - that should be in the 10ms range, and
await should be low.
Will tell you if IO is slow, or if IO is not being issued.
Also, ensure that you ain't swapping with something like "swapon -s"
buddhasystem bnl.gov> writes:
>
>
> Oleg,
>
> I'm a novice at this, but for what it's worth I can't imagine you can have a
> _sustained_ 1kHz insertion rate on a single machine which also does some
> reads. If I'm wrong, I'll be glad to learn that I was. It just doesn't seem
> to square with a
Brandon Williams gmail.com> writes:
>
> On Tue, Jan 25, 2011 at 1:23 PM, Oleg Proudnikov cloudorange.com>
wrote:
>
> When I run contrib/stress with a higher thread count, the server does scale to
> 200 inserts a second with latency of 200ms. At the same time Windows desktop
> scales to 900 ins
On Tue, Jan 25, 2011 at 1:23 PM, Oleg Proudnikov wrote:
> When I run contrib/stress with a higher thread count, the server does scale
> to
> 200 inserts a second with latency of 200ms. At the same time Windows
> desktop
> scales to 900 inserts a second and latency of 120ms. There is a huge
> diffe
k time on a hard drive.
Maxim
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Stress-test-inconsistencies-tp5957467p5960182.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
Tyler Hobbs riptano.com> writes:
> Try using something higher than -t 1, like -t 100.- Tyler
>
Thank you, Tyler!
When I run contrib/stress with a higher thread count, the server does scale to
200 inserts a second with latency of 200ms. At the same time Windows desktop
scales to 900 inserts a s
Try using something higher than -t 1, like -t 100.
- Tyler
On Mon, Jan 24, 2011 at 9:38 PM, Oleg Proudnikov wrote:
> Hi All,
>
> I am struggling to make sense of a simple stress test I ran against the
> latest
> Cassandra 0.7. My server performs very poorly compared to a deskt
Hi All,
I am struggling to make sense of a simple stress test I ran against the latest
Cassandra 0.7. My server performs very poorly compared to a desktop and even a
notebook.
Here is the command I execute - a single threaded insert that runs on the same
host as Cassnadra does (I am using new
Thanks Jonathan
--- On Thu, 7/1/10, Jonathan Ellis wrote:
From: Jonathan Ellis
Subject: Re: Cassandra 0.6.2 stress test failing due to setKeyspace issue
To: user@cassandra.apache.org
Date: Thursday, July 1, 2010, 3:32 PM
you're running a 0.7 stress.py against a 0.6 cassandra, that's
you're running a 0.7 stress.py against a 0.6 cassandra, that's not going to
work
On Thu, Jul 1, 2010 at 12:16 PM, maneela a wrote:
> Can someone direct me how to resolve this issue in cassandra 0.6.2 version?
>
> ./stress.py -o insert -n 1 -y regular -d
> ec2-174-129-65-118.compute-1.amazona
Can someone direct me how to resolve this issue in cassandra 0.6.2 version?
./stress.py -o insert -n 1 -y regular -d
ec2-174-129-65-118.compute-1.amazonaws.com --threads 5 --keep-going
Created keyspaces. Sleeping 1s for propagation.Traceback (most recent call
last): File "./stress.py", line
74 matches
Mail list logo
