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 versions > fixed the issue. > On Jul 14, 2015 2:58 PM, "Mikhail Strebkov" <streb...@gmail.com> wrote: > >> Hi everyone, >> >> Recently I've noticed that most of the nodes have OpsCenter agents >> running at 300% CPU. Each node has 4 cores, so agents are using 75% of >> total available CPU. >> >> We're running 5 nodes with OpenSource Cassandra 2.1.8 in AWS using >> Community AMI. OpsCenter version is 5.1.3. We're using Oracle Java version >> 1.8.0_45. >> >> * PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND* >> 31501 cassandr 20 0 3599m 296m 14m S *339* 2.0 48:20.39 >> /opt/jdk/jdk1.8.0_45/bin/java -Xmx128M -Djclouds.mpu.parts.magnitude=100000 >> -Djclouds.mpu.parts.size=16777216 >> -Dopscenter.ssl.trustStore=/var/lib/datastax-agent/ssl/agentKeyStore >> -Dopscenter.ssl.keyStore=/var/lib/datastax-agent/ssl/agentKeyStore >> -Dopscenter.ssl.keyStorePassword=opscenter >> -Dagent-pidfile=/var/run/datastax-agent/datastax-agent.pid >> -Dlog4j.configuration=file:/etc/datastax-agent/log4j.properties >> -Djava.security.auth.login.config=/etc/datastax-agent/kerberos.config -jar >> datastax-agent-5.1.3-standalone.jar >> /var/lib/datastax-agent/conf/address.yaml >> >> The logs from the agent looks strange to me: >> https://gist.github.com/kluyg/21f78af7adff0a940ed3 >> >> The cluster itself seems to be fine, the load is small, nothing bad in >> Cassandra system.log. >> >> Does anyone know what to tune to bring it back to normal? >> >> Thanks, >> Mikhail >> >
