[Bugs] [Bug 1804058] New: [Thin-arbiter] : Wait for connection with TA node before sending lookup/create of ta-replica id file
bugzilla at redhat.com
bugzilla at redhat.com
Tue Feb 18 06:27:01 UTC 2020
https://bugzilla.redhat.com/show_bug.cgi?id=1804058
Bug ID: 1804058
Summary: [Thin-arbiter] : Wait for connection with TA node
before sending lookup/create of ta-replica id file
Product: GlusterFS
Version: 7
Status: NEW
Component: replicate
Assignee: bugs at gluster.org
Reporter: aspandey at redhat.com
CC: bugs at gluster.org, ksubrahm at redhat.com, pasik at iki.fi,
ravishankar at redhat.com
Depends On: 1720463
Target Milestone: ---
Classification: Community
+++ This bug was initially created as a clone of Bug #1720463 +++
Description of problem:
When we mount a ta volume, as soon as 2 data bricks are connected we consider
that the mount is done and then send a lookup/create on ta file on ta node.
However, this connection with ta node might not have been completed.
Due to this delay, ta replica id file will not be created and we will see
ENOTCONN error in log file.
As we know that this ta node could have a higher latency, we should wait for
reasonable time for connection to happen before sending lookup/create on
replica id file.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--- Additional comment from Worker Ant on 2020-01-03 11:31:37 UTC ---
REVIEW: https://review.gluster.org/23959 (cluster/thin-arbiter: Wait for TA
connection before ta-file lookup) posted (#1) for review on master by Ashish
Pandey
--- Additional comment from Worker Ant on 2020-02-18 06:04:50 UTC ---
REVIEW: https://review.gluster.org/23959 (cluster/thin-arbiter: Wait for TA
connection before ta-file lookup) merged (#5) on master by Ashish Pandey
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1720463
[Bug 1720463] [Thin-arbiter] : Wait for connection with TA node before sending
lookup/create of ta-replica id file
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list