Yes. Worked perfectly. No issues. Only thing worth noting, which I knew but had forgotten about, was that I had the option lookup-unhashed off. That meant when I added the new bricks and told it to rebalance a bunch of the files became unavailable until I re-enabled it. Makes sense though because the files wouldn’t be where they were supposed to be while it was working on rebalancing. I took the route of taking the whole cluster down, making the modifications to the vol info on each member, then bringing it all back up.
From: Brandon Mackie Sent: April 21, 2014 1:24 PM To: [email protected] Subject: RE: Upgrade from 3.3 to 3.4.3 now can't add bricks A conversation with myself, but JoeJulian was kind enough to point out that it was the info file and not the vol file that wasn’t matched. Confirmed that new servers have two extra lines: op-version=2 client-op-version=2 Which of course would cause a mismatch. I’ll take down everything tonight and see if that corrects it as it does correct it on some test servers. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Brandon Mackie Sent: April 21, 2014 1:13 PM To: [email protected]<mailto:[email protected]> Subject: Re: [Gluster-users] Upgrade from 3.3 to 3.4.3 now can't add bricks Replace “bricks” with “servers” as IRC just informed me my vocab was crossed. Anyway, I wanted to add that following http://www.gluster.org/community/documentation/index.php/Resolving_Peer_Rejected I can get one brick to see it as not rejected (the brick that I peer on step 4 but the rest still see it as rejected. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Brandon Mackie Sent: April 21, 2014 12:40 PM To: [email protected]<mailto:[email protected]> Subject: [Gluster-users] Upgrade from 3.3 to 3.4.3 now can't add bricks Good afternoon folks, Not sure if this is an occurrence of https://bugzilla.redhat.com/show_bug.cgi?id=1072720 but cannot add new bricks to my existing cluster running under Ubuntu 12. New bricks are completely blank. Peer probed new from a trusted member. Both sides say “Peer Rejected (Connected)” but does not migrate the peer to the other bricks. If I then clear out the newly created /var/lib/glusterd on the new brick and then restart the server then it migrates to all bricks but all say rejected (connected) instead of just one. Confirmed not firewall as I can open a tcp port in both directions. A quick snap of the log on the new brick: http://pastie.org/9098095 I’ve heard this means the vol file doesn’t match but this is a brand new clean server and therefore no vol file.
_______________________________________________ Gluster-users mailing list [email protected] http://supercolony.gluster.org/mailman/listinfo/gluster-users
