{"action":"created","issue":{"url":"https://api.github.com/repos/neo4j/neo4j/issues/6447","repository_url":"https://api.github.com/repos/neo4j/neo4j","labels_url":"https://api.github.com/repos/neo4j/neo4j/issues/6447/labels{/name}","comments_url":"https://api.github.com/repos/neo4j/neo4j/issues/6447/comments","events_url":"https://api.github.com/repos/neo4j/neo4j/issues/6447/events","html_url":"https://github.com/neo4j/neo4j/issues/6447","id":134056472,"number":6447,"title":"3.0.0 write.lock file not being removed after neo4j stops","user":{"login":"tasmar","id":5840586,"avatar_url":"https://avatars.githubusercontent.com/u/5840586?v=3","gravatar_id":"","url":"https://api.github.com/users/tasmar","html_url":"https://github.com/tasmar","followers_url":"https://api.github.com/users/tasmar/followers","following_url":"https://api.github.com/users/tasmar/following{/other_user}","gists_url":"https://api.github.com/users/tasmar/gists{/gist_id}","starred_url":"https://api.github.com/users/tasmar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tasmar/subscriptions","organizations_url":"https://api.github.com/users/tasmar/orgs","repos_url":"https://api.github.com/users/tasmar/repos","events_url":"https://api.github.com/users/tasmar/events{/privacy}","received_events_url":"https://api.github.com/users/tasmar/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/neo4j/neo4j/labels/3.0","name":"3.0","color":"006b75"},{"url":"https://api.github.com/repos/neo4j/neo4j/labels/bug","name":"bug","color":"fc2929"},{"url":"https://api.github.com/repos/neo4j/neo4j/labels/kernel","name":"kernel","color":"0052cc"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-02-16T18:17:55Z","updated_at":"2016-02-18T16:26:19Z","closed_at":"2016-02-18T16:26:19Z","body":"I have been testing out the 3.0.0-M03 docker image and noticed that when I mount /data to a volume on my host, then stop the container, write.lock is not removed, along with other files not being touched/cleaned up, which is preventing me from running a batch script to populate some data.\r\n\r\nTo recreate the issue I went through these steps.\r\n1. Pull the image `docker pull neo4j/neo4j:3.0.0-M03`\r\n2. Create a directory on the host that will be a mount for the data `mkdir /home/neo4j-data`\r\n3. Start a new container the mounts to this directory `docker run -d --name neo4j-test -p 7474:7474 -v /home/neo4j:/data neo4j/neo4j:3.0.0-M03`\r\n4. Navigate to the write.lock file `/data/databases/graph.db/schema/label/lucene/labelStore/1/write.lock`\r\n5. Stop the container `docker stop neo4j-test`\r\n6. The write.lock file should be gone now but it is not.  \r\n\r\nI tested this in neo4j:2.3.0 and the write.lock file does get removed after a docker stop, granted the directory locations are different from v2.3 to v3.0."},"comment":{"url":"https://api.github.com/repos/neo4j/neo4j/issues/comments/185801416","html_url":"https://github.com/neo4j/neo4j/issues/6447#issuecomment-185801416","issue_url":"https://api.github.com/repos/neo4j/neo4j/issues/6447","id":185801416,"user":{"login":"tasmar","id":5840586,"avatar_url":"https://avatars.githubusercontent.com/u/5840586?v=3","gravatar_id":"","url":"https://api.github.com/users/tasmar","html_url":"https://github.com/tasmar","followers_url":"https://api.github.com/users/tasmar/followers","following_url":"https://api.github.com/users/tasmar/following{/other_user}","gists_url":"https://api.github.com/users/tasmar/gists{/gist_id}","starred_url":"https://api.github.com/users/tasmar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tasmar/subscriptions","organizations_url":"https://api.github.com/users/tasmar/orgs","repos_url":"https://api.github.com/users/tasmar/repos","events_url":"https://api.github.com/users/tasmar/events{/privacy}","received_events_url":"https://api.github.com/users/tasmar/received_events","type":"User","site_admin":false},"created_at":"2016-02-18T16:26:19Z","updated_at":"2016-02-18T16:26:19Z","body":"We testing this and you are correct.  The write.lock file does not prevent us from running our batch script for 3.0.0-M03.  Thank you for all your help!"}}