Kiban can run in dedicated modes via node roles. One of these roles is for the task manager background node. When Kibana runs with this role it does not respond to incoming HTTP traffic from the UI. It is only responsible for running tasks. Kibana startup time is dependent on the number of plugins being loaded. The reason is that Kibana on start discovers all available plugins and loads from the disk the code of each plugin. The same list of plugins is enabled and loaded for all nodes even though the task manager node does not use most. To speed up the startup time of the task manager node we should audit which plugins are not being used by the task manager (or which plugins do not have the task manager as a dependency) and disable them.
Kiban can run in dedicated modes via node roles. One of these roles is for the task manager background node. When Kibana runs with this role it does not respond to incoming HTTP traffic from the UI. It is only responsible for running tasks. Kibana startup time is dependent on the number of plugins being loaded. The reason is that Kibana on start discovers all available plugins and loads from the disk the code of each plugin. The same list of plugins is enabled and loaded for all nodes even though the task manager node does not use most. To speed up the startup time of the task manager node we should audit which plugins are not being used by the task manager (or which plugins do not have the task manager as a dependency) and disable them.