+++ 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
REVIEW: https://review.gluster.org/24129 (cluster/thin-arbiter: Wait for TA connection before ta-file lookup) posted (#1) for review on release-7 by Ashish Pandey
REVIEW: https://review.gluster.org/24129 (cluster/thin-arbiter: Wait for TA connection before ta-file lookup) merged (#2) on release-7 by Ashish Pandey