<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 07/03/2017 06:58 PM, knarra wrote:<br>
    </div>
    <blockquote
      cite="mid:12869870-7d3a-1b80-4199-d336dfb8570c@redhat.com"
      type="cite">
      <meta content="text/html; charset=windows-1252"
        http-equiv="Content-Type">
      <div class="moz-cite-prefix">On 07/03/2017 06:53 PM, yayo (j)
        wrote:<br>
      </div>
      <blockquote
cite="mid:CAGK=3kwU7VbyQjLyvG5TS0LtozOkBpGidOsBYeoyp_eOapTB6g@mail.gmail.com"
        type="cite">
        <div dir="ltr">
          <div class="gmail_extra">Hi,</div>
          <div class="gmail_extra"><br>
          </div>
          <div class="gmail_extra">And sorry for delay</div>
          <div class="gmail_extra"><br>
            <div class="gmail_quote">2017-06-30 14:09 GMT+02:00 knarra <span
                dir="ltr">&lt;<a moz-do-not-send="true"
                  href="mailto:knarra@redhat.com" target="_blank">knarra@redhat.com</a>&gt;</span>:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div bgcolor="#FFFFFF" text="#000000">To <span
                    class="il">add</span> a fully replicated <span
                    class="il">node</span>  you need to reduce the
                  replica count to 2 and <span class="il">add</span>
                  new brick to the volume so that it becomes replica 3.
                  Reducing replica count by removing a brick from
                  replica / arbiter cannot be done from UI currently and
                  this has to be done using <span class="il">gluster</span>
                  CLI. <br>
                   AFAIR, there was an issue where vm's were going to
                  paused state when reducing the replica count and
                  increasing it to 3. Not sure if this still holds good
                  with the latest release. <br>
                  <br>
                  Any specific reason why you want to move to <span
                    class="il">full</span> replication instead of using
                  an arbiter <span class="il">node</span> ?<span
                    class=""><br>
                    <br>
                  </span></div>
              </blockquote>
              <div><br>
              </div>
              <div>We have a new server with the same hard disk size of
                other two node, so, why not? Why join the cluster as an
                arbiter when we can have the same disk capacity to add
                extra replication? </div>
              <div><br>
              </div>
              <div> </div>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div bgcolor="#FFFFFF" text="#000000"><span class=""> <br>
                    <blockquote type="cite">
                      <div dir="ltr">
                        <div class="gmail_extra">
                          <div class="gmail_extra">and remove the
                            arbiter <span class="il">node</span> (Also
                            a way to move the arbiter role to the new <span
                              class="il">node</span>, If needed) </div>
                        </div>
                      </div>
                    </blockquote>
                  </span> To move arbiter role to a new <span
                    class="il">node</span> you can move the <span
                    class="il">node</span> to maintenance , <span
                    class="il">add</span>  new <span class="il">node</span>
                  and replace  old brick with new brick. You can follow
                  the steps below to do that.<br>
                  <br>
                  <ul>
                    <li>Move the <span class="il">node</span> to be
                      replaced into Maintenance mode</li>
                    <li>Prepare the replacement <span class="il">node</span></li>
                    <li>Prepare bricks on that <span class="il">node</span>.</li>
                    <li>Create replacement brick directories</li>
                    <li>Ensure the new directories are owned by the vdsm
                      user and the kvm group.</li>
                    <li># mkdir /rhgs/bricks/engine</li>
                    <li># chmod vdsm:kvm /rhgs/bricks/engine</li>
                    <li># mkdir /rhgs/bricks/data</li>
                    <li># chmod vdsm:kvm /rhgs/bricks/data</li>
                    <li>Run the following command from one of the
                      healthy cluster members:</li>
                    <li># <span class="il">gluster</span> peer probe
                      &lt;new_node&gt;</li>
                    <li> <span class="il">add</span> the new host to the
                      cluster.</li>
                    <li><span class="il">Add</span> new host address to
                      <span class="il">gluster</span> network</li>
                    <li>Click Network Interfaces sub-tab.</li>
                    <li>Click Set up Host Networks.</li>
                    <li>Drag and drop the glusternw network onto the IP
                      address of the new host.</li>
                    <li>Click OK</li>
                    <li>Replace the old brick with the brick on the new
                      host</li>
                    <li>Click the Bricks sub-tab.</li>
                    <li>Verify that brick heal completes successfully.</li>
                    <li>In the Hosts tab, right-click on the old host
                      and click Remove.</li>
                    <li>Clean old host metadata</li>
                    <li># hosted-engine --clean-metadata
                      --host-id=&lt;old_host_id&gt; --force-clean</li>
                  </ul>
                  <span class=""> <br>
                  </span></div>
              </blockquote>
              <div><br>
              </div>
              <div>I need this (reads: I need the arbiter role) if I
                reduce replica count then I add the new node as full
                replica and increasing replica count again to 3? (As you
                expained above)</div>
              <div><br>
              </div>
            </div>
          </div>
        </div>
      </blockquote>
      Above steps hold good if you want to move the arbiter role to a
      new node.<br>
      <br>
      If you want to move to full replica, reducing the replica count
      will work fine but increasing it again back to 3 might cause vm
      pause issues.<br>
    </blockquote>
    So, please poweroff your vms while performing this.<br>
    <blockquote
      cite="mid:12869870-7d3a-1b80-4199-d336dfb8570c@redhat.com"
      type="cite"> <br>
      <br>
      <br>
      <br>
      <blockquote
cite="mid:CAGK=3kwU7VbyQjLyvG5TS0LtozOkBpGidOsBYeoyp_eOapTB6g@mail.gmail.com"
        type="cite">
        <div dir="ltr">
          <div class="gmail_extra">
            <div class="gmail_quote">
              <div>Thank you</div>
            </div>
          </div>
        </div>
      </blockquote>
      <p><br>
      </p>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>