it looks as if the shutdown timeout is just too short. Especially if there
are still hanging tx Neo4j takes more than 20s to stop and aI read that the
default timeout is 30s. I also saw that there is some registry setting for
the timeout that is applied by sc.
Not sure how to address that, see:
ht
Absolutely agree.
I will gladly cooperate on any investigation or shake-down of any solution
we might develop. My suspicion is that 'sc' just asks the service to stop
at an outer "black box level" where the service itself may not get an
'inner signal' of the request to stop. If this is the cas
I think we should rather find and fix the root cause why stopping the
service via sc does make an unclean shutdown.
Michael
On Sun, Jun 1, 2014 at 11:01 PM, Jim Salmons
wrote:
> Thanks for the pointer to that technique, Chris. None of my databases ATM
> are so critical that it is a show-stoppe
Thanks for the pointer to that technique, Chris. None of my databases ATM
are so critical that it is a show-stopper for me, but I figure it is good
to surface the issue in the event that others with critical needs get
bitten.
Now that I've looked at the situation a bit, too, it appears that a
You can, after you've shut down the Neo4j Windows service, use neo4j-shell with
the `-path ` option to start a non-service Neo4j instance and then do a
clean shutdown with the `exit` command. You should then be able to upgrade.
I don't know why there is this problem with shutting down the Window
This issue has surfaced a number of times in various flavors, particularly
when an explicit upgrade (non-automatic requiring
"allow_store_upgrade=true") is involved and the culprit seems to be this:
- If you run Neo4j as a Windows Service (having installed via
Neo4jInstaller.bat and using
