gluster volume get
New in 3.7
Also
gluster volume set help
shows you the defaults.
On October 10, 2015 7:10:38 AM PDT, Lindsay Mathieson <lindsay.mathieson at
gmail.com> wrote:>On 30 September 2015 at 18:36, Tiemen Ruiten <t.ruiten at rdmedia.com>
>wrote:
>
>> From personal experience: A two node volume can get you into trouble
>when
>> one of the nodes goes down unexpectedly/crashes. At the very least,
>you
>> should have an arbiter volume (introduced in Gluster 3.7) on a
>separate
>> physical node.
>>
>
>I've introduced a third node for full replica 3 now. Surprised and
>pleased
>that there is no real performance drop.
>
>This is where the docs get a bit frustrating :(
>https://gluster.readthedocs.org/en/release-3.7.0/Features/server-quorum/
>discusses server quorum and the settings, but doesn't say what the
>default
>values are, and there is no way of reading volume settings in gluster.
>
>
>
>
>--
>Lindsay
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Gluster-users mailing list
>Gluster-users at gluster.org
>http://www.gluster.org/mailman/listinfo/gluster-users
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20151010/f41c4431/attachment.html>
Mauro M.
2015-Oct-10 16:05 UTC
[Gluster-users] Significant issues after update to 3.7.5 (Centos 6.7)
Hello, Today I received the update to 3.7.5 and since the update I began to have serious issues. My cluster has two bricks with replication. With both bricks up I could not start the volume that was stopped soon after the update. By taking one of the nodes down I managed finally to start the volume, but ... with the following error: [2015-10-10 09:40:59.600974] E [MSGID: 106123] [glusterd-syncop.c:1404:gd_commit_op_phase] 0-management: Commit of operation 'Volume Start' failed on localhost At which point clients could mount the filesystem, however with: # gluster volume status it showed the volume as stopped. If I stopped and started again the volume same problem, but, if I issued again a "volume start myvolume" at this point it would show as started! With both bricks up and running instead there is no way to start the volume once stopped. Only if I take one of the bricks down then I can start it with the procedure above. I am downgrading to 3.7.4. If you have not yet upgraded, BEWARE!
On 11 October 2015 at 00:46, Joe Julian <joe at julianfamily.org> wrote:> gluster volume get > > New in 3.7 >Thanks Joe, but stuck with 3.6 for now - Debian Wheezy> > Also > gluster volume set help > shows you the defaults. >But this will tide me over, thanks! -- Lindsay -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151011/48693a44/attachment.html>