]
> *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 issue. At least we observed agent
> constantly died with OOM. Unfortunately, we
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 sim
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
Thanks, I think it got resolved after an update.
Kind regards,
Mikhail
On Wed, Jul 15, 2015 at 2:04 PM, Sebastian Estevez <
sebastian.este...@datastax.com> wrote:
> OpsCenter 5.2 has a couple of fixes that may result in the symptoms you
> described:
> http://docs.datas
> tax.com/en/opscenter/5.2
OpsCenter 5.2 has a couple of fixes that may result in the symptoms you
described:
http://docs.datas
tax.com/en/opscenter/5.2/opsc/release_notes/opscReleaseNotes520.html
- Fixed issues with agent OOM when storing metrics for large numbers of
tables. (OPSC-5934
- Improved handling of me
Looks like it dies with OOM:
https://gist.github.com/kluyg/03785041e16333015c2c
On Tue, Jul 14, 2015 at 12:01 PM, Mikhail Strebkov
wrote:
> OpsCenter 5.1.3 and datastax-agent-5.1.3-standalone.jar
>
> On Tue, Jul 14, 2015 at 12:00 PM, Sebastian Estevez <
> sebastian.este...@datastax.com> wrote:
>
OpsCenter 5.1.3 and datastax-agent-5.1.3-standalone.jar
On Tue, Jul 14, 2015 at 12:00 PM, Sebastian Estevez <
sebastian.este...@datastax.com> wrote:
> What version of the agents and what version of OpsCenter are you running?
>
> I recently saw something like this and upgrading to matching version
What version of the agents and what version of OpsCenter are you running?
I recently saw something like this and upgrading to matching versions fixed
the issue.
On Jul 14, 2015 2:58 PM, "Mikhail Strebkov" wrote:
> Hi everyone,
>
> Recently I've noticed that most of the nodes have OpsCenter agent
