Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate customizing netty resolver used by Azure SDK #73479

Open
rjernst opened this issue May 27, 2021 · 1 comment
Open

Investigate customizing netty resolver used by Azure SDK #73479

rjernst opened this issue May 27, 2021 · 1 comment
Assignees
Labels
:Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.

Comments

@rjernst
Copy link
Member

rjernst commented May 27, 2021

With the new version of the Azure SDK (12.11.1), the sdk switched to using Netty to internally resolve dns. The new resolver tries to look at /etc/hosts as well as /etc/resolver and /etc/resolv.conf.

We have been trying to limit how plugins are able to interact with the system. We don't want plugins reading arbitrary files from the system (see an explanation in #69464). This issue is to investigate whether we can avoid using the netty dns resolver that looks at these system configuration files.

@rjernst rjernst added the :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs label May 27, 2021
@elasticmachine elasticmachine added the Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. label May 27, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (Team:Distributed)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
Projects
None yet
Development

No branches or pull requests

3 participants