yahoo-eng-team team mailing list archive

[LIU Yulong <yulong@xxxxxxxxxxxxx>]

Public bug reported:

The ha state change BatchNotifier uses the following calculated
interval.

    def _calculate_batch_duration(self):
        # Slave becomes the master after not hearing from it 3 times
        detection_time = self.conf.ha_vrrp_advert_int * 3

        # Keepalived takes a couple of seconds to configure the VIPs
        configuration_time = 2

        # Give it enough slack to batch all events due to the same failure
        return (detection_time + configuration_time) * 2

It takes almost 16s, by default ha_vrrp_advert_int is 2s, for a single HA router state change to notify neutron server.
Actually before this notify, the ip MonitorDaemon has already set the router to its relevant state.
So no need to wait this long time.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: l3-ha

** Summary changed:

- HA router state change take too much time to notify neutron server
+ HA router state change takes too much time to notify neutron server

** Description changed:

  The ha state change BatchNotifier uses the following calculated
  interval.
  
      def _calculate_batch_duration(self):
          # Slave becomes the master after not hearing from it 3 times
          detection_time = self.conf.ha_vrrp_advert_int * 3
  
          # Keepalived takes a couple of seconds to configure the VIPs
          configuration_time = 2
  
          # Give it enough slack to batch all events due to the same failure
          return (detection_time + configuration_time) * 2
  
- It takes almost 16s for a single HA router state change to notify neutron server.
+ It takes almost 16s, by default ha_vrrp_advert_int is 2s, for a single HA router state change to notify neutron server.
  Actually before this notify, the ip MonitorDaemon has already set the router to its relevant state.
  So no need to wait this long time.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1612069

Title:
  HA router state change takes too much time to notify neutron server

Status in neutron:
  New

Bug description:
  The ha state change BatchNotifier uses the following calculated
  interval.

      def _calculate_batch_duration(self):
          # Slave becomes the master after not hearing from it 3 times
          detection_time = self.conf.ha_vrrp_advert_int * 3

          # Keepalived takes a couple of seconds to configure the VIPs
          configuration_time = 2

          # Give it enough slack to batch all events due to the same failure
          return (detection_time + configuration_time) * 2

  It takes almost 16s, by default ha_vrrp_advert_int is 2s, for a single HA router state change to notify neutron server.
  Actually before this notify, the ip MonitorDaemon has already set the router to its relevant state.
  So no need to wait this long time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1612069/+subscriptions