1:33 p.m.
--_000_BFAB40933B3367488CE6299BAF8592D1014E52CC4354SOCRATESasl_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi All,
my oVirt-Setup is 3 Hosts with gluster and reaplica 3. I always try to stay=
on the current version and I'm applying updates/upgrade if there are any. =
For this I put a host in maintenance and also use the "Stop Gluster Service=
" checkbox. After it's done updating I'll set it back to active and wait u=
ntil the engine sees all bricks again and then I'll go for the next host.
This worked fine for me the last month and now that I have more and more VM=
s running the changes that are written to the gluster volume while a host i=
s in maintenance become a lot more and it takes pretty long for the healing=
to complete. What I don't understand is that I don't really see a lot of n=
etwork usage in the GUI during that time and it feels quiet slow. The Netwo=
rk for the gluster is a 10G and I'm quiet happy with the performance of it,=
it's just the healing that takes long. I noticed that because I couldn't u=
pdate the third host because of unsynced gluster volumes.
Is there any limiting variable that slows down traffic during healing that =
needs to be configured ? Or should I maybe change my updating process someh=
ow to avoid having so many changes in queue?
Thank you,
Sven
--_000_BFAB40933B3367488CE6299BAF8592D1014E52CC4354SOCRATESasl_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word"
=
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"
xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META
HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator
content=3D"Micros=
oft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DDE
link=3D"#0563C1" v=
link=3D"#954F72"><div class=3DWordSection1><p
class=3DMsoNormal>Hi All, <o:=
p></o:p></p><p
class=3DMsoNormal><o:p> </o:p></p><p
class=3DMsoNormal>=
<span lang=3DEN-US>my oVirt-Setup is 3 Hosts with gluster and reaplica 3. I=
always try to stay on the current version and I’m applying updates/u=
pgrade if there are any. For this I put a host in maintenance and also use =
the “Stop Gluster Service” checkbox. After it’s
don=
e updating I’ll set it back to active and wait until the engine sees =
all bricks again and then I’ll go for the next host.
<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span
lang=3DEN-US><o:p> </o:p></span></p><=
p class=3DMsoNormal><span lang=3DEN-US>This worked fine for me the last mon=
th and now that I have more and more VMs running the changes that are writt=
en to the gluster volume while a host is in maintenance become a lot more a=
nd it takes pretty long for the healing to complete. What I don’t und=
erstand is that I don’t really see a lot of network usage in the GUI =
during that time and it feels quiet slow. The Network for the gluster is a =
10G and I’m quiet happy with the performance of it, it’s just t=
he healing that takes long. I noticed that because I couldn’t update =
the third host because of unsynced gluster
volumes.<o:p></o:p></span></p><p=
class=3DMsoNormal><span
lang=3DEN-US><o:p> </o:p></span></p><p class=
=3DMsoNormal><span lang=3DEN-US>Is there any limiting variable that slows d=
own traffic during healing that needs to be configured ? Or should I maybe =
change my updating process somehow to avoid having so many changes in queue=
? <o:p></o:p></span></p><p class=3DMsoNormal><span
lang=3DEN-US><o:p> =
</o:p></span></p><p class=3DMsoNormal><span
lang=3DEN-US>Thank you, <o:p></=
o:p></span></p><p class=3DMsoNormal><span
lang=3DEN-US><o:p> </o:p></s=
pan></p><p class=3DMsoNormal><span
lang=3DEN-US>Sven<o:p></o:p></span></p><=
p
class=3DMsoNormal><o:p> </o:p></p></div></body></html>=
--_000_BFAB40933B3367488CE6299BAF8592D1014E52CC4354SOCRATESasl_--
1:44 p.m.
This is a multi-part message in MIME format.
--------------941CA42C94052919F4693A27
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
On 04/24/2017 05:03 PM, Sven Achtelik wrote:
Hi All,
my oVirt-Setup is 3 Hosts with gluster and reaplica 3. I always try to
stay on the current version and Im applying updates/upgrade if there
are any. For this I put a host in maintenance and also use the Stop
Gluster Service checkbox. After its done updating Ill set it back
to active and wait until the engine sees all bricks again and then
Ill go for the next host.
This worked fine for me the last month and now that I have more and
more VMs running the changes that are written to the gluster volume
while a host is in maintenance become a lot more and it takes pretty
long for the healing to complete. What I dont understand is that I
dont really see a lot of network usage in the GUI during that time
and it feels quiet slow. The Network for the gluster is a 10G and Im
quiet happy with the performance of it, its just the healing that
takes long. I noticed that because I couldnt update the third host
because of unsynced gluster volumes.
Is there any limiting variable that slows down traffic during healing
that needs to be configured ? Or should I maybe change my updating
process somehow to avoid having so many changes in queue?
Thank you,
Sven
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Hi Sven,
Do you have granular entry heal enabled on the volume? If no, there
is a feature called granular entry self-heal which should be enabled
with sharded volumes to get the benefits. So when a brick goes down and
say only 1 in those million entries is created/deleted. Self-heal would
be done for only that file it won't crawl the entire directory.
You can run|gluster volume set/VOLNAME/cluster.granular-entry-heal
enable / disable|command only if the volume is in|Created|state. If the
volume is in any other state other than|Created|, for
example,|Started|,|Stopped|, and so on, execute|gluster volume heal
VOLNAME granular-entry-heal|enable / disable||command to enable or
disable granular-entry-heal option.
Thanks
kasturi
--------------941CA42C94052919F4693A27
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<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 04/24/2017 05:03 PM, Sven Achtelik
wrote:<br>
</div>
<blockquote
cite="mid:BFAB40933B3367488CE6299BAF8592D1014E52CC4354@SOCRATES.asl.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi All, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">my
oVirt-Setup is 3
Hosts with gluster and reaplica 3. I always try to stay on
the current version and Im applying updates/upgrade if
there are any. For this I put a host in maintenance and also
use the Stop Gluster Service checkbox. After its done
updating Ill set it back to active and wait until the
engine sees all bricks again and then Ill go for the next
host. <o:p></o:p></span></p>
<p class="MsoNormal"><span
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">This
worked fine for me
the last month and now that I have more and more VMs running
the changes that are written to the gluster volume while a
host is in maintenance become a lot more and it takes pretty
long for the healing to complete. What I dont understand is
that I dont really see a lot of network usage in the GUI
during that time and it feels quiet slow. The Network for
the gluster is a 10G and Im quiet happy with the
performance of it, its just the healing that takes long. I
noticed that because I couldnt update the third host
because of unsynced gluster
volumes.<o:p></o:p></span></p>
<p class="MsoNormal"><span
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Is there
any limiting
variable that slows down traffic during healing that needs
to be configured ? Or should I maybe change my updating
process somehow to avoid having so many changes in queue?
<o:p></o:p></span></p>
<p class="MsoNormal"><span
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thank you,
<o:p></o:p></span></p>
<p class="MsoNormal"><span
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
lang="EN-US">Sven<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<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://...
</pre>
</blockquote>
<p>Hi Sven,</p>
<p> Do you have granular entry heal enabled on the volume? If no,
there is a feature called granular entry self-heal which should be
enabled with sharded volumes to get the benefits. So when a brick
goes down and say only 1 in those million entries is
created/deleted. Self-heal would be done for only that file it
won't crawl the entire directory.</p>
<p>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<span style="color: rgb(51, 51, 51); font-size: 16px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; word-spacing: 0px; background-color: rgb(255, 255, 255);
display: inline ! important; float: none;">You can run<span
class="Apple-converted-space"> </span></span><code
class="command" style="box-sizing: border-box; font-size:
14.4px; padding: 2px 4px; color: rgb(51, 51, 51);
background-color: rgb(255, 255, 255); border-radius: 0px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal; letter-spacing:
normal; text-align: left; text-indent: 0px; text-transform:
none; white-space: normal; word-spacing: 0px;">gluster volume
set<span class="Apple-converted-space"> </span><em
class="replaceable" style="box-sizing:
border-box;">VOLNAME</em><span
class="Apple-converted-space"> </span>cluster.granular-entry-heal
enable / disable<span
class="Apple-converted-space"> </span></code><span
style="color: rgb(51, 51, 51); font-size: 16px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; word-spacing: 0px; background-color: rgb(255, 255, 255);
display: inline ! important; float: none;">command only if the
volume is in<span
class="Apple-converted-space"> </span></span><code
class="literal" style="box-sizing: border-box; font-size:
14.4px; padding: 2px 4px; color: rgb(51, 51, 51);
background-color: rgb(255, 255, 255); border-radius: 0px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal; letter-spacing:
normal; text-align: left; text-indent: 0px; text-transform:
none; white-space: normal; word-spacing: 0px;">Created<span
class="Apple-converted-space"> </span></code><span
style="color: rgb(51, 51, 51); font-size: 16px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; word-spacing: 0px; background-color: rgb(255, 255, 255);
display: inline ! important; float: none;">state. If the volume
is in any other state other than<span
class="Apple-converted-space"> </span></span><code
class="literal" style="box-sizing: border-box; font-size:
14.4px; padding: 2px 4px; color: rgb(51, 51, 51);
background-color: rgb(255, 255, 255); border-radius: 0px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal; letter-spacing:
normal; text-align: left; text-indent: 0px; text-transform:
none; white-space: normal; word-spacing: 0px;">Created<span
class="Apple-converted-space"> </span></code><span
style="color: rgb(51, 51, 51); font-size: 16px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; word-spacing: 0px; background-color: rgb(255, 255, 255);
display: inline ! important; float: none;">, for example,<span
class="Apple-converted-space"> </span></span><code
class="literal" style="box-sizing: border-box; font-size:
14.4px; padding: 2px 4px; color: rgb(51, 51, 51);
background-color: rgb(255, 255, 255); border-radius: 0px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal; letter-spacing:
normal; text-align: left; text-indent: 0px; text-transform:
none; white-space: normal; word-spacing: 0px;">Started<span
class="Apple-converted-space"> </span></code><span
style="color: rgb(51, 51, 51); font-size: 16px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; word-spacing: 0px; background-color: rgb(255, 255, 255);
display: inline ! important; float: none;">,<span
class="Apple-converted-space"> </span></span><code
class="literal" style="box-sizing: border-box; font-size:
14.4px; padding: 2px 4px; color: rgb(51, 51, 51);
background-color: rgb(255, 255, 255); border-radius: 0px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal; letter-spacing:
normal; text-align: left; text-indent: 0px; text-transform:
none; white-space: normal; word-spacing:
0px;">Stopped</code><span
style="color: rgb(51, 51, 51); font-size: 16px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; word-spacing: 0px; background-color: rgb(255, 255, 255);
display: inline ! important; float: none;">, and so on, execute<span
class="Apple-converted-space"> </span></span><code
class="command" style="box-sizing: border-box; font-size:
14.4px; padding: 2px 4px; color: rgb(51, 51, 51);
background-color: rgb(255, 255, 255); border-radius: 0px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal; letter-spacing:
normal; text-align: left; text-indent: 0px; text-transform:
none; white-space: normal; word-spacing: 0px;">gluster volume
heal VOLNAME granular-entry-heal<span
class="Apple-converted-space"> </span><code
class="option"
style="box-sizing: border-box; font-size: 12.96px; padding:
2px 4px; color: inherit; background-color: transparent;
border-radius: 0px;">enable / disable</code></code><span
style="color: rgb(51, 51, 51); font-size: 16px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal; text-align:
left; text-indent: 0px; text-transform: none; white-space:
normal; word-spacing: 0px; background-color: rgb(255, 255, 255);
display: inline ! important; float: none;"><span
class="Apple-converted-space"> </span>command to enable or
disable granular-entry-heal option.</span></p>
<p>Thanks</p>
<p>kasturi<br>
</p>
</body>
</html>
--------------941CA42C94052919F4693A27--
2:06 p.m.
--_000_BFAB40933B3367488CE6299BAF8592D1014E52CC4356SOCRATESasl_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi Kasturi,
I'll try that. Will this be persistent over a reboot of a host or even stop=
ping of the complete cluster ?
Thank you
Von: knarra [mailto:knarra@redhat.com]
Gesendet: Montag, 24. April 2017 13:44
An: Sven Achtelik <Sven.Achtelik(a)eps.aero>; users(a)ovirt.org
Betreff: Re: [ovirt-users] Hyperconverged Setup and Gluster healing
On 04/24/2017 05:03 PM, Sven Achtelik wrote:
Hi All,
my oVirt-Setup is 3 Hosts with gluster and reaplica 3. I always try to stay=
on the current version and I'm applying updates/upgrade if there are any. =
For this I put a host in maintenance and also use the "Stop Gluster Service=
" checkbox. After it's done updating I'll set it back to active and wait u=
ntil the engine sees all bricks again and then I'll go for the next host.
This worked fine for me the last month and now that I have more and more VM=
s running the changes that are written to the gluster volume while a host i=
s in maintenance become a lot more and it takes pretty long for the healing=
to complete. What I don't understand is that I don't really see a lot of n=
etwork usage in the GUI during that time and it feels quiet slow. The Netwo=
rk for the gluster is a 10G and I'm quiet happy with the performance of it,=
it's just the healing that takes long. I noticed that because I couldn't u=
pdate the third host because of unsynced gluster volumes.
Is there any limiting variable that slows down traffic during healing that =
needs to be configured ? Or should I maybe change my updating process someh=
ow to avoid having so many changes in queue?
Thank you,
Sven
_______________________________________________
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
Hi Sven,
Do you have granular entry heal enabled on the volume? If no, there is =
a feature called granular entry self-heal which should be enabled with shar=
ded volumes to get the benefits. So when a brick goes down and say only 1 i=
n those million entries is created/deleted. Self-heal would be done for onl=
y that file it won't crawl the entire directory.
You can run gluster volume set VOLNAME cluster.granular-entry-heal enab=
le / disable command only if the volume is in Created state. If the volume =
is in any other state other than Created , for example, Started , Stopped, =
and so on, execute gluster volume heal VOLNAME granular-entry-heal enable /=
disable command to enable or disable granular-entry-heal option.
Thanks
kasturi
--_000_BFAB40933B3367488CE6299BAF8592D1014E52CC4356SOCRATESasl_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word"
=
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"
xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type
content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator
content=3D"Micros=
oft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
code
{mso-style-priority:99;
font-family:"Courier New";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Vorformatiert Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLVorformatiertZchn
{mso-style-name:"HTML Vorformatiert Zchn";
mso-style-priority:99;
mso-style-link:"HTML Vorformatiert";
font-family:Consolas;
color:black;
mso-fareast-language:EN-US;}
span.E-MailFormatvorlage21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.E-MailFormatvorlage23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite
lang=3DDE li=
nk=3D"#0563C1" vlink=3D"#954F72"><div
class=3DWordSection1><p class=3DMsoNo=
rmal><span style=3D'color:#1F497D'>Hi
Kasturi,<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span
style=3D'color:#1F497D'><o:p> </o:p></span></p><p
=
class=3DMsoNormal><span lang=3DEN-US
style=3D'color:#1F497D'>I’ll try=
that. Will this be persistent over a reboot of a host or even stopping of =
the complete cluster ? <o:p></o:p></span></p><p
class=3DMsoNormal><a name=
=3D"_MailEndCompose"></a><span lang=3DEN-US
style=3D'color:#1F497D'><o:p>&n=
bsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US
style=3D'color=
:#1F497D'><o:p> </o:p></span></p><p
class=3DMsoNormal><span lang=3DEN-=
US style=3D'color:#1F497D'>Thank
you<o:p></o:p></span></p><div><div style=
=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm
0cm'><=
p class=3DMsoNormal><b><span
style=3D'color:windowtext;mso-fareast-language=
:DE'>Von:</span></b><span
style=3D'color:windowtext;mso-fareast-language:DE=
'> knarra [mailto:knarra@redhat.com] <br><b>Gesendet:</b> Montag,
24. April=
2017 13:44<br><b>An:</b> Sven Achtelik
&lt;Sven.Achtelik(a)eps.aero&gt;; use=
rs@ovirt.org<br><b>Betreff:</b> Re: [ovirt-users] Hyperconverged Setup
and =
Gluster healing<o:p></o:p></span></p></div></div><p
class=3DMsoNormal><o:p>=
</o:p></p><div><p class=3DMsoNormal>On 04/24/2017 05:03
PM, Sven Acht=
elik wrote:<span
style=3D'font-size:12.0pt;mso-fareast-language:DE'><o:p></=
o:p></span></p></div><blockquote
style=3D'margin-top:5.0pt;margin-bottom:5.=
0pt'><p class=3DMsoNormal>Hi All, <o:p></o:p></p><p
class=3DMsoNormal> =
;<o:p></o:p></p><p class=3DMsoNormal><span lang=3DEN-US>my
oVirt-Setup is 3=
Hosts with gluster and reaplica 3. I always try to stay on the current ver=
sion and I’m applying updates/upgrade if there are any. For this I pu=
t a host in maintenance and also use the “Stop Gluster Service”=
checkbox. After it’s done updating I’ll set it back to a=
ctive and wait until the engine sees all bricks again and then I’ll g=
o for the next host. </span><o:p></o:p></p><p
class=3DMsoNormal><span lang=
=3DEN-US> </span><o:p></o:p></p><p
class=3DMsoNormal><span lang=3DEN-U=
S>This worked fine for me the last month and now that I have more and more =
VMs running the changes that are written to the gluster volume while a host=
is in maintenance become a lot more and it takes pretty long for the heali=
ng to complete. What I don’t understand is that I don’t really =
see a lot of network usage in the GUI during that time and it feels quiet s=
low. The Network for the gluster is a 10G and I’m quiet happy with th=
e performance of it, it’s just the healing that takes long. I noticed=
that because I couldn’t update the third host because of unsynced gl=
uster volumes.</span><o:p></o:p></p><p
class=3DMsoNormal><span lang=3DEN-US=
</span><o:p></o:p></p><p
class=3DMsoNormal><span lang=3DEN-US>Is the=
re any limiting variable that
slows down traffic during healing that needs =
to be configured ? Or should I maybe change my updating process somehow to =
avoid having so many changes in queue? </span><o:p></o:p></p><p
class=3DMso=
Normal><span
lang=3DEN-US> </span><o:p></o:p></p><p
class=3DMsoNormal>=
<span lang=3DEN-US>Thank you, </span><o:p></o:p></p><p
class=3DMsoNormal><s=
pan lang=3DEN-US> </span><o:p></o:p></p><p
class=3DMsoNormal><span lan=
g=3DEN-US>Sven</span><o:p></o:p></p><p
class=3DMsoNormal> <o:p></o:p><=
/p><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span
style=3D'font-=
size:12.0pt;font-family:"Times New
Roman",serif;mso-fareast-language:DE'><b=
r><br><o:p></o:p></span></p><pre>__________________________________________=
_____<o:p></o:p></pre><pre>Users mailing
list<o:p></o:p></pre><pre><a href=
=3D"mailto:Users@ovirt.org">Users@ovirt.org</a><o:p></o:p></pre><pre><a
hre=
f=3D"http://lists.ovirt.org/mailman/listinfo/users">http://l...
mailman/listinfo/users</a><o:p></o:p></pre></blockquote><p>Hi
Sven,<o:p></o=
:p></p><p> Do you have granular entry heal
enabled on the=
volume? If no, there is a feature called granular entry self-heal which sh=
ould be enabled with sharded volumes to get the benefits. So when a brick g=
oes down and say only 1 in those million entries is created/deleted. Self-h=
eal would be done for only that file it won't crawl the entire directory.<o=
:p></o:p></p><p> <span
style=3D'color:#333333;background:=
white'>You can run<span
class=3Dapple-converted-space> </span></span><=
code><span
style=3D'font-size:11.0pt;color:#333333;background:white'>gluste=
r volume set</span></code><span class=3Dapple-converted-space><span
style=
=3D'font-size:11.0pt;font-family:"Courier
New";color:#333333;background:whi=
te'> </span></span><em><span
style=3D'font-size:11.0pt;font-family:"Co=
urier
New";color:#333333;background:white'>VOLNAME</span></em><span
class=
=3Dapple-converted-space><span
style=3D'font-size:11.0pt;font-family:"Couri=
er
New";color:#333333;background:white'> </span></span><code><span
sty=
le=3D'font-size:11.0pt;color:#333333;background:white'>cluster.granular-ent=
ry-heal enable / disable</span></code><span
class=3Dapple-converted-space><=
span style=3D'font-size:11.0pt;font-family:"Courier
New";color:#333333;back=
ground:white'> </span></span><span
style=3D'color:#333333;background:w=
hite'>command only if the volume is in<span
class=3Dapple-converted-space>&=
nbsp;</span></span><code><span
style=3D'font-size:11.0pt;color:#333333;back=
ground:white'>Created</span></code><span
class=3Dapple-converted-space><spa=
n style=3D'font-size:11.0pt;font-family:"Courier
New";color:#333333;backgro=
und:white'> </span></span><span
style=3D'color:#333333;background:whit=
e'>state. If the volume is in any other state other than<span class=3Dapple=
-converted-space> </span></span><code><span
style=3D'font-size:11.0pt;=
color:#333333;background:white'>Created</span></code><span
class=3Dapple-co=
nverted-space><span style=3D'font-size:11.0pt;font-family:"Courier
New";col=
or:#333333;background:white'> </span></span><span
style=3D'color:#3333=
33;background:white'>, for example,<span
class=3Dapple-converted-space>&nbs=
p;</span></span><code><span
style=3D'font-size:11.0pt;color:#333333;backgro=
und:white'>Started</span></code><span
class=3Dapple-converted-space><span s=
tyle=3D'font-size:11.0pt;font-family:"Courier
New";color:#333333;background=
:white'> </span></span><span
style=3D'color:#333333;background:white'>=
,<span
class=3Dapple-converted-space> </span></span><code><span
style=
=3D'font-size:11.0pt;color:#333333;background:white'>Stopped</span></code><=
span style=3D'color:#333333;background:white'>, and so on, execute<span
cla=
ss=3Dapple-converted-space> </span></span><code><span
style=3D'font-si=
ze:11.0pt;color:#333333;background:white'>gluster volume heal VOLNAME granu=
lar-entry-heal</span></code><span class=3Dapple-converted-space><span
style=
=3D'font-size:11.0pt;font-family:"Courier
New";color:#333333;background:whi=
te'> </span></span><code><span
style=3D'font-size:9.5pt;color:#333333'=
enable / disable</span></code><span
class=3Dapple-converted-space><span st=
yle=3D'color:#333333;background:white'> </span></span><span
style=3D'c=
olor:#333333;background:white'>command to enable or disable granular-entry-=
heal
option.</span><o:p></o:p></p><p>Thanks<o:p></o:p></p><p>kasturi<o:p></=
o:p></p></div></body></html>=
--_000_BFAB40933B3367488CE6299BAF8592D1014E52CC4356SOCRATESasl_--
2:22 p.m.
This is a multi-part message in MIME format.
--------------F665B3500A76C389CE232BB1
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
On 04/24/2017 05:36 PM, Sven Achtelik wrote:
Hi Kasturi,
Ill try that. Will this be persistent over a reboot of a host or even
stopping of the complete cluster ?
Thank you
Hi Sven,
This is a volume set option ((has nothing to do with reboot)and it
will be present on the volume until you reset it manually using 'gluster
volume reset' command . You just need to execute 'gluster volume heal
<volname> granular-entry-heal enable' and this will do the right thing
for you.
Thanks
kasturi.
*Von:*knarra [mailto:knarra@redhat.com]
*Gesendet:* Montag, 24. April 2017 13:44
*An:* Sven Achtelik <Sven.Achtelik(a)eps.aero>; users(a)ovirt.org
*Betreff:* Re: [ovirt-users] Hyperconverged Setup and Gluster healing
On 04/24/2017 05:03 PM, Sven Achtelik wrote:
Hi All,
my oVirt-Setup is 3 Hosts with gluster and reaplica 3. I always
try to stay on the current version and Im applying
updates/upgrade if there are any. For this I put a host in
maintenance and also use the Stop Gluster Service checkbox.
After its done updating Ill set it back to active and wait until
the engine sees all bricks again and then Ill go for the next host.
This worked fine for me the last month and now that I have more
and more VMs running the changes that are written to the gluster
volume while a host is in maintenance become a lot more and it
takes pretty long for the healing to complete. What I dont
understand is that I dont really see a lot of network usage in
the GUI during that time and it feels quiet slow. The Network for
the gluster is a 10G and Im quiet happy with the performance of
it, its just the healing that takes long. I noticed that because
I couldnt update the third host because of unsynced gluster volumes.
Is there any limiting variable that slows down traffic during
healing that needs to be configured ? Or should I maybe change my
updating process somehow to avoid having so many changes in queue?
Thank you,
Sven
_______________________________________________
Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
Hi Sven,
Do you have granular entry heal enabled on the volume? If no,
there is a feature called granular entry self-heal which should be
enabled with sharded volumes to get the benefits. So when a brick goes
down and say only 1 in those million entries is created/deleted.
Self-heal would be done for only that file it won't crawl the entire
directory.
You can run|gluster volume set|/VOLNAME/|cluster.granular-entry-heal
enable / disable|command only if the volume is in|Created|state. If
the volume is in any other state other than|Created|, for
example,|Started|,|Stopped|, and so on, execute|gluster volume heal
VOLNAME granular-entry-heal||enable / disable|command to enable or
disable granular-entry-heal option.
Thanks
kasturi
--------------F665B3500A76C389CE232BB1
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<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 04/24/2017 05:36 PM, Sven Achtelik
wrote:<br>
</div>
<blockquote
cite="mid:BFAB40933B3367488CE6299BAF8592D1014E52CC4356@SOCRATES.asl.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
code
{mso-style-priority:99;
font-family:"Courier New";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Vorformatiert Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLVorformatiertZchn
{mso-style-name:"HTML Vorformatiert Zchn";
mso-style-priority:99;
mso-style-link:"HTML Vorformatiert";
font-family:Consolas;
color:black;
mso-fareast-language:EN-US;}
span.E-MailFormatvorlage21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.E-MailFormatvorlage23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="color:#1F497D">Hi
Kasturi,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"
lang="EN-US">Ill
try that. Will this be persistent over a reboot of a host or
even stopping of the complete cluster ?
<o:p></o:p></span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
name="_MailEndCompose"></a><span
style="color:#1F497D"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"
lang="EN-US">Thank
you</span></p>
</div>
</blockquote>
Hi Sven,<br>
<br>
This is a volume set option ((has nothing to do with reboot)and
it will be present on the volume until you reset it manually using
'gluster volume reset' command . You just need to execute 'gluster
volume heal <volname> granular-entry-heal enable' and this
will do the right thing for you. <br>
<br>
Thanks<br>
kasturi.<br>
<blockquote
cite="mid:BFAB40933B3367488CE6299BAF8592D1014E52CC4356@SOCRATES.asl.local"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D"
lang="EN-US"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="color:windowtext;mso-fareast-language:DE">Von:</span></b><span
style="color:windowtext;mso-fareast-language:DE"> knarra
[<a class="moz-txt-link-freetext"
href="mailto:knarra@redhat.com">mailto:knarra@redhat.com</a>]
<br>
<b>Gesendet:</b> Montag, 24. April 2017 13:44<br>
<b>An:</b> Sven Achtelik <a
class="moz-txt-link-rfc2396E"
href="mailto:Sven.Achtelik@eps.aero"><Sven.Achtelik@eps.aero></a>;
<a class="moz-txt-link-abbreviated"
href="mailto:users@ovirt.org">users@ovirt.org</a><br>
<b>Betreff:</b> Re: [ovirt-users] Hyperconverged Setup
and Gluster healing<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 04/24/2017 05:03 PM, Sven Achtelik
wrote:<span
style="font-size:12.0pt;mso-fareast-language:DE"><o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi All, <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">my
oVirt-Setup is 3
Hosts with gluster and reaplica 3. I always try to stay on
the current version and Im applying updates/upgrade if
there are any. For this I put a host in maintenance and
also use the Stop Gluster Service checkbox. After its
done updating Ill set it back to active and wait until
the engine sees all bricks again and then Ill go for the
next host. </span><o:p></o:p></p>
<p class="MsoNormal"><span
lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">This
worked fine for
me the last month and now that I have more and more VMs
running the changes that are written to the gluster volume
while a host is in maintenance become a lot more and it
takes pretty long for the healing to complete. What I
dont understand is that I dont really see a lot of
network usage in the GUI during that time and it feels
quiet slow. The Network for the gluster is a 10G and Im
quiet happy with the performance of it, its just the
healing that takes long. I noticed that because I couldnt
update the third host because of unsynced gluster
volumes.</span><o:p></o:p></p>
<p class="MsoNormal"><span
lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Is there
any limiting
variable that slows down traffic during healing that needs
to be configured ? Or should I maybe change my updating
process somehow to avoid having so many changes in queue?
</span><o:p></o:p></p>
<p class="MsoNormal"><span
lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Thank
you, </span><o:p></o:p></p>
<p class="MsoNormal"><span
lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
lang="EN-US">Sven</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"
style="margin-bottom:12.0pt"><span
style="font-size:12.0pt;font-family:"Times New
Roman",serif;mso-fareast-language:DE"><br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Users mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="mailto:Users@ovirt.org">Users@ovirt.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</blockquote>
<p>Hi Sven,<o:p></o:p></p>
<p> Do you have granular entry heal enabled on the volume? If
no, there is a feature called granular entry self-heal which
should be enabled with sharded volumes to get the benefits. So
when a brick goes down and say only 1 in those million entries
is created/deleted. Self-heal would be done for only that file
it won't crawl the entire directory.<o:p></o:p></p>
<p> <span style="color:#333333;background:white">You can
run<span
class="apple-converted-space"> </span></span><code><span
style="font-size:11.0pt;color:#333333;background:white">gluster
volume set</span></code><span
class="apple-converted-space"><span
style="font-size:11.0pt;font-family:"Courier
New";color:#333333;background:white"> </span></span><em><span
style="font-size:11.0pt;font-family:"Courier
New";color:#333333;background:white">VOLNAME</span></em><span
class="apple-converted-space"><span
style="font-size:11.0pt;font-family:"Courier
New";color:#333333;background:white"> </span></span><code><span
style="font-size:11.0pt;color:#333333;background:white">cluster.granular-entry-heal
enable / disable</span></code><span
class="apple-converted-space"><span
style="font-size:11.0pt;font-family:"Courier
New";color:#333333;background:white"> </span></span><span
style="color:#333333;background:white">command only if the
volume is in<span
class="apple-converted-space"> </span></span><code><span
style="font-size:11.0pt;color:#333333;background:white">Created</span></code><span
class="apple-converted-space"><span
style="font-size:11.0pt;font-family:"Courier
New";color:#333333;background:white"> </span></span><span
style="color:#333333;background:white">state. If the volume
is in any other state other than<span
class="apple-converted-space"> </span></span><code><span
style="font-size:11.0pt;color:#333333;background:white">Created</span></code><span
class="apple-converted-space"><span
style="font-size:11.0pt;font-family:"Courier
New";color:#333333;background:white"> </span></span><span
style="color:#333333;background:white">, for example,<span
class="apple-converted-space"> </span></span><code><span
style="font-size:11.0pt;color:#333333;background:white">Started</span></code><span
class="apple-converted-space"><span
style="font-size:11.0pt;font-family:"Courier
New";color:#333333;background:white"> </span></span><span
style="color:#333333;background:white">,<span
class="apple-converted-space"> </span></span><code><span
style="font-size:11.0pt;color:#333333;background:white">Stopped</span></code><span
style="color:#333333;background:white">, and so on,
execute<span
class="apple-converted-space"> </span></span><code><span
style="font-size:11.0pt;color:#333333;background:white">gluster
volume heal VOLNAME granular-entry-heal</span></code><span
class="apple-converted-space"><span
style="font-size:11.0pt;font-family:"Courier
New";color:#333333;background:white"> </span></span><code><span
style="font-size:9.5pt;color:#333333">enable /
disable</span></code><span
class="apple-converted-space"><span
style="color:#333333;background:white"> </span></span><span
style="color:#333333;background:white">command to enable or
disable granular-entry-heal
option.</span><o:p></o:p></p>
<p>Thanks<o:p></o:p></p>
<p>kasturi<o:p></o:p></p>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>
--------------F665B3500A76C389CE232BB1--
3:02 p.m.
This is a multi-part message in MIME format.
--------------EB5CC7609E582B131F35CB79
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Hello.
Out of curiosity, why do you and people in general use more replica 3
than replica 2 ?
If I understand correctly this seems overkill and waste of storage as 2
copies of data (replica 2) seems pretty reasonable similar to RAID 1
and still in the worst case the data can be replicated after a fail. I
see that replica 3 helps more on performance at the cost of space.
Fernando
On 24/04/2017 08:33, Sven Achtelik wrote:
Hi All,
my oVirt-Setup is 3 Hosts with gluster and reaplica 3. I always try to
stay on the current version and Im applying updates/upgrade if there
are any. For this I put a host in maintenance and also use the Stop
Gluster Service checkbox. After its done updating Ill set it back
to active and wait until the engine sees all bricks again and then
Ill go for the next host.
This worked fine for me the last month and now that I have more and
more VMs running the changes that are written to the gluster volume
while a host is in maintenance become a lot more and it takes pretty
long for the healing to complete. What I dont understand is that I
dont really see a lot of network usage in the GUI during that time
and it feels quiet slow. The Network for the gluster is a 10G and Im
quiet happy with the performance of it, its just the healing that
takes long. I noticed that because I couldnt update the third host
because of unsynced gluster volumes.
Is there any limiting variable that slows down traffic during healing
that needs to be configured ? Or should I maybe change my updating
process somehow to avoid having so many changes in queue?
Thank you,
Sven
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--------------EB5CC7609E582B131F35CB79
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hello.</p>
<p>Out of curiosity, why do you and people in general use more
replica 3 than replica 2 ?</p>
<p>If I understand correctly this seems overkill and waste of
storage as 2 copies of data (replica 2) seems pretty reasonable
similar to RAID 1 and still in the worst case the data can be
replicated after a fail. I see that replica 3 helps more on
performance at the cost of space.</p>
<p>Fernando<br>
</p>
<br>
<div class="moz-cite-prefix">On 24/04/2017 08:33, Sven Achtelik
wrote:<br>
</div>
<blockquote
cite="mid:BFAB40933B3367488CE6299BAF8592D1014E52CC4354@SOCRATES.asl.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi All, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">my
oVirt-Setup is 3
Hosts with gluster and reaplica 3. I always try to stay on
the current version and Im applying updates/upgrade if
there are any. For this I put a host in maintenance and also
use the Stop Gluster Service checkbox. After its done
updating Ill set it back to active and wait until the
engine sees all bricks again and then Ill go for the next
host. <o:p></o:p></span></p>
<p class="MsoNormal"><span
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">This
worked fine for me
the last month and now that I have more and more VMs running
the changes that are written to the gluster volume while a
host is in maintenance become a lot more and it takes pretty
long for the healing to complete. What I dont understand is
that I dont really see a lot of network usage in the GUI
during that time and it feels quiet slow. The Network for
the gluster is a 10G and Im quiet happy with the
performance of it, its just the healing that takes long. I
noticed that because I couldnt update the third host
because of unsynced gluster
volumes.<o:p></o:p></span></p>
<p class="MsoNormal"><span
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Is there
any limiting
variable that slows down traffic during healing that needs
to be configured ? Or should I maybe change my updating
process somehow to avoid having so many changes in queue?
<o:p></o:p></span></p>
<p class="MsoNormal"><span
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thank you,
<o:p></o:p></span></p>
<p class="MsoNormal"><span
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
lang="EN-US">Sven<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<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://...
</pre>
</blockquote>
<br>
</body>
</html>
--------------EB5CC7609E582B131F35CB79--
3:24 p.m.
Hello!
On Mon, Apr 24, 2017 at 3:02 PM, FERNANDO FREDIANI <
fernando.frediani(a)upx.com> wrote:
Out of curiosity, why do you and people in general use more replica 3
than
replica 2 ?
The answer is simple - quorum. With just two participants you don't know
what to do, when your peer is unreachable. When you have three
participants, you are able to establish a majority. In that case, when two
partiticipants are able to communicate, they now, that lesser part of
cluster knows, that it should not accept any changes.
If I understand correctly this seems overkill and waste of storage as
2
copies of data (replica 2) seems pretty reasonable similar to RAID 1 and
still in the worst case the data can be replicated after a fail. I see that
replica 3 helps more on performance at the cost of space.
You are absolutely right. You need two copies of data to provide data
redundancy
and you need three (or more) members in cluster to provide
distinguishable majority. Therefore we have arbiter volumes, thus solving
that issue [1].
[1]
https://gluster.readthedocs.io/en/latest/Administrator%20Guide/arbiter-vo...
3:33 p.m.
This is a multi-part message in MIME format.
--------------B6FFA6AC96D6E0AC3C594A20
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
But then quorum doesn't replicate data 3 times, does it ?
Fernando
On 24/04/2017 10:24, Denis Chaplygin wrote:
Hello!
On Mon, Apr 24, 2017 at 3:02 PM, FERNANDO FREDIANI
<fernando.frediani(a)upx.com <mailto:fernando.frediani@upx.com>> wrote:
Out of curiosity, why do you and people in general use more
replica 3 than replica 2 ?
The answer is simple - quorum. With just two participants you don't
know what to do, when your peer is unreachable. When you have three
participants, you are able to establish a majority. In that case, when
two partiticipants are able to communicate, they now, that lesser part
of cluster knows, that it should not accept any changes.
If I understand correctly this seems overkill and waste of storage
as 2 copies of data (replica 2) seems pretty reasonable similar to
RAID 1 and still in the worst case the data can be replicated
after a fail. I see that replica 3 helps more on performance at
the cost of space.
You are absolutely right. You need two copies of data to provide data
redundancy and you need three (or more) members in cluster to provide
distinguishable majority. Therefore we have arbiter volumes, thus
solving that issue [1].
[1]
https://gluster.readthedocs.io/en/latest/Administrator%20Guide/arbiter-vo...
--------------B6FFA6AC96D6E0AC3C594A20
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>But then quorum doesn't replicate data 3 times, does it ?</p>
<p>Fernando<br>
</p>
<br>
<div class="moz-cite-prefix">On 24/04/2017 10:24, Denis Chaplygin
wrote:<br>
</div>
<blockquote
cite="mid:CANVzE5kfHSF15iwRYxagU-rSEvN60XSZcjc8jVSTrKdYuXeeEg@mail.gmail.com"
type="cite">
<div dir="ltr">Hello!<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Apr 24, 2017 at 3:02 PM,
FERNANDO FREDIANI <span dir="ltr"><<a
moz-do-not-send="true" target="_blank"
href="mailto:fernando.frediani@upx.com">fernando.frediani@upx.com</a>></span>
wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px
solid rgb(204,204,204);padding-left:1ex"
class="gmail_quote">
<div bgcolor="#FFFFFF">Out of curiosity, why do you and
people in general use more replica 3 than replica 2 ? </div>
</blockquote>
<div><br>
</div>
<div>The answer is simple - quorum. With just two
participants you don't know what to do, when your peer is
unreachable. When you have three participants, you are
able to establish a majority. In that case, when two
partiticipants are able to communicate, they now, that
lesser part of cluster knows, that it should not accept
any changes.<br>
</div>
<div> </div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px
solid rgb(204,204,204);padding-left:1ex"
class="gmail_quote">
<div bgcolor="#FFFFFF">
<p>If I understand correctly this seems overkill and
waste of storage as 2 copies of data (replica 2)
seems pretty reasonable similar to RAID 1 and still in
the worst case the data can be replicated after a
fail. I see that replica 3 helps more on performance
at the cost of space.</p>
<span class="gmail-HOEnZb"></span><br>
</div>
</blockquote>
</div>
You are absolutely right. You need two copies of data to
provide data redundancy and you need three (or more) members
in cluster to provide distinguishable majority. Therefore we
have arbiter volumes, thus solving that issue [1]. <br>
<br>
[1] <a moz-do-not-send="true"
href="https://gluster.readthedocs.io/en/latest/Administrator%20Guide/arbiter-volumes-and-quorum/">https://gluster.readthedocs.io/en/latest/Administrator%20Guide/arbiter-volumes-and-quorum/</a><br>
</div>
</div>
</blockquote>
<br>
</body>
</html>
--------------B6FFA6AC96D6E0AC3C594A20--
4:35 p.m.
With arbiter volume you still have a replica 3 volume, meaning that you
have three participants in your quorum. But only two of those participants
keep the actual data. Third one, the arbiter, stores only some metadata,
not the files content, so data is not replicated 3 times.
On Mon, Apr 24, 2017 at 3:33 PM, FERNANDO FREDIANI <
fernando.frediani(a)upx.com> wrote:
But then quorum doesn't replicate data 3 times, does it ?
Fernando
On 24/04/2017 10:24, Denis Chaplygin wrote:
Hello!
On Mon, Apr 24, 2017 at 3:02 PM, FERNANDO FREDIANI <
fernando.frediani(a)upx.com> wrote:
> Out of curiosity, why do you and people in general use more replica 3
> than replica 2 ?
>
The answer is simple - quorum. With just two participants you don't know
what to do, when your peer is unreachable. When you have three
participants, you are able to establish a majority. In that case, when two
partiticipants are able to communicate, they now, that lesser part of
cluster knows, that it should not accept any changes.
> If I understand correctly this seems overkill and waste of storage as 2
> copies of data (replica 2) seems pretty reasonable similar to RAID 1 and
> still in the worst case the data can be replicated after a fail. I see that
> replica 3 helps more on performance at the cost of space.
>
> You are absolutely right. You need two copies of data to provide data
redundancy and you need three (or more) members in cluster to provide
distinguishable majority. Therefore we have arbiter volumes, thus solving
that issue [1].
[1] https://gluster.readthedocs.io/en/latest/Administrator%
20Guide/arbiter-volumes-and-quorum/
4:41 p.m.
This is a multi-part message in MIME format.
--------------E1421BB04F7A8066E3169AB1
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Ok, great, thanks for the clarification.
Therefore a replica 3 configuration means raw storage space cost is
'similar' to a RAID 1 and actual data exists only 2 times and two
different servers.
Regards
Fernando
On 24/04/2017 11:35, Denis Chaplygin wrote:
With arbiter volume you still have a replica 3 volume, meaning that
you have three participants in your quorum. But only two of those
participants keep the actual data. Third one, the arbiter, stores only
some metadata, not the files content, so data is not replicated 3 times.
On Mon, Apr 24, 2017 at 3:33 PM, FERNANDO FREDIANI
<fernando.frediani(a)upx.com <mailto:fernando.frediani@upx.com>> wrote:
But then quorum doesn't replicate data 3 times, does it ?
Fernando
On 24/04/2017 10:24, Denis Chaplygin wrote:
> Hello!
>
> On Mon, Apr 24, 2017 at 3:02 PM, FERNANDO FREDIANI
> <fernando.frediani(a)upx.com <mailto:fernando.frediani@upx.com>>
wrote:
>
> Out of curiosity, why do you and people in general use more
> replica 3 than replica 2 ?
>
>
> The answer is simple - quorum. With just two participants you
> don't know what to do, when your peer is unreachable. When you
> have three participants, you are able to establish a majority. In
> that case, when two partiticipants are able to communicate, they
> now, that lesser part of cluster knows, that it should not accept
> any changes.
>
> If I understand correctly this seems overkill and waste of
> storage as 2 copies of data (replica 2) seems pretty
> reasonable similar to RAID 1 and still in the worst case the
> data can be replicated after a fail. I see that replica 3
> helps more on performance at the cost of space.
>
>
> You are absolutely right. You need two copies of data to provide
> data redundancy and you need three (or more) members in cluster
> to provide distinguishable majority. Therefore we have arbiter
> volumes, thus solving that issue [1].
>
> [1]
>
https://gluster.readthedocs.io/en/latest/Administrator%20Guide/arbiter-vo...
>
<https://gluster.readthedocs.io/en/latest/Administrator%20Guide/arbiter-vo...
--------------E1421BB04F7A8066E3169AB1
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Ok, great, thanks for the clarification.</p>
<p>Therefore a replica 3 configuration means raw storage space cost
is 'similar' to a RAID 1 and actual data exists only 2 times and
two different servers.</p>
<p>Regards<br>
Fernando<br>
</p>
<br>
<div class="moz-cite-prefix">On 24/04/2017 11:35, Denis Chaplygin
wrote:<br>
</div>
<blockquote
cite="mid:CANVzE5nokh4MnXYfh8-oSQ8v0o1R4cKP0q1k5SKWPBqBHXiVqg@mail.gmail.com"
type="cite">
<div dir="ltr">With arbiter volume you still have a replica 3
volume, meaning that you have three participants in your quorum.
But only two of those participants keep the actual data. Third
one, the arbiter, stores only some metadata, not the files
content, so data is not replicated 3 times.<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Apr 24, 2017 at 3:33 PM,
FERNANDO FREDIANI <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:fernando.frediani@upx.com"
target="_blank">fernando.frediani(a)upx.com</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>But then quorum doesn't replicate data 3 times, does it
?</p>
<span class="HOEnZb"><font color="#888888">
<p>Fernando<br>
</p>
</font></span>
<div>
<div class="h5"> <br>
<div class="m_-3736559709896304842moz-cite-prefix">On
24/04/2017 10:24, Denis Chaplygin wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hello!<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Apr 24, 2017 at
3:02 PM, FERNANDO FREDIANI <span
dir="ltr"><<a
moz-do-not-send="true"
href="mailto:fernando.frediani@upx.com"
target="_blank">fernando.frediani(a)upx.com</a>&gt;</span>
wrote:<br>
<blockquote style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"
class="gmail_quote">
<div bgcolor="#FFFFFF">Out of curiosity, why
do you and people in general use more
replica 3 than replica 2 ? </div>
</blockquote>
<div><br>
</div>
<div>The answer is simple - quorum. With just
two participants you don't know what to do,
when your peer is unreachable. When you have
three participants, you are able to
establish a majority. In that case, when two
partiticipants are able to communicate, they
now, that lesser part of cluster knows, that
it should not accept any changes.<br>
</div>
<div> </div>
<blockquote style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"
class="gmail_quote">
<div bgcolor="#FFFFFF">
<p>If I understand correctly this seems
overkill and waste of storage as 2
copies of data (replica 2) seems pretty
reasonable similar to RAID 1 and still
in the worst case the data can be
replicated after a fail. I see that
replica 3 helps more on performance at
the cost of space.</p>
<span
class="m_-3736559709896304842gmail-HOEnZb"></span><br>
</div>
</blockquote>
</div>
You are absolutely right. You need two copies of
data to provide data redundancy and you need
three (or more) members in cluster to provide
distinguishable majority. Therefore we have
arbiter volumes, thus solving that issue [1]. <br>
<br>
[1] <a moz-do-not-send="true"
href="https://gluster.readthedocs.io/en/latest/Administrator%20Guide/arbiter-volumes-and-quorum/"
target="_blank">https://gluster.readthedocs.<wbr>io/en/latest/Administrator%<wbr>20Guide/arbiter-volumes-and-<wbr>quorum/</a><br>
</div>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>
--------------E1421BB04F7A8066E3169AB1--
2551
days inactive
2551
days old
8 comments
4 participants
participants (4)
-
Denis Chaplygin -
FERNANDO FREDIANI -
knarra -
Sven Achtelik