Bug 1800583 - Halo replication is not working
Summary: Halo replication is not working
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-07 13:23 UTC by Pranith Kumar K
Modified: 2020-03-13 13:21 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-12 13:26:19 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 24100 0 None Merged cluster/afr: Fixes for halo 2020-03-13 13:21:14 UTC

Description Pranith Kumar K 2020-02-07 13:23:51 UTC
Description of problem:

    Current implementation assumes that ping-event will come after connect event
    but that may not be the case in the cases where after socket connection fds
    need to be re-opened which would consume more time. So handle any order of the
    ping/child-up events.

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 2020-02-07 13:26:16 UTC
REVIEW: https://review.gluster.org/24100 (cluster/afr: Fixes for halo) posted (#1) for review on master by Pranith Kumar Karampuri

Comment 2 Worker Ant 2020-03-12 13:26:19 UTC
This bug is moved to https://github.com/gluster/glusterfs/issues/1017, and will be tracked there from now on. Visit GitHub issues URL for further details

Comment 3 Worker Ant 2020-03-13 13:21:16 UTC
REVIEW: https://review.gluster.org/24100 (cluster/afr: Fixes for halo) merged (#4) on master by Pranith Kumar Karampuri


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