keith-turner opened a new issue, #5842:
URL: https://github.com/apache/accumulo/issues/5842
**Describe the bug**
When testing 4.0 72584da0c5e8c75c1c2c46583239b4eb059757a6 noticed the
monitor was at 100% CPU and staying there. Found it was a single thread using
the CPU and jstacked it and kept seeing the following.
```
"Metric Fetcher Thread" #50 daemon prio=5 os_prio=0 cpu=13456650.19ms
elapsed=15277.58s tid=0x000055fffc216e30 nid=0x16a70 runnable
[0x00007f77e73ed000]
java.lang.Thread.State: RUNNABLE
at
org.apache.accumulo.monitor.next.InformationFetcher.run(InformationFetcher.java:273)
at
org.apache.accumulo.core.util.threads.Threads.lambda$createCriticalThread$0(Threads.java:76)
at
org.apache.accumulo.core.util.threads.Threads$$Lambda$633/0x00007f77f1630228.run(Unknown
Source)
at
org.apache.accumulo.core.trace.TraceWrappedRunnable.run(TraceWrappedRunnable.java:52)
at java.lang.Thread.run([email protected]/Thread.java:840)
```
**Expected behavior**
Lower CPU usage if possible.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
