Hello!
I've noticed a strange CPU utilisation patterns on machines in our
cluster. After C* daemon restart it behaves in a normal way, after a
few weeks since a restart CPU usage starts to raise. Currently on one
of the nodes (screenshots attached) cpu load is ~4. Shortly before
restart load raise
just a guess, gc?
On Mon, Jul 20, 2015 at 3:15 PM, Marcin Pietraszek
wrote:
> Hello!
>
> I've noticed a strange CPU utilisation patterns on machines in our
> cluster. After C* daemon restart it behaves in a normal way, after a
> few weeks since a restart CPU usage starts to raise. Currently on o
Cassandra does some housekeeping before it starts accepting requests from
clients.
For instance, as you can see from the log file, it replays commit log.
When the node is ready to accept requests from clients it logs a message to the
log file similar to “Starting listening for CQL clients on
loc
Hi all,
Please, is that possible to change this command:
nodetool getendpoints MyKeyspace MyTable text
10.147.243.4
10.147.243.5
to
nodetool getendpoints MyKeyspace MyTable text="Hello" ?
is there a solution to get more details about mes rows ?
Thanks a lot.
Best Regards.
Hi,
So since, I upgraded to 2.2-rc2 I get the CASSANDRA-9643 warning :
WARN o.a.c.i.s.f.b.BigTableWriter - Compacting large partition bytes
Some of my partitions may have ~20 millions of rows, while others may have
only a few hundreds of rows. It may grow up to 300 millions of rows per
par
Hi all & Sebastain
We recently encountered similar issue. At least we observed agent
constantly died with OOM. Unfortunately, we are still with 1.2.X and it
will be a while before we can totally move to Cassandra 2 series.
Is there a backport patch to fix OOM in OpsCenter 5.1 branch? Please let u
Please, what is the difference between 1) and 2)
http://pastie.org/private/ydziir2376ru58ywrjq
Bests.
2015-07-20 12:55 GMT+01:00 Thouraya TH :
> Hi all,
>
> Please, is that possible to change this command:
>
> nodetool getendpoints MyKeyspace MyTable text
> 10.147.243.4
> 10.147.243.5
>
> to
>
May I please be discontinued from this email?
May I unsubscribe?
From: John Wong [mailto:gokoproj...@gmail.com]
Sent: Monday, July 20, 2015 8:37 AM
To: user@cassandra.apache.org
Subject: Re: OpsCenter datastax-agent 300% CPU
Hi all & Sebastain
We recently encountered similar issu
There is no difference.
In #2, I'm guessing you're confusing using some of the column names as
keys. You could also do getendpoints Mykeyspace Mytable 'foo' and
Mykeyspace Mytable 'bar'
getendpoints does not require any data in your column family to function;
it only requires a schema for the co
I recently became aware of a Java driver bug that might be causing similar
symptoms. Do you, perchance, have any keyspaces that have replication
defined against non-existent Data Centers?
https://datastax-oss.atlassian.net/browse/JAVA-702
If so, fixing that replication setting and restarting the
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.2.0.
You can read about the release here:
http://www.datastax.com/dev/blog/cassandra-2-2
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability wit
ok..
Can you please explain me what mean these ip address ? what contain these
machines ? Bests.
./nodetool getendpoints Mykeyspace Mytable 'gv8'
172.16.64.43
172.16.64.42
./nodetool getendpoints Mykeyspace Mytable 'gv4'
172.16.64.41
172.16.65.1
./nodetool getendpoints Mykeyspace Mytable 'gv1'
172
On Mon, Jul 20, 2015 at 6:32 AM, Pierre Devops
wrote:
> Some of my partitions may have ~20 millions of rows, while others may have
> only a few hundreds of rows. It may grow up to 300 millions of rows per
> partition in a near futur, leading to very huge partition (50~80 GB I
> think).
>
Rows th
On Sat, Jul 18, 2015 at 10:09 AM, J. Ryan Earl wrote:
> Even with https://issues.apache.org/jira/browse/CASSANDRA-7386 data
> balancing across JBOD setups is pretty horrible. Having used JBOD for
> about 2 years from 1.2.x and up, it is my opinion JBOD on Cassandra is
> nascent at best and far f
Chamila,
As you can see from the netstat/lsof output, there is nothing listening on
port 9042 because Cassandra has not started yet. This is the reason you are
unable to connect via cqlsh.
You need to work out first why Cassandra has not started.
With regards to JVM, Oded is referring to the max
Hi there,
I am running a 6 node cluster on 2.1.7 with a table using DTCS to store
time series data, for up to 12 hours (using ttl of 12h). Data are written
as they arrive, without any update or active delete.
During the first 12h, the cluster gets filled with data. And a bit later,
the amount of d
Data structures that have a recently-modified access pattern seem to be a poor
fit for Cassandra. I’m wondering if any of you smart guys can provide
suggestions.
For the sake of discussion, lets assume I have the following tables:
CREATE TABLE document (
docId UUID,
doc TEXT,
17 matches
Mail list logo
