Start lifecycle of "telemetry" plugin wasn't completed in 30sec

[rudolf]

The telemetry plugin frequently takes more than 30s to complete which causes Kibana to fail to start up. Plugin's lifecycle methods should not block Kibana from starting up see https://github.com/elastic/kibana/blob/6042a01f385078587e8e09418ef07f69ec2dadf7/rfcs/text/0007_lifecycle_unblocked.md and #53268

Versions where I've seen this behaviour (although other versions are likely affected too):

• 7.9.1
• 7.9.2

[elasticmachine]

Pinging @elastic/kibana-telemetry (Team:KibanaTelemetry)

[shasts]

Plugin's setup lifecycle should not block Kibana from starting up

Would this help cases like https://github.com/elastic/sdh-kibana/issues/582 too?

[rudolf]

@shasts No. Your link describes a case where monitoring was disabled for security reasons CVE-2020-7013 and CVE-2020-7015. However enabling or disabling a plugin causes Kibana to have to re-run the "optimizer" and this takes up considerably more memory than when Kibana runs without the optimizer. In this case, more memory than was available to Kibana.

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)