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

Should we track seconardy servers separately from the primary instance? #37695

Closed
toddself opened this issue May 31, 2019 · 3 comments
Closed
Labels
discuss Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@toddself
Copy link
Contributor

@restrry posed this on the pr for multiple http servers and it likely bears a quick thought.

I originally put the primary server in the map and was calling it servers, but thought we might need to easily gain access to the primary one.

perhaps we don't?

@jen-huang jen-huang added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc discuss labels Jun 4, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform

@mshustov
Copy link
Contributor

mshustov commented Jun 5, 2019

I think it's unnecessary change anything until we have a real reason to do so, feel free to ignore my comment in that PR

@mshustov
Copy link
Contributor

mshustov commented Aug 1, 2019

close as original implementation was reverted in #42333

@mshustov mshustov closed this as completed Aug 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

4 participants