Feature Request: client-node interface
Bug #1604957 reported by
james beedy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
elasticsearch (Juju Charms Collection) |
New
|
Undecided
|
Unassigned |
Bug Description
Have you guys entertained the idea of adding elasticsearch client-node capability to Juju deployed elasticsearch clusters?
I feel like this could be easily accomplished by making node.master and node.data configurable through charm config params, alongside a client node interface .... possibly might just need a new es-client charm.
client-node -> https:/
To post a comment you must log in.
This is a great idea and seems like a great feature for high traffic systems.
An alternative idea for how to handle this would be to have the Juju leader unit act as the primary entry point and load balancer and have it automatically configure itself as a client. However, this might be more complicated to implement and perhaps having it as a separate service is cleaner and more flexible.
If it is going to be deployed as an independent service, I would recommend having it as a separate charm, to force it to be deployed and scaled independently, and to make it clear that it has a dedicated role.