BIND 10 #387: xfrin not checking for new copy of zone

[BIND 10 Development]

#387: xfrin not checking for new copy of zone
-------------------------------------+-------------------------------------
                 Reporter:  shane    |                Owner:  vorner
                     Type:  defect   |               Status:  reviewing
                 Priority:  minor    |            Milestone:
                Component:  xfrin    |  Sprint-20110419
                 Keywords:           |           Resolution:
Estimated Number of Hours:  0.0      |            Sensitive:  0
                Billable?:  1        |  Add Hours to Ticket:  0
                Internal?:  0        |          Total Hours:  0
-------------------------------------+-------------------------------------
Changes (by zzchen_pku):

 * owner:  zzchen_pku => vorner


Comment:

 Replying to [comment:17 vorner]:
 > Hello
 > This should solve the problem it does not check them after restart. But
 why no new zone arrived at the beginning? Was it a different problem or
 misunderstanding and there's no problem?
 In the original implementation, zonemgr manage zones in sqlite db, so no
 new zone arrives at the beginning.
 > And, what if someone have really a lot of zones? In that case most of
 them will try to refresh near the startup (not directly at once because of
 the jitter), and the retry time should probably be short (a lot shorter
 than usual refresh). Is it possible to limit number of concurrent requests
 or something? (I know this is out of scope of this ticket).
 I think xfrin should do this work,  xfrin has its own _max_transfers_in,
 when the concurrent requests exceeds  _max_transfers_in, it can send a
 command with ZONE_XFRIN_FAILED flag to zonemgr, then zonemgr will retry to
 do refresh for the specified zone.

 I will merge the patch, thanks.

-- 
Ticket URL: <https://bind10.isc.org/ticket/387#comment:18>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development