Looks like setup issue to me. Copying SSH keys manually is not required.
Command prefix is required while adding to authorized_keys file in each remote
nodes. That will not be available if ssh keys are added manually.
Geo-rep specifies /nonexisting/gsyncd in the command to make sure it
On March 2, 2020 2:33:10 AM GMT+02:00, David Cunningham
wrote:
>Hello,
>
>We've set up geo-replication but it isn't actually syncing. Scenario is
>that we have two GFS clusters. Cluster A has nodes cafs10, cafs20, and
>cafs30, replicating with each other over a LAN. Cluster B has nodes
>nvfs10,
Thanks for the update David!
On Fri, Feb 28, 2020 at 8:21 PM David Spisla wrote:
> Dear Gluster Community,
>
> as mentioned on the last Gluster Community meeting, here is bug report for
> the above issue. The patch is already sent to gerrit:
> https://bugzilla.redhat.com/show_bug.cgi?id=1808421
Hi Rifat,
I suspect you are hitting
https://bugzilla.redhat.com/show_bug.cgi?id=1773856. This bug has been
fixed in master and will be backported to release branches soon.
Although the bug says, "with volume set operation when a node is down we
see the issue", according to the RCA of the bug it
Hello,
We've set up geo-replication but it isn't actually syncing. Scenario is
that we have two GFS clusters. Cluster A has nodes cafs10, cafs20, and
cafs30, replicating with each other over a LAN. Cluster B has nodes nvfs10,
nvfs20, and nvfs30 also replicating with each other over a LAN. We are
Strahil Nikolov wrote on 01/03/2020 07:12:
> On March 1, 2020 2:02:33 AM GMT+02:00, Ronny Adsetts
> wrote:
>>
>> I have a 4-server system running a distributed-replicate setup, 4 x (2
>> + 1) = 12. Bricks are staggered across the servers. Sharding is
>> enabled. (v info shown below)
>>
>> Now,
