BIND 10 #1001: busy loop in notify_out
BIND 10 Development
do-not-reply at isc.org
Tue Jun 28 02:36:44 UTC 2011
#1001: busy loop in notify_out
-------------------------------------+-------------------------------------
Reporter: | Owner: zzchen_pku
jinmei | Status: closed
Type: | Milestone:
defect | Sprint-20110628
Priority: major | Resolution: fixed
Component: | Sensitive: 0
xfrout | Sub-Project: DNS
Keywords: | Estimated Difficulty: 4.0
Defect Severity: High | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by zzchen_pku):
* status: reviewing => closed
* resolution: => fixed
Comment:
Replying to [comment:8 jelte]:
> > > First of all, it is noted by TODO that it shouldn't look for slaves
directly in the database. Certainly true, and I think we might not want
the code in notify to look for it at all (but rather have it passed by
xfrout, which also has a better chance to discover which slaves it should
not send to. I'm mainly thinking of the problem i have right now that my
bind10 is sending notifies to itself)
> > Yeah, shall we create a ticket for it now?
>
> please do :)
#1059 has been created for it.
> > > ZoneNotifyInfo, the docstring of __init__ talks about one specific
member variable. That info should be placed at that variable.
> > >
> > > The comment about exponential backoff on line 381 should go one line
earlier imo
> > Updated.
> > Please check, thanks.
>
> looks good
>
> I think this code can be merged
okay, merged, thanks for your review.
--
Ticket URL: <http://bind10.isc.org/ticket/1001#comment:9>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list