BIND 10 #1847: CC timeouts in auth
BIND 10 Development
do-not-reply at isc.org
Wed Apr 4 02:12:32 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: 2
Keywords: | Total Hours: 0
Defect Severity: N/A |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by naokikambe):
Replying to [comment:12 jinmei]:
> One possibility I had in my mind is that b10-auth stores
> statistics in a separate storage such as an SQLite3 DB file, maybe in
> a periodic batch task. b10-stats or any other statistics clients
> would then retrieve the stored statistics values from that storage
> separately.
IMO stats might periodically pull out statistics from each module via a CC
session, and store them into an SQLite3 DB together with a timestamp.
Because maybe auth is very busy to answering DNS queries, and its
asynchronous writing to the SQLite3 DB is likely to be very difficult. I'm
afraid it might be possible to affect its response performance. That
situations of auth are definitely in my image. If we complete replacing
the current msgq with another better implement, couldn't that issue be
problem, which is transmitting large bytes in the CC channel?
Thanks
--
Ticket URL: <http://bind10.isc.org/ticket/1847#comment:13>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list