[
https://issues.apache.org/jira/browse/TINKERPOP-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17086530#comment-17086530
]
ohad israeli commented on TINKERPOP-2359:
-----------------------------------------
I am using the gremlin javascript library and i havent been able to spot how to
send via it the graph.close - do you have any idea how can i extend it to
handle the graph close ?
I did look at g.io() but it doesnt answer my needs.
Regarding the docker, it seems that i am able to catch the termination signals
if i am starting directly with the shell scripts but within docker the process
is being killed prior of gracefully shutdown, i did try various actions to try
and make it fail gracefully but without any luck at the moment while working
within docker. ( i do have other sample code which does fails gracefully within
docker but i cant make the gremlin server to behave the same )
> onShutDown not being called when docker container stopped
> ---------------------------------------------------------
>
> Key: TINKERPOP-2359
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2359
> Project: TinkerPop
> Issue Type: Bug
> Components: server
> Affects Versions: 3.4.6
> Reporter: ohad israeli
> Priority: Minor
>
> When one uses groovy hooks with tinkerpop server hosted within the official
> docker the onStartUp hook will be called at server startup but the onShutDown
> will not be called.
> I am using tinkergraph server for local testing and i would like to persist
> the data upon the server exit. i've added a graph.close to the onShutDown
> hook but i havent been able to get it called.
> It will be called of course if you use the server start / server stop shell
> script but not if you kill / stop the docker container.
> If there is some other way to persist the date i.e. call the graph.close from
> code and note via the console it would also be great as using it from node
> javascript i havent been able to find a way to call the graph.close directly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
