[
https://issues.apache.org/jira/browse/DRILL-8077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461326#comment-17461326
]
ASF GitHub Bot commented on DRILL-8077:
---------------------------------------
Z0ltrix commented on pull request #2406:
URL: https://github.com/apache/drill/pull/2406#issuecomment-996602728
> Hi @vvysotskyi, @Z0ltrix. The two considerations,
>
> 1. this change is a workaround for buggy IPv6 support in HDFS and
>
> 2. the workaround is untargeted and could have side effects in some
environments because Drill's JVMs get set to prefer IPv4 for every socket they
open, whether to HDFS or elsewhere
>
>
> , make me wonder if this should really be promoted to a Drill default. An
alternative might be that we create a doc page describing this problem and
showing users how to apply the workaround uncovered by @Z0ltrix to their own
environments...
Hi @jnturton,
good Point...
What now? How i should continue?
This PR or Docs?
Regards
Christian
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> Thousand of CLOSE_WAIT connections to HDFS Datanode
> ----------------------------------------------------
>
> Key: DRILL-8077
> URL: https://issues.apache.org/jira/browse/DRILL-8077
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Other
> Affects Versions: 1.16.0
> Reporter: Christian Pfarr
> Priority: Major
>
> In IPv6 environments after a while drill has a lot of connections to HDFS
> Datanode in CLOSE_WAIT state.
> To fix this we add '-Djava.net.preferIPv4Stack=true
> -Djava.net.preferIPv6Addresses=false' to our drill configuration and the
> problem vanished.
> we saw
> [https://community.cloudera.com/t5/Support-Questions/Over-40000-CLOSE-WAIT-after-hbase-cluster-restart/m-p/6403/highlight/true#M51847]
> from cloudera that helped.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
