# Director deploy changes delayed udpated in Icingaweb2

**URL:** <https://community.icinga.com/t/director-deploy-changes-delayed-udpated-in-icingaweb2/3732>\
**Category:** Icinga Web\
**Tags:** icingaweb2, director\
**Created:** [March 9, 2020, 1:37pm UTC](https://community.icinga.com/t/director-deploy-changes-delayed-udpated-in-icingaweb2/3732 "2020-03-09T13:37:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nkortgen](https://community.icinga.com/letter_avatar_proxy/v4/letter/n/87869e/32.png) [@nkortgen](https://community.icinga.com/u/nkortgen)\
**Post date:** [March 9, 2020, 1:37pm UTC](https://community.icinga.com/t/director-deploy-changes-delayed-udpated-in-icingaweb2/3732/1 "2020-03-09T13:37:32Z")

</div>

## Environmental Information

* * *

Version Infos

```
icinga2 - The Icinga 2 network monitoring daemon (version: 2.11.2-1)
Icinga Web 2 Version 2.7.3
director 1.7.2

System information:
  Platform: Red Hat Enterprise Linux Server
  Platform version: 7.7 (Maipo)
  Kernel: Linux
  Kernel version: 3.10.0-1062.12.1.el7.x86_64
  Architecture: x86_64

```

Setup

- Dual Master Setup  
 ![image](https://community.icinga.com/uploads/default/original/2X/d/d72197ea4d09a420b235bd343e7440533ccf0cf2.png)
- Orange =\> Secondary Master
- Blue =\> Primary Master

> Active Endpoints change from time to time but i read that this is a normal behaviour

* * *

## Problem

Any updates done with the director are delayed or even not updated on the webinterface.  
The deployments don’t show any problems and the output of `icinga2 deamon -C` is fine.

 ![image](https://community.icinga.com/uploads/default/original/2X/3/36ee2104e57ee2594d804dfb8979a4b24f4ea8b4.png)

So basically everything configured with the director is displayed with up to 10 minutes delay in icingaweb2.

I have checked multiple logs an can’t find a clue what causes the problem.

---

<div class="post-metadata">

**Author:** ![log1c](https://community.icinga.com/user_avatar/community.icinga.com/log1c/32/2071_2.png) [@log1c](https://community.icinga.com/u/log1c)\
**Post date:** [March 11, 2020, 11:10am UTC](https://community.icinga.com/t/director-deploy-changes-delayed-udpated-in-icingaweb2/3732/2 "2020-03-11T11:10:24Z")

</div>

Could it simply take that long to distribute the config to the many zones/endpoints in your setup?

I don’t have such a big setup myself, biggest, regarding objects, is  
 ![image](https://community.icinga.com/uploads/default/original/2X/7/73882605a4d9a5a56a09dd0b0034f593921eef75.png)

This sometimes takes about a minute to show changes, but this is still only four zones/endpoints.

In this thread:

> [@Icinga2 at large scale](https://community.icinga.com/t/icinga2-at-large-scale/2178):
>
> Hello community, I was not sure where to put this topic, please move it if it’s under wrong category In this topic i would like to cover several questions: system requirements, possible bottlenecks and benchmarking. Hope this will simplify installation for new users and provide “ready for deploy” cluster schemas and strategy. My main goals are: define benchmarking tools for stress testing of cluster prototype define how scalable Icinga2 is, based on stress tests provide system requirements …

There is a mentioning that

> [@Icinga2 at large scale](https://community.icinga.com/t/icinga2-at-large-scale/2178/7):
>
> Configuration propagation in the system takes around 5-6 minutes, time calculated from pressing “Deploy” button in Director to getting hosts visualized in Tactical Overview with Pending status

---

<div class="post-metadata">

**Author:** ![nkortgen](https://community.icinga.com/letter_avatar_proxy/v4/letter/n/87869e/32.png) [@nkortgen](https://community.icinga.com/u/nkortgen)\
**Post date:** [March 18, 2020, 10:44am UTC](https://community.icinga.com/t/director-deploy-changes-delayed-udpated-in-icingaweb2/3732/3 "2020-03-18T10:44:51Z")

</div>

## I probably found more information

The changes are first moved to a _zones-stage_ location.  
This seems to be a new feature, from there on it takes very long to move the changes to production (ca 10-15 minutes)

Is there any configuration i´m missing due to the update which needs to be done to increase the speed with which my changes are deplyoed to production?

 ![image](https://community.icinga.com/uploads/default/original/2X/5/539095c33da72cb5540714986a4a021c3cba64f2.png)

As you can see the actual “services” are firstly moved to _zones-stage_.

---

<div class="post-metadata">

**Author:** ![nkortgen](https://community.icinga.com/letter_avatar_proxy/v4/letter/n/87869e/32.png) [@nkortgen](https://community.icinga.com/u/nkortgen)\
**Post date:** [March 19, 2020, 10:47am UTC](https://community.icinga.com/t/director-deploy-changes-delayed-udpated-in-icingaweb2/3732/4 "2020-03-19T10:47:01Z")

</div>

# (Update)

Provided Image was wrong sorry

 ![image](https://community.icinga.com/uploads/default/original/2X/a/ab96131454cd4b48ef504618eca8a5f910990436.png)