Bug 1331164 - [GSS] - High number of failed heal entries increasing
Summary: [GSS] - High number of failed heal entries increasing
Status: CLOSED DUPLICATE of bug 1339765
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: replicate
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Pranith Kumar K
QA Contact: storage-qa-internal@redhat.com
Depends On:
Blocks: RHGS-3.4-GSS-proposed-tracker
TreeView+ depends on / blocked
Reported: 2016-04-27 20:03 UTC by Pablo Caruana
Modified: 2019-11-14 07:52 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2018-02-14 09:01:23 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Pablo Caruana 2016-04-27 20:03:06 UTC
Description of problem:

For several days, we have had an issue with a high amount of failed heal entries in one of our Gluster nodes.
Enviroment running 2 nodes, 3 Gluster volumes replicated on the 2 nodes.  
gluster_volume_info:cluster.quorum-count: 1
gluster_volume_info:cluster.quorum-type: fixed

Version-Release number of selected component (if applicable):

For some reason  some files are being healed but constantly increasing the number on thousands potential files to health according to the statics. for some reason those are are not being healed.

Comment 3 Pablo Caruana 2016-04-27 20:22:16 UTC
Extending the 1st comment/description
all clients are using glusterfs.fuse with the acl mount option
the number of unhealed files are  increasing by thousands every day during at least 5 days.

Comment 20 Bipin Kunal 2017-08-30 09:12:44 UTC
Hello Ravi,

  From comment #17, it looks like we were not able to completely RCA this issue. Is there anything more which can be done with existing data?

  Apart from this, in comment #16, I had some questions. Could you please have a look and reply to that.

-Bipin Kunal

Comment 21 Bipin Kunal 2017-08-30 09:15:53 UTC
I even see that this bug was earlier marked as dependent on bug #1339765 but it was removed later removed, Any reason for that?

-Bipin Kunal

Note You need to log in before you can comment on or make changes to this bug.