BIND 10 #299: AXFR fails half the time
BIND 10 Development
do-not-reply at isc.org
Tue Nov 2 07:15:53 UTC 2010
#299: AXFR fails half the time
-----------------------------+----------------------------------------------
Reporter: zzchen_pku | Owner: zzchen_pku
Type: defect | Status: reviewing
Priority: major | Milestone:
Component: xfrout | Resolution:
Keywords: | Sensitive: 0
Estimatedhours: 0.0 | Hours: 0
Billable: 1 | Totalhours: 1.5
Internal: 0 |
-----------------------------+----------------------------------------------
Comment(by jinmei):
Replying to [comment:31 zhanglikun]:
> the events should like this:
I don't think this is correct in trac #299:
> =0.2sec: client B sends an AXFR request for zone Y, b10-xfrout create
another thread for zone Y's transfer-out. Now there are two transfer-out
threads.
The AXFR from client B should be transferred from b10-auth to b10-xfrout
via "the long connection between Xfrout and Auth". And a single
!XfroutSession instance (corresponding to the same single thread) handles
all incoming requests sequentially.
Or am I misreading the trac299 code?
--
Ticket URL: <http://bind10.isc.org/ticket/299#comment:32>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list