BIND 10 #2222: Implement counters into Xfrout (2/3)

BIND 10 Development do-not-reply at isc.org
Tue Sep 25 08:11:36 UTC 2012


#2222: Implement counters into Xfrout (2/3)
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  naokikambe
  naokikambe                         |                Status:  reviewing
                       Type:         |             Milestone:
  enhancement                        |  Sprint-20120925
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  xfrout                             |  Estimated Difficulty:  4
                   Keywords:         |           Total Hours:  2.15
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => naokikambe
 * totalhours:  0 => 2.15


Comment:

 Hello

 Replying to [comment:13 naokikambe]:
 > Replying to [comment:12 vorner]:
 >
 > OTOH in this situation the stats module collects statistics from xfrout
 at least every second. In the above case axfr_running cannot be 1 because
 transferring is already done when querying statistics. However this test
 would make sense if transferring takes more than one second. For that we
 should use so large size of zone. Would we like to do that in lettuce?
 Otherwise I think we shouldn't do that because this test doesn't make
 sense in most situation.

 I think there may be better and more reliable ways for this kind of test.
 What
 I'd do is creating a fake client. It would start the transfer, but it
 would
 pause for a while before reading data. The zone would have to be large
 enough
 to fill the TCP buffer, but not that huge to take over a second by itself.

 But that's obviously too large for this ticket. Should I create a new one
 for
 it, or do you want to create it yourself?

 > So may I remove this test from `xfrin_notify_handling.feature`?

 Yes, please remove it.

 After the removal, it seems good enough for merge.

 Thank you

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


More information about the bind10-tickets mailing list