cancel
Showing results for 
Search instead for 
Did you mean: 

Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.

Fatal error occurred when handling a client connection, remote peer unexpectedly closed connection:

Hi,

I am facing issue that my 6 (3 cores, 3 replica) neo4j servers are getting down one by one (checked with CALL dbms.cluster.overview()). Then I restart all servers and neo4j service back online. this happened randomly daily.
I check debug.log and found following errors:

  1. Fatal error occurred when initializing pipeline
  2. Fatal error occurred when handling a client connection, remote peer unexpectedly closed connection.
  3. Detected VM stop-the-world pause

All six servers are AWS t2.2xlarge linux servers with 8 core CPU and 32 GB RAM.
Neo4j configurations are as follow:

dbms.memory.heap.initial_size=16g
dbms.memory.heap.max_size=16g
dbms.memory.pagecache.size=20g

Then on all servers I have also changed the open files limit from 1024 to 40,000 by updating the limits.conf.

Please help me out to figure out the issue and whats the best solution. Thanks

0 REPLIES 0