Hi All,
We have a cluster (2.1.2) of 3 nodes , There is one table which contains
huge amount of data and having sstable count more than 1800 on all 3 nodes.
We have noticed that suddently compaction for that CF occurs very
frequently right after completion of previous compaction and also taking
l
Hi,
2.1.x does have compaction issues. Upgrading to 2.1.6 should help you. You
can also search this mailing list for some recommendations for that
specific problem since it is a recurrent issue.
Regards,
Carlos Juzarte Rolo
Cassandra Consultant
Pythian - Love your data
rolo@pythian | Twitter:
Hi,
I'm looking for information on how to correctly deploy an OpsCenter
instance behind a HTTP(S) proxy.
I have a running instance of OpsCenter 5.1 reachable at
http://opscenter:/opscenter/ but I would like to be able to
serve this kind of tool under a single hostname on HTTPS along with
ot
First, your firewall should really be your frontend There operational
frontend is apache, which is common. You want every url with opscenter in
it handled elsewhere. You could also set up proxies for /.
cluster-configs, etc...
Then there is mod_rewrite, which provides a lot more granularity abo
Can anyone guide me with any pointers plz
On 17 June 2015 at 17:05, Jayapandian Ponraj wrote:
> Hi
>
> I have a cassandra cluster of 6 nodes, with DateTiered compaction for
> the tables/CFs
> For some reason the minor compaction never happens.
> I have enabled debug logging and I don't see any de
Hi,
>From what I read there are some issue using DTCS. You should probably go to
the last minor version.
You should also give more context so people can help. Have you tried a
simple restart ? Does it happen on all your nodes ?
C*heers,
Alain
2015-06-18 11:42 GMT+02:00 Jayapandian Ponraj :
>
Hi,
Curently the cluster runs 2.0.14 on all nodes, will try to upgrade to 2.0.15
The issue is in all the nodes..
simple restart as in a rolling restart of all the nodes?
On 18 June 2015 at 15:18, Alain RODRIGUEZ wrote:
> Hi,
>
> From what I read there are some issue using DTCS. You should prob
Hi guys.
I'm facing slow read requests from time to time, I've spotted the
keyspace/cf where this is happening but I can't see anything obvious
(single partition slice query, no tombstones, ...) anything else where to
look at?
I'd like to have the slow queries logged to either log or saved to a
p
Hi Carlos,
Different possibilities (to log slow queries).
1) A probabilistic way to catch slow queries (probabilistic, but with
detailed info) => look for “nodetool settraceprobability” like in
http://www.datastax.com/dev/blog/advanced-request-tracing-in-cassandra-1-2
2) Catch slow
Thanks Dominique for your fast and useful reply.
I think I'll try No 2, catch slow queries in the driver, but unfortunately
we don't use Java but Ruby and it doesn't seem to have that feature.
Anyone using Ruby has worked out a solution? I'm thinking of adding the
feature to the driver otherwise
Hi,
I want to make on a regular base repairs on my cluster as suggested by the
documentation.
I want to do this in a way that the cluster is still responding to read
requests.
So I understand that I should not use the -par switch for that as it will do
the repair in parallel and consume all ava
If you're using DSE, you can schedule it automatically using the repair
service. If you're open source, check out Spotify cassandra reaper, it'll
manage it for you.
https://github.com/spotify/cassandra-reaper
On Thu, Jun 18, 2015 at 12:36 PM Jean Tremblay <
jean.tremb...@zen-innovations.com> w
OpsCenter is a little bit tricky to simply just rewrite urls, the lhr
requests and rest endpoints it hits are all specified a little differently
in the javascript app it loads.
We ended up monkey patching a buttload of the js files to get all the
requests working properly with our proxy. Everytime
In your examples, there are front pages then there are links to more info
on different things.
Do you want me to just write a front page or to provide content for the
different links?
On Thu, Jun 18, 2015 at 5:13 AM, Jonathan Ballet
wrote:
> Hi,
>
> I'm looking for information on how to correct
I'm using sstableloader to bulk-load a table from one cluster to another. I
can't just copy sstables because the clusters have different topologies.
While we're looking to upgrade soon to Cassandra 2.0.x, we're on Cassandra
1.2.19. The source data comes from a "nodetool snapshot."
Here's the comma
Thanks Jonathan.
But I need to know the following:
If you issue a “nodetool repair” on one node will it repair all the nodes in
the cluster or only the one on which we issue the command?
If it repairs only one node, do I have to wait that the nodetool repair ends,
and only then issue another “
Hi Jean,
Running nodetool repair on a node will repair only that node in the
cluster. It is recommended to run nodetool repair on one node at a time.
Few things to keep in mind while running repair
1. Running repair will trigger compactions
2. Increase in CPU utilization.
Run node tool re
Hi
Is their any way to schedule a job in cassandra to delete the recrods which
are older than a specific time period.
Excluding the option of TTL.
Regards
Anil
Sent from Samsung Mobile
Perfect thank you.
So making a weekly "nodetool repair -pr” on all nodes one after the other will
repair my cluster. That is great.
If it does a compaction, does it mean that it would also clean up my tombstone
from my LeveledCompactionStrategy tables at the same time?
Thanks for your help.
O
19 matches
Mail list logo
