BIND 10 #338: imporve zonemgr jitter rule

[BIND 10 Development]

#338: imporve zonemgr jitter rule
------------------------------------+---------------------------------------
      Reporter:  zzchen_pku         |        Owner:  zzchen_pku
          Type:  enhancement        |       Status:  closed    
      Priority:  major              |    Milestone:            
     Component:  secondary manager  |   Resolution:  complete  
      Keywords:                     |    Sensitive:  0         
Estimatedhours:  0.0                |        Hours:  0         
      Billable:  1                  |   Totalhours:  0         
      Internal:  0                  |  
------------------------------------+---------------------------------------
Changes (by zzchen_pku):

  * status:  assigned => closed
  * resolution:  => complete


Comment:

 Someone suggested that we only need jitter for the first refresh of any
 given zone.
 As the zone's "next_refresh_time" can be modified by notify-in,after
 running for a period,some zone's "next_refresh_time" may become the same
 again, so I will keep it as it is.
 Ticket #340 provides customizable configuration for jitter scope and
 Ticket #339 lists all of the zones along with their refresh and expiry
 times. I believe the two tickets can handle the jitter problem.

 I think we can close it, will reopen it if necessary.

-- 
Ticket URL: <http://bind10.isc.org/ticket/338#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development