[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesos-issues
Subject:    [jira] [Created] (MESOS-8513) Noisy "transport endpoint is not connected" logs on closing sockets.
From:       "Till Toenshoff (JIRA)" <jira () apache ! org>
Date:       2018-01-31 0:52:00
Message-ID: JIRA.13134945.1517359870000.81015.1517359920123 () Atlassian ! JIRA
[Download RAW message or body]

Till Toenshoff created MESOS-8513:
-------------------------------------

             Summary: Noisy "transport endpoint is not connected" logs on closing \
sockets.  Key: MESOS-8513
                 URL: https://issues.apache.org/jira/browse/MESOS-8513
             Project: Mesos
          Issue Type: Bug
    Affects Versions: 1.4.1, 1.5.0, 1.6.0
            Reporter: Till Toenshoff
            Assignee: Till Toenshoff


When within libprocess a socket is closing, we try to shut it down. That shutdown \
fails as the socket is not connected. This is intended behavior. The error code \
returned {{ENOTCONN}} tells us that there is nothing to see here for such common \
scenario.

The problem appears to be the logging of such event - that might appear as not useful \
- no matter which log-level is used.

{noformat}
E1214 08:15:18.017247 20752 process.cpp:2401] Failed to shutdown socket with fd 288: \
Transport endpoint is not connected {noformat}

We should try to prevent this specific, non actionable logging entirely while making \
sure we do not hinder debugging scenarios.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[prev in list] [next in list] [prev in thread] [next in thread]