Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Zookeeper >> mail # user >> Using MSG_NOSIGNAL on socket sends in libzookeeper_mt


Copy link to this message
-
Re: Using MSG_NOSIGNAL on socket sends in libzookeeper_mt
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 <[EMAIL PROTECTED]> 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?
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB