[
https://issues.apache.org/jira/browse/DRILL-8077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461571#comment-17461571
]
ASF GitHub Bot commented on DRILL-8077:
---------------------------------------
vdiravka commented on pull request #2406:
URL: https://github.com/apache/drill/pull/2406#issuecomment-996887174
Agree with @jnturton and @vvysotskyi.
But possibly improvements still can be done for the algorithm of closing
connections by Drill to avoid:
> This leads to thousands of CLOSE_WAIT ipv6 connections from Drillbit to
Datanode
@Z0ltrix you can submit a separate ticket for that with details and error log
--
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)
