BIND 10 #1356: Simultaneous transfers fail with Sqlite3 data source
BIND 10 Development
do-not-reply at isc.org
Tue Jan 22 21:42:31 UTC 2013
#1356: Simultaneous transfers fail with Sqlite3 data source
-------------------------------------+-------------------------------------
Reporter: vorner | Owner:
Type: defect | UnAssigned
Priority: low | Status:
Component: xfrin | reviewing
Keywords: | Milestone:
Sensitive: 0 | Sprint-20130205
Sub-Project: DNS | Resolution:
Estimated Difficulty: 3 | CVSS Scoring:
Total Hours: 0 | Defect Severity: High
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:7 jelte]:
> So just add this to the XFRIN_XFR_OTHER_FAILURE description?
>
> {{{
> One common cause of this error could be a locked database; especially
when
> using sqlite3 which does not support simultaneous transactions. This is
> not a critical error, and the transfer will be attempted again at the
next
> retry time.
> }}}
To be very precise, "which does not support simultaneous transactions"
should be something like "where a single transaction involving write
operations blocks any other read or write transactions" (i.e.,
multiple read transactions should still be okay, if I understand it
correctly). But other than the wording (the original wording is
probably okay, too, as the point is quite subtle) it looks okay.
--
Ticket URL: <http://bind10.isc.org/ticket/1356#comment:8>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list