[Bugs] [Bug 1240577] Data Tiering: Database locks observed on tiered volumes on continous writes to a file

bugzilla at redhat.com bugzilla at redhat.com
Tue Jul 7 09:58:29 UTC 2015


Joseph Elwin Fernandes <josferna at redhat.com> changed:

           What    |Removed                     |Added
                 CC|                            |josferna at redhat.com

--- Comment #1 from Joseph Elwin Fernandes <josferna at redhat.com> ---
The reason this happens is in WAL mode opening a new db connection is an
expensive operation as it will try to a lock on the WAL file(even though for a
short time). The migration process opens a new connection per brick per
promotion/demotion cycle. This is bad scheme.

1) Create a new connection only in tier_init per brick and have the connection
alive and use it for every promotion/demotion 
2) Enable pooling (Pooling=True in the connection string) when the connection
is established, there isn't any locking of WAL file, because existing
connections are reused internal to sqlite.


You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list