-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
restart neo4j in docker without killing container #77
Comments
If you're going to the trouble of making your own docker image to use supervisord I'd heavily recommend that you run neo4j directly instead of the entrypoint script. Then you wouldn't have to fight the setting code. So something like
|
using supervisord in a docker container is not the way to go: if you process dies, the container dies. Just restart the container. Docker provides the |
@spacecowboy I am in a situation where I want to restore a |
Yes I have the trouble too! I want to import some csv data to graph.db ,but always display error. /var/lib/neo4j # neo4j-admin import --nodes=import/movies.csv --database graph.db Available resources: IMPORT FAILED in 18047d 12h 53m 50s 261ms. WARNING Import failed. The store files in /data/databases/graph.db are left as they are, although they are likely in an unusable state. Starting a database on these store files will likely fail or observe inconsistent records so start at your own risk or delete the store manually |
Same issue here, using it in Kubernetes. For now I use a workaround:
To solve the use-case of imports I'm now working on using a Kubernetes initContainer to seed the database using a previously registered dump. |
@nicorikken I have the same problem, but a different solution in Kubernetes. I used a Job and created a modified image from the Neo4j image. I mounted a Persistent Volume to this container on |
@Rohithzr This would count as an administrative procedure and needs to be done by set of cli parameters where you can import your new graph from the other directory without restarting the main process. The proper solution wouldn't be to make this kind of workaround to keep the container always running, would be to add the proper functionality in neo4j for import from a directory / NFS Having said that you could override the entrypoint to start neo4j &; and to tail -f somke log file |
I've rolled my own Dockerfile to start with neo4j and include supervisord to run the docker-entrypoint script. It would be nice if I didn't have to do this and use my own image, but rather if Neo4j was setup this way from the get-go, or at least in some way that the container wouldn't die when trying to add additional conf entries aside from the few items that can be passed in as environment variables. If it helps, did the following:
Dockerfile:
The text was updated successfully, but these errors were encountered: