[dev.icinga.com #10977] Different feature sets on endpoints in one HA Zone

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/10977

Created by twidhalm on 2016-01-18 12:08:37 +00:00

Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2016-01-29 09:27:34 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

---

Hi,

Since having the option to run different features on nodes in one HA zone brings a lot of flexibility and was announced as one of the great features of Icinga 2 ( e.g, https://www.netways.de/fileadmin/images/Events\_Trainings/Events/OSMC/2014/Slides\_2014/Current\_state\_of\_Icinga\_Icinga\_Team.pdf ) I'd like to see this supported again in Icinga 2.

Some usecases (I can get more, if you need more to convince you ;-) )

• Minimal HA Setup - One master with all Addons like IDO, Icinga Web 2, Grapher, etc. and one master only with checker and notification in case the real master breaks down.
• Load balancing Checker. In case one (or more) master is not enough to run all desired check plugins, extra hosts with only checker active could help to balance the load. Running all other features would cause a lot of overhead.
• Running features on a designated host within the HA / LB setup to handle writing performance data or to the IDO

For more information on this issue please refer to #10969 , #7206 and #9476

For some features I'd like to see the default behaviour to change so it works per default with different feature sets. e.g. checker and ido should first check what hosts it is running on to determine which hosts should activate and deactivate it to fulfill ha requirements. Right now the default behaviour of ido is that a host with ido running deactivates it if another host is in the same zone regardless of ido running there or not. (Which is not supported right now, as stated in the beforementioned issues)

Cheers,
Thomas

---

Relations:

• relates #10977
• relates #10977
• relates #10977
• relates #10977

[icinga-migration]

Updated by tgelf on 2016-01-20 12:50:23 +00:00

**

I'd also love to see this working as initially designed. Having dedicated nodes for specific tasks in a cluster is an important feature to me (and others).

[icinga-migration]

Updated by mfriedrich on 2016-01-22 15:40:38 +00:00

• Tracker changed from Bug to Feature
• Category set to Cluster

Slides and documentation were not accurate at that time (and have been updated ever since), and clearly such a feature does not fit inside the current cluster design and implementation, as there was a general demand on HA features.

Though I'd like to hear design and implementation specific proposals how that could fit into the current design with e.g. having the checker nodes independent load-balancing, etc. Possibly related: pin checks to specific endpoint nodes, etc. I'll link the other issues.

[icinga-migration]

Updated by mfriedrich on 2016-01-22 15:41:28 +00:00

• Relates set to 10040

[icinga-migration]

Updated by mfriedrich on 2016-01-22 15:42:04 +00:00

• Relates set to 10709

[icinga-migration]

Updated by mfriedrich on 2016-01-22 15:42:37 +00:00

• Relates set to 10679

[icinga-migration]

Updated by mfriedrich on 2016-01-29 09:27:34 +00:00

• Target Version set to Backlog

[icinga-migration]

Updated by mfriedrich on 2016-11-09 14:53:31 +00:00

• Relates set to 12955

[gunnarbeutner]

There are no plans to support this.