BIND 10 #1847: CC timeouts in auth
BIND 10 Development
do-not-reply at isc.org
Mon Apr 2 20:26:33 UTC 2012
#1847: CC timeouts in auth
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: | Status: closed
defect | Milestone: New Tasks
Priority: | Resolution: invalid
medium | Sensitive: 0
Component: | Sub-Project: DNS
Unclassified | Estimated Difficulty: 0
Keywords: | Total Hours: 0
Defect Severity: N/A |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:8 jelte]:
> I have seen this one as well where I don't run Stats. It is not so much
a timeout issue; the problem is that stats collection is a 'push' method;
modules push their stats regularly to the Stats module. Since they expect
the module to answer, and they do not check whether it is running, this
results in a timeout (noone is answering). The easy fix would be to not
expect a response. A better solution might be to make it a pull action
('getstats' or something, initiated by the stats collector)
I'd actually suggest revisiting the IPC method for statistics at more
fundamental level. Blocking/timeout issue aside, I suspect the CC
channel is not appropriate for exchanging statistics information due
to scalability issues. I assume we'd eventually (soon?) like to be
able to have per-zone statistics, while still allowing millions of
zones to be served. If there's a reasonable way of using the CC
channel to exchange all of the statistics, that's fine, but I suspect
we need to use a different method for this purpose.
--
Ticket URL: <http://bind10.isc.org/ticket/1847#comment:9>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list