Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAE9Du-05yWeOQX6HPFhKs5joN+2U=TsUB9KwJ0AomyokhEo+uw@mail.gmail.com>
References: 
 <CAE9Du-05yWeOQX6HPFhKs5joN+2U=TsUB9KwJ0AomyokhEo+uw@mail.gmail.com>
Date: Mon, 22 Aug 2011 09:32:04 -0700
Message-ID: 
 <CALF7aMShsbMywo1OWdb9-GKxtD-N6XWs0Pt_tny9J6+4+gkkCQ@mail.gmail.com>
Subject: Re: Using MSG_NOSIGNAL on socket sends in libzookeeper_mt
From: Mahadev Konar <mahadev@hortonworks.com>
To: user@zookeeper.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Looks like we had similar issues in our tests and we ignored them in
the test cases:

https://issues.apache.org/jira/browse/ZOOKEEPER-482

Is this the tracking jira for SIGPIPE issue?

https://issues.apache.org/jira/browse/ZOOKEEPER-1051

thanks
mahadev

On Mon, Aug 22, 2011 at 7:44 AM, Stephen Tyree <tyree731@gmail.com> wrote:
> Right now when send is called after the cluster has closed the connection
> (say on session expiration) SIGPIPE is fired for the entire application.
> This seems like something we shouldn't be leaking out of the API, so a
> simple fix (at least for Linux) would be to add the MSG_NOSIGNAL option to
> any socket sends we do. This isn't portable to other platforms, but on other
> platforms there are similar solutions to the problem. What does everyone
> think?
>