You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2021/12/13 16:21:21 UTC

[GitHub] [arrow] lupko edited a comment on issue #11932: [Python] Unable to turn-off signal blocking for pyarrow flight RPC server

lupko edited a comment on issue #11932:
URL: https://github.com/apache/arrow/issues/11932#issuecomment-992635862


   @lidavidm for me, the goal is to integrate Flight RPC server into a larger app, and manage the lifecycle of the server from there. 
   
   e.g. when my app receives signal to stop, it handles the teardown and as part of it shuts down the Flight RPC server. That's why for me the approach of no signal handling done by PyArrow is preferred. 
   edit: in my case, the existing shutdown() functionality is fine. wait until existing clients finish.
   
   btw, is there any difference between shutdown done as part of PyArrow signal handling and the shutdown() that I can trigger myself?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org