keith-turner opened a new issue, #5712: URL: https://github.com/apache/accumulo/issues/5712
**Describe the bug** When running the test described in #5707 w/o the fix in #5707 after the test got stuck observed that the zookeeper server was consistently using 100% CPU for long periods of time. Not sure if it was doing this before the test got stuck. This needs to further investigation to see if Accumulo is accessing zookeeper too aggressively under certain situations. **To Reproduce** Could try running the bulk random walk test using external compaction w/o the fix in #5707 and monitor zookeeper CPU usage. The high CPU utilization was observed after the user compaction was stuck, not sure what the CPU utilization looked like before that. Would be good to look at the utilization in general when running some random walk and continuous ingest test. **Expected behavior** A single node cluster w/ light activity from a random walk test should probably not be pushing zookeeper to 100% cpu utilization. If the activity is reasonable, then it would be good to understand it. Suspect something in the manager is reading zookeeper too aggressively. -- 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: notifications-unsubscr...@accumulo.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
