[
https://issues.apache.org/jira/browse/KUDU-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16399831#comment-16399831
]
Todd Lipcon commented on KUDU-2350:
-----------------------------------
Based on some openssl list threads I found, it's a bit of a mess to use
MSG_NOSIGNAL. Since all of our sockets would be from our reactor threads, I
think it's probably easiest to just slap a pthread_sigmask() call in there to
block SIGPIPE when we start the thread.
> Kudu C++ client application might fail with SIGPIPE if TLS connection aborted
> from the tablet server side
> ---------------------------------------------------------------------------------------------------------
>
> Key: KUDU-2350
> URL: https://issues.apache.org/jira/browse/KUDU-2350
> Project: Kudu
> Issue Type: Bug
> Reporter: Alexey Serbin
> Priority: Major
>
> [~tlipcon] noticed that {{kudu perf loadgen}} failed with SIGPIPE if the
> TLS-protected connection terminates abruptly at the server-side.
> Most likely, we miss MSG_NOSIGNAL socket option for TLS sockets. Setting
> MSG_NOSIGNAL for client sockets (if possible) or calling
> {{pthread_sigmask()}} to ignore SIGPIPE could help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
