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

Configure Kibana for multiple ES servers/nodes (in the same cluster) #2260

Closed
Ellesedil opened this issue Dec 11, 2014 · 10 comments
Closed

Configure Kibana for multiple ES servers/nodes (in the same cluster) #2260

Ellesedil opened this issue Dec 11, 2014 · 10 comments

Comments

@Ellesedil
Copy link

In our QA environment, we have two servers running Elasticsearch in the same cluster, which effectively means we have two nodes. Right now, we have Kibana set up on only one of the servers, and it's currently configured to use that sever's ES instance for it's connection to our data. When ES needs to be cycled or otherwise brought down on the box, Kibana breaks because it cannot connect.

After about 30 minutes of searching, this is the closest thing I could find my issue: #22. But the distinction is I want Kibana to still pay attention only to a single cluster, but have data served to it from multiple nodes.

Is it possible to configure Kibana to set multiple ES servers/nodes for it's connection to the ES cluster? If so, could the documentation be updated somewhere to reflect how to do this? Thanks.

@rashidkpc rashidkpc reopened this Dec 11, 2014
@rashidkpc
Copy link
Contributor

Simply setup an elasticsearch client-only on the Kibana host (see here: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-node.html)

Then point kibana at localhost, the ES client node will do the work of making sure it knows which nodes are live and which aren't.

@Ellesedil
Copy link
Author

That solves part of the issue, but Kibana still has a single node as a point of failure. If the client node has to be brought down for whatever reason, then Kibana has nothing to connect to. Configuring multiple client nodes for redundancy is a moot point. So, two things:

  1. Is there any reference to this in the Kibana documentation so people can find how to do this in the future?
  2. Is this the best that can be hoped for? At this point, it sounds like there should be a feature request to allow multiple nodes to be configured in Kibana, and it will cycle through them in order when there's something to do until it finds an active node or has checked them all.

@rashidkpc
Copy link
Contributor

Configure the client node on localhost, have kibana talk to localhost. If that host goes down Kibana would be down anyway. Alternatively use something like HAProxy, or a dedicated load balancer in front of elasticsearch. We do not plan to implement cycling through nodes in the near future, elasticsearch client nodes accomplish the goal and do a great job of it.

@ccrivelli
Copy link

I have two questions about this topic.

  1. If the elasticsearch cluster (server nodes) is already configured with shield and ssl certificates, should shield be installed and configured (with all the certificates in the keystore) also in the elasticsearch client node (where kibana is running)? In other words, should an elasticsearch client node be 'secured' like the server nodes (creating a certificate request, signing the the certificate request by the root ca, then installing the signed cert) to become a member of the existing cluster and to be able to connect to the server nodes?

  2. The same elasticsearch cluster (server nodes) is configured to authenticate against an external Active Directory over ldaps. This has NOT to be implemented/configured on the elasticsearch client node. Correct?

Thanks.

@chamarts
Copy link

@ccrivelli old thread. but just wondering if you figure out the answer

@chilcano
Copy link

chilcano commented Jun 9, 2016

The same here!
@ccrivelli +1

@ankitjhil
Copy link

Same here!
@ccrivelli +1

@eamocanu
Copy link

+1

@Dom-nik
Copy link

Dom-nik commented Nov 18, 2016

@ccrivelli +1

@rashidkpc
Your answer is useful, but this is not an available option for everyone, it seems. For the users who are considering X-Pack it means paying extra for another ES license (for the client/load balancer node) to get HA in Kibana.

@mchenx
Copy link

mchenx commented May 20, 2020

markov00 added a commit that referenced this issue Dec 21, 2023
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [@elastic/charts](https://togithub.com/elastic/elastic-charts) |
[`61.0.3` ->
`61.2.0`](https://renovatebot.com/diffs/npm/@elastic%2fcharts/61.0.3/61.2.0)
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/@elastic%2fcharts/61.2.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@elastic%2fcharts/61.2.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@elastic%2fcharts/61.0.3/61.2.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@elastic%2fcharts/61.0.3/61.2.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>elastic/elastic-charts (@&#8203;elastic/charts)</summary>

###
[61.2.0](elastic/elastic-charts@v61.1.0...v61.2.0)
(2023-12-19)


##### Bug Fixes

* **deps:** update dependency @elastic/eui to ^91.1.0
([#2267](elastic/elastic-charts#2267))
([308e974](elastic/elastic-charts@308e974))
* **deps:** update dependency @elastic/eui to ^91.2.0
([#2268](elastic/elastic-charts#2268))
([29cdcb3](elastic/elastic-charts@29cdcb3))
* **metric:** background colors and sparkline rendering
([#2255](elastic/elastic-charts#2255))
([5abddfc](elastic/elastic-charts@5abddfc))
* **partition:** rendering with small radius
([#2273](elastic/elastic-charts#2273))
([95a8537](elastic/elastic-charts@95a8537))
* **partition:** zero value sectors cause max stack call
([#2260](elastic/elastic-charts#2260))
([4b30db7](elastic/elastic-charts@4b30db7))
* **theme:** legacy margins
([#2262](elastic/elastic-charts#2262))
([299c869](elastic/elastic-charts@299c869))


##### Features

* increase tooltip width to 500px and truncate items to 2 lines
([#2261](elastic/elastic-charts#2261))
([afdef1c](elastic/elastic-charts@afdef1c))

###
[`v61.1.0`](https://togithub.com/elastic/elastic-charts/blob/HEAD/CHANGELOG.md#6110-2023-11-20)

[Compare
Source](https://togithub.com/elastic/elastic-charts/compare/v61.0.3...v61.1.0)

##### Bug Fixes

- **deps:** update dependency
[@&#8203;elastic/eui](https://togithub.com/elastic/eui) to v91
([#&#8203;2233](https://togithub.com/elastic/elastic-charts/issues/2233))
([e89f623](https://togithub.com/elastic/elastic-charts/commit/e89f623792312c4f6b609ebb975de0800f3c297e))
- **metric:** add option to set empty cell background color
([#&#8203;2247](https://togithub.com/elastic/elastic-charts/issues/2247))
([6a9fb86](https://togithub.com/elastic/elastic-charts/commit/6a9fb86bee5212a47060c5070f260961097014b4))
- **metric:** background color for bar with interactions
([#&#8203;2248](https://togithub.com/elastic/elastic-charts/issues/2248))
([dcb56fa](https://togithub.com/elastic/elastic-charts/commit/dcb56fa08540631a9b3b0e588352ee6daf3d54a0))

##### Features

- **bullet:** improve header layout and positioning
([#&#8203;2243](https://togithub.com/elastic/elastic-charts/issues/2243))
([b3a95d2](https://togithub.com/elastic/elastic-charts/commit/b3a95d24fb02690ca6599622352c743c04624690))
- **bullet:** new design style and implementation
([#&#8203;2156](https://togithub.com/elastic/elastic-charts/issues/2156))
([fca6cdd](https://togithub.com/elastic/elastic-charts/commit/fca6cdd5bc34a65c0792dbab7d756404bf43501b))

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/elastic/kibana).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy44Ny4yIiwidXBkYXRlZEluVmVyIjoiMzcuMTAzLjEiLCJ0YXJnZXRCcmFuY2giOiJtYWluIn0=-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Marco Vettorello <marco.vettorello@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants