Bug 1270123
Summary: | Data Tiering: Database locks observed on tiered volumes on continous writes to a file | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Joseph Elwin Fernandes <josferna> |
Component: | tiering | Assignee: | Joseph Elwin Fernandes <josferna> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | bugs <bugs> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 3.7.6 | CC: | bugs, dlambrig, josferna, nchilaka, sankarshan, vagarwal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.7.6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1240577 | Environment: | |
Last Closed: | 2015-11-17 05:59:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1240577, 1271729 | ||
Bug Blocks: | 1240569, 1260923, 1265399, 1267242, 1275914 |
Description
Joseph Elwin Fernandes
2015-10-09 02:39:13 UTC
*** Bug 1265399 has been marked as a duplicate of this bug. *** COMMIT: http://review.gluster.org/12325 committed in release-3.7 by Dan Lambright (dlambrig) ------ commit 489f02879afd940d201d092720dbf13b2922b134 Author: Joseph Fernandes <josferna> Date: Fri Sep 18 19:57:54 2015 +0530 tier/ctr: Solution for db locks for tier migrator and ctr using sqlite version less than 3.7 i.e rhel 6.7 Problem: On RHEL 6.7, we have sqlite version 3.6.2 which doesnt support WAL journaling mode, as this journaling mode is only available in sqlite 3.7 and above. As a result we cannot have to progreses concurrently accessing sqlite, without running into db locks! Well WAL is also need for performace on CTR side. Solution: This solution is to use CTR db connection for doing queries when WAL mode is absent. i,e tier migrator will send sync_op ipc calls to CTR, which in turn will do the query and create/update the query file suggested by tier migrator. Pending: Well this solution will stop the db locks but the performance is still an issue for CTR. We are developing an in-Memory Transaction Log (iMeTaL) which will help boost the CTR performance by doing in memory udpates on the IO path and later flush the updates to the db in a batch/segment flush. Master patch: http://review.gluster.org/#/c/12191 >> Change-Id: Ie3149643ded159234b5cc6aa6cf93b9022c2f124 >> BUG: 1240577 >> Signed-off-by: Joseph Fernandes <josferna> >> Signed-off-by: Dan Lambright <dlambrig> >> Signed-off-by: Joseph Fernandes <josferna> >> Reviewed-on: http://review.gluster.org/12191 >> Tested-by: Gluster Build System <jenkins.com> >> Reviewed-by: Luis Pabon <lpabon> Signed-off-by: Joseph Fernandes <josferna> Change-Id: Ie8c7a7e9566244c104531b579126bb57fbc6e32b BUG: 1270123 Reviewed-on: http://review.gluster.org/12325 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Dan Lambright <dlambrig> Tested-by: Dan Lambright <dlambrig> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.6, please open a new bug report. glusterfs-3.7.6 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://www.gluster.org/pipermail/gluster-users/2015-November/024359.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |