Bug 1276248
Summary: | [Tier]: restarting volume reports "insert/update failure" in cold brick logs | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Rahul Hinduja <rhinduja> | |
Component: | tier | Assignee: | Joseph Elwin Fernandes <josferna> | |
Status: | CLOSED ERRATA | QA Contact: | Rahul Hinduja <rhinduja> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | rhgs-3.1 | CC: | asrivast, dlambrig, josferna, rhs-bugs, sankarshan, storage-qa-internal | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | RHGS 3.1.2 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.7.5-7 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1277352 (view as bug list) | Environment: | ||
Last Closed: | 2016-03-01 05:48:18 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: | ||||
Bug Blocks: | 1260783, 1260923, 1277352, 1279059 |
Description
Rahul Hinduja
2015-10-29 08:55:53 UTC
This is caused due to the lookup heal. Well CTR doesnt read from the DB, so to make sure that file records are created it does a heal during a lookup. It remembers the decision in the inode context cache and retrys periodically. When the volume is restarted it looses all the inode cache from the previous time and CTR lookup heals tries the heal again, but this time it finds that the records are already there from sql and logs this error, and remembers this until the volume is restarted or inode is flushed out of inode cache of the brick. Solution: the log levels should be reduced to trace for this case and customers need not see this. What is the default? Default should be, we do not see the logs. If more information is needed, then we setup the loglevel to see the additional logs. Well any insert/update failure to the Db should be ERROR. But for this special case we should use TRACE. Upstream patch posted : http://review.gluster.org/#/c/12491 Per RCA, the log message is not an error. The merged patch makes the behavior visible at the trace level. this has not been put up in 3.7.5-6 as it has been moved to modified from on_qa by dev Verified with build: glusterfs-3.7.5-13.el7rhgs.x86_64 No errors related to insert/update is observed on brick logs. Moving the bug to verified state. [root@dhcp37-165 glusterfs]# grep -ri "insert" * [root@dhcp37-165 glusterfs]# [root@dhcp37-165 bricks]# grep -ri "insert" * [root@dhcp37-165 bricks]# Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0193.html |