mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 09:19:04 -04:00
[es/versionCheck] explain why we need to track per-server
This commit is contained in:
parent
cda9594859
commit
5eb9ccdc41
1 changed files with 8 additions and 2 deletions
|
@ -9,8 +9,14 @@ import semver from 'semver';
|
|||
import isEsCompatibleWithKibana from './is_es_compatible_with_kibana';
|
||||
import SetupError from './setup_error';
|
||||
|
||||
// tracks the node descriptions that get logged in warnings so
|
||||
// that we don't spam the log with the same message over and over
|
||||
/**
|
||||
* tracks the node descriptions that get logged in warnings so
|
||||
* that we don't spam the log with the same message over and over.
|
||||
*
|
||||
* There are situations, like in testing or multi-tenancy, where
|
||||
* the server argument changes, so we must track the previous
|
||||
* node warnings per server
|
||||
*/
|
||||
const lastWarnedNodesForServer = new WeakMap();
|
||||
|
||||
module.exports = function checkEsVersion(server, kibanaVersion) {
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue