Hi,
Yeah shared storage is needed only for more than 2 nodes to sync the geo rep
status.
If I have some time , I can try to reproduce it if you could provide the gluster
version, operating system and volume options.
Best Regards,
Strahil Nikolov
On Mon, Aug 19, 2024 at 4:45, Karl Kleinpaste<karl at kleinpaste.org>
wrote: On 8/18/24 16:41, Strahil Nikolov wrote:
I don't see anything mentioning shared storage in the docs and I assume
it's now automatic but can you check 'gluster volume get all
cluster.enable-shared-storage' ? I would give a try with RH's
documentation despite it's old it has some steps (like the shared volume)
that might be needed
I appreciate the reply. For the first item:
Option?????????????????????????????????? Value????????????????????????????????
?
------?????????????????????????????????? -----????????????????????????????????
?
cluster.enable-shared-storage??????????? disable (DEFAULT)
I tried turning this on, but apparently it's inapplicable for my test
configuration of 1-brick volumes.
gluster volume set j cluster.enable-shared-storage on
volume set: failed: Not a valid option for single volume
I looked through that documentation. It comes down to the same geo-rep create
command, with the same result.
In any event, I re-ran
gluster-georep-sshkey generate
on both nodes, which worked fine. Then, just as before
gluster volume geo-replication j geoacct at pms::n create ssh-port 6247
push-pem
Please check gsync config file. Unable to get statefile's name
geo-replication command failed
I don't yet see what else I could be doing with this.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20240822/a55557b5/attachment.html>