BIND 10 #2212: support "load zone" command in the configurator thread

BIND 10 Development do-not-reply at isc.org
Tue Sep 4 06:32:41 UTC 2012


#2212: support "load zone" command in the configurator thread
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:  task   |             Milestone:  Next-Sprint-
                   Priority:         |  Proposed
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  b10-auth                           |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  5
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
  background zone loading            |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Description changed by jinmei:

Old description:

> A subtask of #2201, depend on #2202, #2203, #2205, #2209
>
> This task extends the newly introduced "data source configurator"
> thread (#2205) to support background zone reloading.
>
> It will be based on the current content of LoadZoneCommand::exec(),
> but works as follows:
> - first call `ConfigurableClientList::getCacheZoneUpdater()`
>   introduced in #2209
> - then call updater->load()
> - then acquire the lock introduced in #2202
> - then call updater->install()
> - then release the lock
> - then call updater->cleanup().
>
> Note that updater operations can throw.

New description:

 (We probably don't have time to do this for the September release)

 A subtask of #2201, depend on #2202, #2203, #2205, #2209

 This task extends the newly introduced "data source configurator"
 thread (#2205) to support background zone reloading.

 It will be based on the current content of LoadZoneCommand::exec(),
 but works as follows:
 - first call `ConfigurableClientList::getCacheZoneUpdater()`
   introduced in #2209
 - then call updater->load()
 - then acquire the lock introduced in #2202
 - then call updater->install()
 - then release the lock
 - then call updater->cleanup().

 Note that updater operations can throw.

--

-- 
Ticket URL: <http://bind10.isc.org/ticket/2212#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list