diff options
author | Ashish Pandey <aspandey@redhat.com> | 2020-01-03 16:54:33 +0530 |
---|---|---|
committer | Ashish Pandey <aspandey@redhat.com> | 2020-02-18 12:19:31 +0530 |
commit | fc0f7442f038ce86344dd6b735abcff6a50533b8 (patch) | |
tree | 0212f516cf1a3f8b6ae659e0e6d0e67b2e5be42d /libglusterfs/src/glusterfs | |
parent | 1d59dc3b37df2c5f960e0620c7e8c36760ff96c8 (diff) | |
download | glusterfs-fc0f7442f038ce86344dd6b735abcff6a50533b8.tar.gz glusterfs-fc0f7442f038ce86344dd6b735abcff6a50533b8.tar.xz glusterfs-fc0f7442f038ce86344dd6b735abcff6a50533b8.zip |
cluster/thin-arbiter: Wait for TA connection before ta-file lookup
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 if we do lookup.
Solution:
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.
fixes: bz#1804058
Change-Id: I36f90865afe617e4e84cee57fec832a16f5dd6cc
(cherry picked from commit a7fa54ddea3fe429f143b37e4de06a93b49d776a)
Diffstat (limited to 'libglusterfs/src/glusterfs')
0 files changed, 0 insertions, 0 deletions