Bug 1655861 - Avoid sending duplicate pmap signout
Summary: Avoid sending duplicate pmap signout
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Sanju
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-04 06:19 UTC by Atin Mukherjee
Modified: 2020-03-17 03:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-17 03:27:15 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 21792 0 None Abandoned glusterfsd: avoid sending duplicate pmap signout 2019-03-04 19:30:29 UTC

Description Atin Mukherjee 2018-12-04 06:19:46 UTC 
Description of problem:

Based on brick multiplexing feature testing in GD2, it was identified that brick is initiating duplicate pmap_signout event. One from glusterfs_handle_terminate and other from server_notify/server_rpc_notify.

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-04 06:27:07 UTC 
REVIEW: https://review.gluster.org/21792 (glusterfsd: avoid sending duplicate pmap signout) posted (#1) for review on master by Atin Mukherjee
Comment 2 Amar Tumballi 2019-05-18 06:33:03 UTC 
patch abandoned.
Comment 3 Worker Ant 2020-03-17 03:27:15 UTC 
This bug is moved to https://github.com/gluster/glusterfs/issues/1108, and will be tracked there from now on. Visit GitHub issues URL for further details
Note You need to log in before you can comment on or make changes to this bug.