Neo4j takes 40 minutes to become available

Neo4j takes 40 minutes to become available

Can this be tuned in some way?

Regards
Alexander

@aschou

Thats clearly not typical and not something most users encounter.

a. What Neo4j version?

b. How is Neo installed? tar, rpm, debian, kubernetes, ?

c. can you provide the logs\debug.log which might describe where the 40 minutes is spent

a. What Neo4j version?

4.4.25

b. How is Neo installed? tar, rpm, debian, kubernetes, ?

linux rpm install started with neo4j binary
sudo -u neo4j neo4j start

c. can you provide the logs\debug.log which might describe where the 40 minutes is spent
i dont have the logs since its like 3 weeks ago last restart, but it seems to be scanning the indexes.

Also, even though the logs rotation is working, im getting 0kb in logfile.

-rwxr-xr-x 1 neo4j neo4j 0 Jul 18 03:49 neo4j.log

@aschou

is there no logs/debug.log?

Regarding a 0 byte neo4j.log please see Neo4j system service - Operations Manual

So, to clearify a bit.

The service comes up at once, but the bolt lietsning port does not become available after these index scans that takes around 40 minutes, is there a way to speed this up?

Alex

@aschou

is there no logs/debug.log?

Again this is not typical. How are you stopping Neo4j?

Can you attach the logs\debug.log