You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Lynch Wu (Jira)" <ji...@apache.org> on 2021/03/05 00:59:00 UTC
[jira] [Created] (ARROW-11866) [C++] Arrow Flight
SetShutdownOnSignals cause potential mutex deadlock in gRPC
Lynch Wu created ARROW-11866:
--------------------------------
Summary: [C++] Arrow Flight SetShutdownOnSignals cause potential mutex deadlock in gRPC
Key: ARROW-11866
URL: https://issues.apache.org/jira/browse/ARROW-11866
Project: Apache Arrow
Issue Type: Bug
Components: FlightRPC
Affects Versions: 3.0.0
Environment: * Arrow 3.0
* gcc (Debian 10.2.0-16) 10.2.0
* grpc 1.33.1/C++
Reporter: Lynch Wu
Fix For: 4.0.0
1. When starting a Flight Server with shut down signal (SIGTERM) and using `Ctrl + C` to terminate the server cause potential mutex deadlock in gRPC.
* gcc (Debian 10.2.0-16) 10.2.0
* grpc 1.33.1/C++
2. [https://github.com/apache/arrow/blob/master/cpp/src/arrow/flight/test_server.cc] This test case can be used as minimal code to re-produce the issue with above gRPC version and gcc version on Debian 10.2.0.
3. Related gRPC issue is: [https://github.com/grpc/grpc/issues/24884]
4. I am wandering the way handling the signal is proper with gRPC here: [https://github.com/apache/arrow/blob/master/cpp/src/arrow/flight/server.cc#L881]
Feel free to share your thoughts for this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)