Hi
- Hardware Specs
RAM: 14GB
Cores: 8
Disk: 440GB SSD
- I have deployed 7 instances ( Earlier, I mentioned 8 but I had to
decommission 1 due to low disk space ) on AWS.
- Every node is in the same datacenter.
.
- I have created a custom schema with 28 columns. Created a simple YAML
file for th
These are sample queries. I'll try to get real application queries using the
trace probability thing.
17 Nis 2017 ÖS 7:32 tarihinde benjamin roth yazdı:
Hm it is very unlikely that this kind of queries are really run on your
production system!
2017-04-17 17:49 GMT+02:00 Eren Yilmaz
mailto:ere
What are your hardware specs? Where are you running the cluster? Is every
node in the same physical datacenter? What command are you using to run stress?
> On Apr 17, 2017, at 9:57 AM, Akshay Suresh
> wrote:
>
> Hi
>
> I have not done much. Just created a schema with SimpleStrategy and a
Hi
I have not done much. Just created a schema with SimpleStrategy and a
replication factor of 3.
Then I created a yaml file
Now I am running the cassandra stress tool invoking the yaml file - with
10,000 records ( no warmup ) with 10 concurrent threads. I am just running
writes ( no reads )
Wh
Hm it is very unlikely that this kind of queries are really run on your
production system!
2017-04-17 17:49 GMT+02:00 Eren Yilmaz :
> I ran two queries, the first one is on the application table, the second
> one is on our counter table. I’m posting the results below (removed the
> values for con
It would help to know what kind queries are slow.
Hannu
> On 17 Apr 2017, at 18:42, Akshay Suresh wrote:
>
> Hi
>
> I have set up a cassandra cluster of 8 nodes.
>
> I am using Apache Cassandra 3.9
>
> While using cassandra-stress tool for load testing, I am getting really slow
> writes ( l
I ran two queries, the first one is on the application table, the second one is
on our counter table. I’m posting the results below (removed the values for
convenience). Coincidence or luck, both queries looked up to node-05 for
replica. Still does not make any sense to me.
cqlsh:Usergrid_Appl
Hi
I have set up a cassandra cluster of 8 nodes.
I am using Apache Cassandra 3.9
While using cassandra-stress tool for load testing, I am getting really
slow writes ( low upto few 10-20 writes per second ) along with frequent
timeouts and out of heap space errors.
Kindly let me know how do I re
You can set the trace probability on a node to 1% and you'll catch a trace
on that table.
http://cassandra.apache.org/doc/latest/tools/nodetool/settraceprobability.html
On Mon, Apr 17, 2017 at 11:17 AM, benjamin roth wrote:
> Just run some queries on counter tables. Some on regular tables. Look
Just run some queries on counter tables. Some on regular tables. Look at
traces and then compare. You don't need to do anything with application
code. You can also set trace probability on a table level and then analyze
the queries.
Am 17.04.2017 17:07 schrieb "Eren Yilmaz" :
> I can’t add tracin
I can’t add tracing using driver – Usergrid code is way too complex. When I
look at logging the slow queries on the C* side, it says the feature is added
in version 3.10 (https://issues.apache.org/jira/browse/CASSANDRA-12403), and we
use 3.7. Any other ways to log slow queries in this version? O
You could enable a slow query log and then trace single queries couldn't
you?
Am 17.04.2017 16:31 schrieb "Eren Yilmaz" :
I can’t trace selects on the application tables unfortunately. The
application is Usergrid, and it stores the data in binary. We have little
control over Usergrid-created data
I can’t trace selects on the application tables unfortunately. The application
is Usergrid, and it stores the data in binary. We have little control over
Usergrid-created data.
From: benjamin roth [mailto:brs...@gmail.com]
Sent: Monday, April 17, 2017 4:12 PM
To: user@cassandra.apache.org
Subjec
Hi all,
This is my existing table configured on apache-cassandra-3.0.9:
CREATE TABLE report_id1 (
mc_id text,
tag_id text,
e_date timestamp.
value text
PRIMARY KEY ((mc_id, tag_id), e_date)
}
I create table dynamically for each report from application. Need to
support upto 1000 re
Do you see difference when tracing the selects?
2017-04-17 13:36 GMT+02:00 Eren Yilmaz :
> Application tables use LeveledCompactionStrategy. At first, counter tables
> were created by default SizeTieredCompactionStrategy, but we changed them
> to LeveledCompactionStrategy then.
>
>
>
> compaction
Application tables use LeveledCompactionStrategy. At first, counter tables were
created by default SizeTieredCompactionStrategy, but we changed them to
LeveledCompactionStrategy then.
compaction = { 'class' :
'org.apache.cassandra.db.compaction.LeveledCompactionStrategy',
'sstable_size_in_mb'
Do you have a different compaction strategy on the counter tables?
2017-04-17 10:07 GMT+02:00 Eren Yilmaz :
> We are using Cassandra (3.7) counter tables in our application, and there
> are about 10 counter tables. The counter tables are in a separate keyspace
> with RF=3 (total 10 nodes). The ta
We are using Cassandra (3.7) counter tables in our application, and there are
about 10 counter tables. The counter tables are in a separate keyspace with
RF=3 (total 10 nodes). The tables are read-heavy, for each web request to the
application, we read at least 20 counter values. The counter rea
18 matches
Mail list logo
