Paul,

That is pretty high memory usage for a locator. Jens idea to get a
histogram or heap dump is a real good one. That'll help determine if there
is a memory leak.

Thanks,

Barry Oglesby
GemFire Advanced Customer Engineering (ACE)
For immediate support please contact Pivotal Support at
http://support.pivotal.io/


On Wed, Dec 2, 2015 at 10:13 AM, Catanzarite, P. (Paul) <
[email protected]> wrote:

> It will take me some time to get the thread dump but here is some
> additional info.
>
>
>
> Server info:
>
> VM with 2 CPUs and 4gb memory and only this one locator is running on this
> server
>
>
>
> => uptime
>
> 12:57:17 up 11 days,  3:10,  1 user,  load average: 0.34, 0.46, 0.46
>
>
>
> => top
>
> top - 12:57:46 up 11 days,  3:10,  1 user,  load average: 0.53, 0.50, 0.47
>
> Tasks: 147 total,   1 running, 146 sleeping,   0 stopped,   0 zombie
>
> Cpu(s): 11.2%us,  0.6%sy,  0.0%ni, 88.1%id,  0.0%wa,  0.0%hi,  0.0%si,
> 0.0%st
>
> Mem:   3916900k total,  3484956k used,   431944k free,   266008k buffers
>
> Swap:  8388604k total,    26100k used,  8362504k free,   350836k cached
>
>
>
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
>
> 4952 gemfire   20   0 3680m 2.3g 8192 S 105.7 61.8   3529:13 java
>
>
>
>
>
> Pulse shows locator heap using 1.9gb  (out of 2gb configured)
>
>
>
> Member Metrics
>
>
>
>   Category    |              Metric              | Value
>
> ------------- | -------------------------------- | ------
>
> member        | upTime                           | 962112
>
>               | cpuUsage                         | 60
>
>               | currentHeapSize                  | 1905
>
>               | maximumHeapSize                  | 2031
>
> jvm           | jvmThreads                       | 92
>
>               | fileDescriptorLimit              | 32768
>
>               | totalFileDescriptorOpen          | 120
>
>
>
>
>
>
>
>
>
> *From:* Barry Oglesby [mailto:[email protected]]
> *Sent:* Wednesday, December 02, 2015 12:56 PM
> *To:* [email protected]
> *Subject:* Re: Locator high cpu
>
>
>
> What is the memory usage of the locator? Do you have any JMX clients or
> Pulse running? Can you get a few thread dumps of the locator JVM? That
> should help determine what the threads are doing.
>
>
> Barry Oglesby
>
> GemFire Advanced Customer Engineering (ACE)
>
> For immediate support please contact Pivotal Support at
> http://support.pivotal.io/
>
>
>
>
>
> On Wed, Dec 2, 2015 at 9:51 AM, Catanzarite, P. (Paul) <
> [email protected]> wrote:
>
> We have a gemfire client/server cluster that we’ve noticed our locator is
> running a sustained 50 – 100% cpu utilization.  We stopped all work in this
> environment (test) and the cpu has remained the same.  We are running
> gemfire v8.1, java 1.7 on linux VM RHEL 6.  Any suggestions on what to look
> at to see what may be causing this?
>
> Thanks.
>
> -Paul
>
>
> ---------------------------------------------------------
>
> NOTICE: The information contained in this electronic mail message is
> confidential and intended only for certain recipients.  If you are not an
> intended recipient, you are hereby notified that any disclosure,
> reproduction, distribution or other use of this communication and any
> attachments is strictly prohibited.  If you have received this
> communication in error, please notify the sender by reply transmission and
> delete the message without copying or disclosing it.
>
>
> ============================================================================================
>
>
>

Reply via email to