BIND 10 #2861: synchronization between auth main thread and datasrc builder

[BIND 10 Development]

#2861: synchronization between auth main thread and datasrc builder
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  medium        |                    Milestone:  Next-
           Component:  b10-auth      |  Sprint-Proposed
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |  shared memory data source
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Description changed by jinmei:

Old description:

> Subtask of #2830.  No dependency.
>
> b10-auth will now need to wait for the completion of initial data
> source setup (create clients and load any local-cached zones) because
> until then the main thread cannot know which data source needs shared
> segments.
>
> I'm not sure what's the best way to do this, but one possible (but
> naive) approach is to run a timer while the builder thread is working
> on the "RECONFIGURE" command, and let the builder update some shared
> info when it's done.  the main thread periodically checks the state
> until it's completed.
>
> We could (should?) also defer listening to queries until it's
> completed because partially working server would be rather harmful (I
> guess there's a ticket on this).
>
> Consider a better way to do this if any, and implement it.

New description:

 Subtask of #2830.  No dependency.

 b10-auth will now need to wait for the completion of initial data
 source setup (create clients and load any local-cached zones) because
 until then the main thread cannot know which data source needs shared
 segments.

 I'm not sure what's the best way to do this, but one possible (but
 naive) approach is to run a timer while the builder thread is working
 on the "RECONFIGURE" command, and let the builder update some shared
 info when it's done.  the main thread periodically checks the state
 until it's completed.

 We could (should?) also defer listening to queries until it's
 completed because partially working server would be rather harmful (see
 #2510).

 Consider a better way to do this if any, and implement it.

--

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