Ad Widget

Collapse

Distributed configuration updates

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • xs-
    Senior Member
    Zabbix Certified Specialist
    • Dec 2007
    • 393

    #1

    Distributed configuration updates

    Hi,

    When trying to update configuration of a distributed node via the master node webinterface, changes take really long (if at all) to propagate.
    Is this normal? I thought the sync interval was around 10min-60min.

    So far i've been able to determine that these config changes are propagated every 2-6 hours, if i'm lucky, sometimes changes don't get propagated at all (i think if the master node restarts during the wait period).

    Is there a way to decrease the interval time? I've tries to search the sources but no luck so far.

    -- Edit
    I've seen this behavior with 1.4.4 and it seems the same with 1.4.5 (upgraded a couple of hours ago)
  • Alexei
    Founder, CEO
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2004
    • 5654

    #2
    I believe the inter-node update interval is no longer than 5 minutes by default.
    Alexei Vladishev
    Creator of Zabbix, Product manager
    New York | Tokyo | Riga
    My Twitter

    Comment

    • xs-
      Senior Member
      Zabbix Certified Specialist
      • Dec 2007
      • 393

      #3
      I'll use our upgraded 1.4.5 setup as a reference.

      I did the following tests (with trigger name configurations, different triggers each time ofcourse):
      - Update slave node config via the master node web interface (VIA MASTER)
      - Update slave node config slave node web interface (VIA SLAVE)

      - VIA MASTER
      I see the configuration changes on the master web interface with slave node selected. On the slave web interface, these changes are not visible.
      Besides this, before the update, 2 triggers were ON on the slave, visible on the master. After the change, these triggers were gone on the master, but still visible on the slave.
      Master logfile does not show any attempt to send configuration to slave, slave logfile does not show any configuration push from the master.

      - VIA SLAVE
      It took about 5-15 min (i verified on the master web interface after 15 min) for the change to propagate to the master node.
      Changes visible on the master webinterface, all seems well.
      Master log file doesnt show configuration updates (i think this would be 'data' update). Slave node shows its sending configuration changes to master.
      ---------------8<---------------------- (on slave node)
      7848:20080328:084649 NODE 3: Sending configuration changes of node 3 to node 1 datalen 544
      7848:20080328:084859 NODE 3: Sending configuration changes of node 3 to node 1 datalen 21188
      7848:20080328:095110 NODE 3: Sending configuration changes of node 3 to node 1 datalen 544
      ---------------8<----------------------



      Conclusion
      Slave node -> master node configuration updates seem to go well, no prob here
      Master node -> slave node configuration updates are definitely not happening every 5 min (in our environment that is), and i wonder if they will happen at all (if they happen, ill update this thread).

      Comment

      • xs-
        Senior Member
        Zabbix Certified Specialist
        • Dec 2007
        • 393

        #4
        I am still experiencing this issue.

        client node -> master node updates are fine and within the 5 min limit
        master node -> client node updates are around the 2+ hour interval (if at all)

        Is there a way to verify config update attempts?
        Where, in the sources, can i find the interval parameters for this?

        I cant find any info on this except the manual stating that this is a short time.

        Comment

        Working...