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

[dev.icinga.com #6743] Better explanation for HA config cluster #1807

Closed
icinga-migration opened this issue Jul 16, 2014 · 4 comments
Closed
Labels
area/documentation End-user or developer help enhancement New feature or request
Milestone

Comments

@icinga-migration
Copy link

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

Created by mfriedrich on 2014-07-16 10:57:47 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2014-08-24 09:25:04 +00:00)
Target Version: 2.1.0
Last Update: 2014-09-16 09:22:14 +00:00 (in Redmine)


There is some misunderstanding how HA zones work, especially where to put the configuration.

  1. one instance has /etc/icinga2/zones.d/ populated and syncs/validates that into /var/lib/icinga2/api/zones/
  2. all other instances get the configuration synced (if apilistener accept_config = true) from /var/lib... to /var/lib/... (user won't see it)
  3. if the config "master" dies, all remaining instances still got the current configuration in /var/lib and continue to run (they elect a new zone master doing the primary event processing)
  4. if the previous config master died hard, one can manually copy the configuration from /var/lib... to /etc/icinga2/zones.d/ and make this one the new config master

Possible problems:

  • empty zonename directory on the "slaves", such as /etc/icinga2/zones.d/config-ha-master, causing configsync ping pong
  • all instances have zones.d populated and try to sync each other
  • config master vs zone master (not the same, first one is static by putting the zones.d config, the second one dynamically elected)

Feedback
http://www.monitoring-portal.org/wbb/index.php?page=Thread&postID=206124#post206124
http://www.monitoring-portal.org/wbb/index.php?page=Thread&threadID=31250
https://lists.icinga.org/pipermail/icinga-users/2014-July/008328.html

Changesets

2014-08-24 09:21:54 +00:00 by mfriedrich 32c2013

Documentation: Rewrite cluster docs

* Re-organize structure
* New section with HA features
* Permissions and security
* How to add a new node
* Cluster requirements
* Additional hints on installation
* More troubleshooting

fixes #6743
fixes #6703
fixes #6997

2014-08-27 09:48:44 +00:00 by (unknown) 0ce727e

Documentation: Additional cluster hints, better formatting

refs #6743
refs #6703
refs #6997

Relations:

@icinga-migration
Copy link
Author

Updated by gbeutner on 2014-08-08 09:23:33 +00:00

  • Target Version set to 2.1.0

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-08-24 09:25:04 +00:00

  • Status changed from New to Resolved
  • Done % changed from 0 to 100

Applied in changeset i2:32c20132d014c9735483e1475e0c9864f8290e29.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-08-27 14:35:42 +00:00

  • Relates set to 7010

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-09-16 09:22:14 +00:00

  • Project changed from 42 to Icinga 2
  • Category set to Documentation

@icinga-migration icinga-migration added enhancement New feature or request area/documentation End-user or developer help labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.1.0 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation End-user or developer help enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant