Bug 1662264 - thin-arbiter: Check with thin-arbiter file before marking new entry change log
Summary: thin-arbiter: Check with thin-arbiter file before marking new entry change log
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ashish Pandey
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1672314
TreeView+ depends on / blocked
 
Reported: 2018-12-27 09:08 UTC by Ashish Pandey
Modified: 2019-03-25 16:32 UTC (History)
1 user (show)

Fixed In Version: glusterfs-6.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1672314 (view as bug list)
Environment:
Last Closed: 2019-03-25 16:32:53 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 21933 0 None Open cluster/thin-arbiter: Consider thin-arbiter before marking new entry changelog 2019-02-01 05:45:30 UTC

Description Ashish Pandey 2018-12-27 09:08:23 UTC
Description of problem:

In case of creating an entry, if a fop fails on any one of the data bricks,
we mark the changelog on that entry on the brick which was successful.

For thin arbiter volume before marking this changelog, we should check if the brick on which fop succeeded was the good brick or not. If the bricks was bad according to thin-arbiter file information, we should just continue with postop  
changelog process. If the brick was good, we should mark the new entry changelog and continuew with postop changelog.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-12-27 09:19:25 UTC
REVIEW: https://review.gluster.org/21933 (cluster/thin-arbiter: Consider thin-arbiter before marking new entry changelog) posted (#1) for review on master by Ashish Pandey

Comment 2 Worker Ant 2019-02-01 05:45:32 UTC
REVIEW: https://review.gluster.org/21933 (cluster/thin-arbiter: Consider thin-arbiter before marking new entry changelog) merged (#6) on master by Amar Tumballi

Comment 3 Worker Ant 2019-02-06 06:36:58 UTC
REVIEW: https://review.gluster.org/22161 (cluster/thin-arbiter: Consider thin-arbiter before marking new entry changelog) posted (#1) for review on release-5 by Ashish Pandey

Comment 4 Shyamsundar 2019-03-25 16:32:53 UTC
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-6.0, please open a new bug report.

glusterfs-6.0 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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/


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