<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Strahil<br>
</p>
<div class="moz-cite-prefix">On 16/11/20 4:21 pm, Strahil Nikolov
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:2050636085.3425870.1605523871494@mail.yahoo.com">
<pre class="moz-quote-pre" wrap="">Hi Ravi,
I can propose a pull request if someone gives me a general idea of each setting.
Do we have comments in the source code that can be used as a description ?</pre>
</blockquote>
<p>`gluster volume set help` lists many of the documented options.
For the others (which usually are not needed to be tweaked but
its there if you still want to play with), each translator has a<b>
<font face="monospace">struct volume_options options[]</font></b>
in the source code (do a<font face="monospace"> git grep "struct
volume_options options"</font> on the source code) which usually
has a ".<b>description</b>" filed that gives a short description.</p>
<p>HTH,</p>
<p>Ravi<br>
</p>
<blockquote type="cite"
cite="mid:2050636085.3425870.1605523871494@mail.yahoo.com">
<pre class="moz-quote-pre" wrap="">
Best Regards,
Strahil Nikolov
В понеделник, 16 ноември 2020 г., 10:36:09 Гринуич+2, Ravishankar N <a class="moz-txt-link-rfc2396E" href="mailto:ravishankar@redhat.com"><ravishankar@redhat.com></a> написа:
On 14/11/20 3:23 am, Mahdi Adnan wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Hi,
Differently, the Gluster docs missing quite a bit regarding the available options that can be used in the volumes.
Not only that, there are some options that might corrupt data and do not have proper documentation, for example, disable Sharding will lead to data corruption and I think it does not give any warning? "maybe I'm wrong regarding the warning tho" and I can not find any details about it in the official Gluster docs. The same goes for multiple clients accessing a volume with Sharding enabled.
also, in some cases, write-behind and stat-prefetch can lead to data inconsistency if multiple clients accessing the same data.
I think having solid "Official" Gluster docs with all of these details is essential to have stable Gluster deployments.
On Thu, Nov 12, 2020 at 7:34 PM Eli V <a class="moz-txt-link-rfc2396E" href="mailto:eliventer@gmail.com"><eliventer@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I think docs.gluster.org needs a section on the available parameters,
especially considering how important some of them can be. For example
a google for performance.parallel-readdir, or
features.cache-invalidation only seems to turn up some hits in the
release notes on docs.gluster.org. I woudn't expect a new user to have
to go read the release notes for all previous releases to understand
the importance of these parameters, or what paremeters even exist.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
<a class="moz-txt-link-freetext" href="https://docs.gluster.org/en/latest/">https://docs.gluster.org/en/latest/</a> can be updated by sending pull requests to <a class="moz-txt-link-freetext" href="https://github.com/gluster/glusterdocs">https://github.com/gluster/glusterdocs</a>. It would be great if you can send some patches regarding the changes you would like to see. It doesn't have to be perfect. I can help in getting them reviewed and merged.
Thanks,
Ravi
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> ________
Community Meeting Calendar:
Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: <a class="moz-txt-link-freetext" href="https://meet.google.com/cpu-eiue-hvk">https://meet.google.com/cpu-eiue-hvk</a>
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="https://lists.gluster.org/mailman/listinfo/gluster-users">https://lists.gluster.org/mailman/listinfo/gluster-users</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
--
Respectfully
Mahdi
________
Community Meeting Calendar:
Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: <a class="moz-txt-link-freetext" href="https://meet.google.com/cpu-eiue-hvk">https://meet.google.com/cpu-eiue-hvk</a>
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="https://lists.gluster.org/mailman/listinfo/gluster-users">https://lists.gluster.org/mailman/listinfo/gluster-users</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
________
Community Meeting Calendar:
Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: <a class="moz-txt-link-freetext" href="https://meet.google.com/cpu-eiue-hvk">https://meet.google.com/cpu-eiue-hvk</a>
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="https://lists.gluster.org/mailman/listinfo/gluster-users">https://lists.gluster.org/mailman/listinfo/gluster-users</a>
</pre>
</blockquote>
</body>
</html>