Hi Alex,
Did you setup LACP using links to both switches ?
Best Regards,
Strahil Nikolov
On Mar 22, 2019 18:42, Alex K <rightkicktech@xxxxxxxxx> wrote:
Hi all,I had the opportunity to test the setup on actual hardware, as I managed to arrange for a downtime at customer.The results were that, when cables were split between two switches, even though servers were able to ping each other, gluster was not able to start the volumes and the only relevant log I noticed was:[2019-03-21 14:16:15.043714] E [MSGID: 106153] [glusterd-syncop.c:113:gd_collate_errors] 0-glusterd: Staging failed on gluster2. Please check log file for details.
[2019-03-21 14:16:15.044034] E [MSGID: 106153] [glusterd-syncop.c:113:gd_collate_errors] 0-glusterd: Staging failed on gluster2. Please check log file for details.
[2019-03-21 14:16:15.044292] E [MSGID: 106153] [glusterd-syncop.c:113:gd_collate_errors] 0-glusterd: Staging failed on gluster2. Please check log file for details.
[2019-03-21 14:49:11.278724] E [MSGID: 106153] [glusterd-syncop.c:113:gd_collate_errors] 0-glusterd: Staging failed on gluster2. Please check log file for details.
[2019-03-21 14:49:40.904596] E [MSGID: 106153] [glusterd-syncop.c:113:gd_collate_errors] 0-glusterd: Staging failed on gluster1. Please check log file for details.Does anyone has any idea what does this staging error mean?I don't have the hardware anymore available for testing and I will try to reproduce on virtual env.ThanxAlexOn Mon, Mar 18, 2019 at 12:52 PM Alex K <rightkicktech@gmail.com> wrote:Performed some tests simulating the setup on OVS.When using mode 6 I had mixed results for both scenarios (see below):There were times that hosts were not able to reach each other (simple ping tests) and other time where hosts were able to reach each other with ping but gluster volumes were down due to connectivity issues being reported (endpoint is not connected). systemctl restart network usually resolved the gluster connectivity issue. This was regardless of the scenario (interlink or not). I will need to do some more tests.On Tue, Feb 26, 2019 at 4:14 PM Alex K <rightkicktech@gmail.com> wrote:Thank you to all for your suggestions.I came here since only gluster was having issues to start. Ping and other networking services were showing everything fine, so I guess there is sth at gluster that does not like what I tried to do.Unfortunately I have this system in production and I cannot experiment. It was a customer request to add redundancy to the switch and I went with what I assumed would work.I guess I have to have the switches stacked, but the current ones do not support this. They are just simple managed switches.Multiple IPs per peers could be a solution.I will search a little more and in case I have sth I will get back.On Tue, Feb 26, 2019 at 6:52 AM Strahil <hunter86_bg@yahoo.com> wrote:Hi Alex,
As per the following ( ttps://community.cisco.com/t5/switching/lacp-load-balancing-in-2-switches-part-of-3750-stack-switch/td-p/2268111 ) your switches need to be stacked in order to support lacp with your setup.
Yet, I'm not sure if balance-alb will work with 2 separate switches - maybe some special configuration is needed ?!?
As far as I know gluster can have multiple IPs matched to a single peer, but I'm not sure if having 2 separate networks will be used as active-backup or active-active.
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
