BIND 10 #2900: Investigate and fix mixed and missing log messages

[BIND 10 Development]

#2900: Investigate and fix mixed and missing log messages
-------------------------------------+-------------------------------------
            Reporter:  muks          |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:
           Component:  logging       |  Previous-Sprint-Proposed
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  meta          |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by jinmei):

 * estimatedhours:  0 => meta


Old description:

> This is a ticket created after #2198 has been merged.
>
> Even with a mutex lock to mutually synchronize threads, we still see the
> mixed and missing log messages. The latest observation is that writes
> between lock...unlock seem to be buffered and happen later after the
> unlocks happen.
>
> This especially seems to be triggered by the lettuce tests, where BIND 10
> output is redirected using `subprocess.Popen`.
>
> This is a ticket to investigate this behaviour, and fix the problem.

New description:

 This is a ticket created after #2198 has been merged.

 Even with a mutex lock to mutually synchronize threads, we still see the
 mixed and missing log messages. The latest observation is that writes
 between lock...unlock seem to be buffered and happen later after the
 unlocks happen.

 This especially seems to be triggered by the lettuce tests, where BIND 10
 output is redirected using `subprocess.Popen`.

 This is a ticket to investigate this behaviour, and fix the problem.

 Consider this as a meta ticket, keeping track of the issue until the
 final resolution.

 The currently suggested development subtask is #3000

--

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