Neo4j CPU utilization reaches 100%. why?
See original GitHub issueI have a Linux instance on which neo4j is deployed. It is working fine but from 2-3 days sometimes CPU utilization reaches 100% and the DB stop responding to any request.Even, I’m not able to open the DB in the browser. Then, I need to reboot the instance which is not good.
Below the logs which have found in debug.log
old [223790]: Check pointing completed
2018-01-04 17:12:38.329+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] Log Rotation [6]: Starting log pruning.
2018-01-04 17:12:38.329+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] Log Rotation [6]: Log pruning complete.
2018-01-04 17:14:20.225+0000 WARN [o.n.k.i.c.MonitorGc] GC Monitor: Application threads blocked for 389ms.
2018-01-04 17:14:33.212+0000 WARN [o.n.k.i.c.MonitorGc] GC Monitor: Application threads blocked for 267ms.
2018-01-04 17:16:32.934+0000 WARN [o.n.k.i.c.MonitorGc] GC Monitor: Application threads blocked for 237ms.
2018-01-04 17:16:34.253+0000 WARN [o.n.k.i.c.MonitorGc] GC Monitor: Application threads blocked for 317ms.
2018-01-04 17:17:16.896+0000 WARN [o.n.k.i.c.MonitorGc] GC Monitor: Application threads blocked for 291ms.
2018-01-04 17:17:20.761+0000 ERROR [o.n.b.v.t.BoltProtocolV1] Failed to write response to driver Cannot write to buffer when closed
java.io.IOException: Cannot write to buffer when closed
at org.neo4j.bolt.v1.transport.ChunkedOutput.ensure(ChunkedOutput.java:163)
at org.neo4j.bolt.v1.transport.ChunkedOutput.writeShort(ChunkedOutput.java:94)
at org.neo4j.bolt.v1.packstream.PackStream$Packer.packStructHeader(PackStream.java:427)
at org.neo4j.bolt.v1.messaging.BoltResponseMessageWriter.onSuccess(BoltResponseMessageWriter.java:76)
at org.neo4j.bolt.v1.messaging.MessageProcessingHandler.onFinish(MessageProcessingHandler.java:111)
at org.neo4j.bolt.v1.runtime.BoltStateMachine.after(BoltStateMachine.java:102)
at org.neo4j.bolt.v1.runtime.BoltStateMachine.reset(BoltStateMachine.java:175)
at org.neo4j.bolt.v1.messaging.BoltMessageRouter.lambda$onReset$2(BoltMessageRouter.java:74)
at org.neo4j.bolt.v1.runtime.concurrent.RunnableBoltWorker.execute(RunnableBoltWorker.java:130)
at org.neo4j.bolt.v1.runtime.concurrent.RunnableBoltWorker.run(RunnableBoltWorker.java:91)
at java.lang.Thread.run(Thread.java:748)
I’m not getting why I’m getting this IOException Please help me to find the solution!
Issue Analytics
- State:
- Created 6 years ago
- Comments:29 (14 by maintainers)
Top Results From Across the Web
Neo4j High CPU Utilisation while seeding 20million dataset
Now the problem I'm facing is everything is working fine. But my Neo4j CPU utilization is around 388% across 4 cores when I'm...
Read more >Neo4J Write: CPU at 100% when there is a lot of write
I ran around 3k write queries in around 1 minutes, the CPU hits 100%. Here is the jstack log: jstack when CPU at...
Read more >100% cpu on one cpu while performaing cypher queries using ...
I am using py2neo package in the python script. In the beginning the queries are processed fine. I can see multiple cpus being...
Read more >Monitoring and Analysis of CPU Utilization, Disk Throughput ...
Figure 5:2 95% Confidence Interval for CPU Utilization for 100% Mixed Load. ... b) Later, to search the index entry, Cassandra hits the...
Read more >Neo4J Cypher Query- Cpu Usage Profiler - ADocLib
Neo4j Graph Platform The CPU usage stays between 25-40% consistently; I increased the minimum pool size hoping it would Another thing I am...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Anurag690 I’m no longer maintaining this driver. You are in good hands with @zhenlineo 😃
Hi @Anurag690, If you have a Neo4j cpu usage problem, you could start an issue on neo4j with necessary information for us to help you debug your problem.