BIND 10 #1356: Simultaneous transfers fail with Sqlite3 data source

BIND 10 Development do-not-reply at isc.org
Wed Jan 23 10:25:08 UTC 2013


#1356: Simultaneous transfers fail with Sqlite3 data source
-------------------------------------+-------------------------------------
            Reporter:  vorner        |                        Owner:  jelte
                Type:  defect        |                       Status:
            Priority:  low           |  closed
           Component:  xfrin         |                    Milestone:
            Keywords:                |  Sprint-20130205
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DNS           |  wontfix
Estimated Difficulty:  3             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  High
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by jelte):

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


Comment:

 It's even more subtle ;)

 Now that I read the documentation again, it should for most of the write-
 transaction (technically there is a difference between types of operations
 and types of locks btw) still be possible to read, only during the actual
 commit should all other operations fail. But of course that might very
 well be most of the actual processing time.

 But I guess any text is ok indeed. Taking yours, committed, closing
 ticket.

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


More information about the bind10-tickets mailing list