[
https://issues.apache.org/jira/browse/HADOOP-17859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18040737#comment-18040737
]
ASF GitHub Bot commented on HADOOP-17859:
-----------------------------------------
github-actions[bot] commented on PR #3323:
URL: https://github.com/apache/hadoop/pull/3323#issuecomment-3578184476
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> DNS Query on DNS Registry got connection timed out at times.
> ------------------------------------------------------------
>
> Key: HADOOP-17859
> URL: https://issues.apache.org/jira/browse/HADOOP-17859
> Project: Hadoop Common
> Issue Type: Bug
> Components: registry
> Reporter: Jeongin Ju
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.1.2
>
> Attachments: HADOOP-17859.001.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> DNS query on YARN Registry DNS got connection timed out at times.
>
> After checking logs on registry dns, we found the cause that size of UDP
> Response is greater than Preallocated Byte buffer(4096)
>
> We added failsafe case by returning input query with TC flag so that client
> can know they should retried using TCP protocol.
>
>
> We found the problem and patched our cluster on 3.1.2 but it seems trunk
> still has the same problem.
> I attached patch based on the trunk.
>
> Thanks!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
