[jira] [Updated] (HDDS-7825) Difficult to debug why a node is excluded

["Michael Smith (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-7825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Smith updated HDDS-7825:
--------------------------------
    Summary: Difficult to debug why a node is excluded  (was: Impossible to debug why a node is excluded)

> Difficult to debug why a node is excluded
> -----------------------------------------
>
>                 Key: HDDS-7825
>                 URL: https://issues.apache.org/jira/browse/HDDS-7825
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: EC Client
>    Affects Versions: 1.3.0
>            Reporter: Michael Smith
>            Priority: Major
>
> When the client adds a node to the ExcludedNodes list due to an exception, the exception is hidden. I've found no logging to help determine why a node is added to the ExcludedNodes list, which makes it nearly impossible to determine if some configuration needs to be changed.
> In my case it turned out I was running into port exhaustion because lots of sockets were being opened/closed quickly, leaving many in TIME_WAIT, and I was on an older kernel with tcp_tw_reuse=0. One thing that helped determine that was the cause was doing a custom build of Ozone where I added logging when a node is excluded to see what exception caused it. Turns out that exception wasn't related to the target node.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org