BIND 10 #3000: reproduce mixed log issues

BIND 10 Development do-not-reply at isc.org
Mon Feb 17 20:06:49 UTC 2014


#3000: reproduce mixed log issues
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  logging       |  closed
            Keywords:                |                    Milestone:
           Sensitive:  0             |  bind10-1.2-release-freeze
         Sub-Project:  Core          |                   Resolution:
Estimated Difficulty:  5             |  complete
         Total Hours:  0             |                 CVSS Scoring:
                                     |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by stephen):

 * status:  reviewing => closed
 * resolution:   => complete


Comment:

 Reviewed commit b3b16651cfdaf35aae6f2bfa367b8531622bbb8d

 Running on Ubuntu 12.04, I can reproduce the behaviour described by
 vorner:

 a) If flush is true, no mixing happens, if it's false, it produces mixed
 messages.

 b) If mixed messages occur, they tend to be at the head of the file (and
 rare): in a 640,008-line file, three runs of the b10-mixer each produced
 seven mixed messages, all within the first 4,000 lines.  (I speculate that
 each mixed message is the result of the first write by a new process.)

 c) Not mentioned by vorner, towards the end of the file (all after line
 600,000) in each run were seven blank lines.  (I speculate that each is
 caused by a process terminating.)

 It is not clear what is happening and so, as per the ticket description,
 this ticket is being closed.  Ticket #2900 is left open as the development
 task for fixing the problem.

 Branch trac3000 (that contains the code reproducing the issue) is
 '''not''' being merged to master. A note that this branch contains such
 code is being added to the notes in #2900.

-- 
Ticket URL: <https://bind10.isc.org/ticket/3000#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list