<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Alex,<div class=""><br class=""></div><div class="">Thank you for the quick reply! </div><div class=""><br class=""></div><div class="">Yes, I'm aware that using “plain” hardware with replication is more what GlusterFS is for. I cannot talk about prices where in detail, but for me, it evens more or less out. Moreover, I have more SAN that I'd rather re-use (because of Lustre) than buy new hardware. I'll test more to understand what precisely "replace-brick" changes. I understand the mode of operation in case of replicated volumes. But I was surprised (in a good way) that is was also working for distributed volumes, i.e., I was surprised that gluster does not complain of the new brick already contains data. It there some technical documentation of the inner workings of glusterfs? </div><div class=""><br class=""></div><div class="">This leads me to the question: If I wanted to extend my current installation (the one that uses SANs) with more standard hardware: is is possible to mix replicated and non-replicated bricks? (I assume no... but I still dare to ask.) </div><div class=""><br class=""></div><div class="">best wishes,</div><div class="">Stefan</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">Am 11.12.2017 um 23:07 schrieb Alex Chekholko <<a href="mailto:alex@calicolabs.com" class="">alex@calicolabs.com</a>>:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Hi Stefan,</div><div class=""><br class=""></div>I think what you propose will work, though you should test it thoroughly.<div class=""><br class=""></div><div class="">I think more generally, "the GlusterFS way" would be to use 2-way replication instead of a distributed volume; then you can lose one of your servers without outage. And re-synchronize when it comes back up.</div><div class=""><br class=""></div><div class="">Chances are if you weren't using the SAN volumes; you could have purchased two servers each with enough disk to make two copies of the data, all for less dollars...</div><div class=""><br class=""></div><div class="">Regards,</div><div class="">Alex</div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Dec 11, 2017 at 12:52 PM, Stefan Solbrig <span dir="ltr" class=""><<a href="mailto:stefan.solbrig@ur.de" target="_blank" class="">stefan.solbrig@ur.de</a>></span> wrote:<br class=""><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" class="gmail_quote">Dear all,<br class="">
<br class="">
I'm rather new to glusterfs but have some experience running lager lustre and beegfs installations. These filesystems provide active/active failover. Now, I discovered that I can also do this in glusterfs, although I didn't find detailed documentation about it. (I'm using glusterfs 3.10.8)<br class="">
<br class="">
So my question is: can I really use glusterfs to do failover in the way described below, or am I misusing glusterfs? (and potentially corrupting my data?)<br class="">
<br class="">
My setup is: I have two servers (qlogin and gluster2) that access a shared SAN storage. Both servers connect to the same SAN (SAS multipath) and I implement locking via lvm2 and sanlock, so I can mount the same storage on either server.<br class="">
The idea is that normally each server serves one brick, but in case one server fails, the other server can serve both bricks. (I'm not interested on automatic failover, I'll always do this manually. I could also use this to do maintainance on one server, with only minimal downtime.)<br class="">
<br class="">
<br class="">
#normal setup:<br class="">
[root@qlogin ~]# gluster volume info g2<br class="">
#...<br class="">
# Volume Name: g2<br class="">
# Type: Distribute<br class="">
# Brick1: qlogin:/glust/castor/brick<br class="">
# Brick2: gluster2:/glust/pollux/brick<br class="">
<br class="">
# failover: let's artificially fail one server by killing one glusterfsd:<br class="">
[root@qlogin] systemctl status glusterd<br class="">
[root@qlogin] kill -9 <pid/of/glusterfsd/running/<wbr class="">brick/castor><br class="">
<br class="">
# unmount brick<br class="">
[root@qlogin] umount /glust/castor/<br class="">
<br class="">
# deactive LV<br class="">
[root@qlogin] lvchange -a n vgosb06vd05/castor<br class="">
<br class="">
<br class="">
### now do the failover:<br class="">
<br class="">
# active same storage on other server:<br class="">
[root@gluster2] lvchange -a y vgosb06vd05/castor<br class="">
<br class="">
# mount on other server<br class="">
[root@gluster2] mount /dev/mapper/vgosb06vd05-castor /glust/castor<br class="">
<br class="">
# now move the "failed" brick to the other server<br class="">
[root@gluster2] gluster volume replace-brick g2 qlogin:/glust/castor/brick gluster2:/glust/castor/brick commit force<br class="">
### The last line is the one I have doubts about<br class="">
<br class="">
#now I'm in failover state:<br class="">
#Both bricks on one server:<br class="">
[root@qlogin ~]# gluster volume info g2<br class="">
#...<br class="">
# Volume Name: g2<br class="">
# Type: Distribute<br class="">
# Brick1: gluster2:/glust/castor/brick<br class="">
# Brick2: gluster2:/glust/pollux/brick<br class="">
<br class="">
<br class="">
Is it intended to work this way?<br class="">
<br class="">
Thanks a lot!<br class="">
<br class="">
best wishes,<br class="">
Stefan<br class="">
<br class="">
______________________________<wbr class="">_________________<br class="">
Gluster-users mailing list<br class="">
<a href="mailto:Gluster-users@gluster.org" class="">Gluster-users@gluster.org</a><br class="">
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank" class="">http://lists.gluster.org/<wbr class="">mailman/listinfo/gluster-users</a><br class="">
</blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></body></html>