github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 01:38:56 -04:00
Code Issues Projects Releases Packages Wiki Activity

fix(NA): apply ipv4 first dns result order for worker threads (#163484)

Browse source 
This PR is a follow up of https://github.com/elastic/kibana/pull/163025
as we discover the initial fix doesn't apply correctly to working
threads during development.
This commit is contained in:
Tiago Costa 2023-08-09 16:49:57 +01:00 • committed by GitHub
parent 49849cf42c
commit f4856f7478
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 14 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

13
src/setup_node_env/dns_ipv4_first.js Normal file
View file

@ -0,0 +1,13 @@
/*
* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
* or more contributor license agreements. Licensed under the Elastic License
* 2.0 and the Server Side Public License, v 1; you may not use this file except
* in compliance with, at your election, the Elastic License 2.0 or the Server
* Side Public License, v 1.
*/
// enables Node 16 default DNS lookup behavior for the current thread
require('dns').setDefaultResultOrder('ipv4first');
// overrides current process node options, so it can be restored in worker threads too
process.env.NODE_OPTIONS = `${process.env.NODE_OPTIONS || ''} --dns-result-order=ipv4first`;

2
src/setup_node_env/index.js
View file

@ -10,7 +10,7 @@
require('./setup_env');
// restore < Node 16 default DNS lookup behavior
require('dns').setDefaultResultOrder('ipv4first');
require('./dns_ipv4_first');
require('@kbn/babel-register').install();
require('./polyfill');