<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 11 October 2018 at 18:30, Shyam Ranganathan <span dir="ltr"><<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 10/10/2018 11:20 PM, Atin Mukherjee wrote:<br>
> <br>
> <br>
> On Wed, 10 Oct 2018 at 20:30, Shyam Ranganathan <<a href="mailto:srangana@redhat.com">srangana@redhat.com</a><br>
</span><span class="">> <mailto:<a href="mailto:srangana@redhat.com">srangana@redhat.com</a>>> wrote:<br>
> <br>
> The following options were added post 4.1 and are part of 5.0 as the<br>
> first release for the same. They were added in as part of bugs, and<br>
> hence looking at github issues to track them as enhancements did not<br>
> catch the same.<br>
> <br>
> We need to document it in the release notes (and also the gluster doc.<br>
> site ideally), and hence I would like a some details on what to write<br>
> for the same (or release notes commits) for them.<br>
> <br>
> Option: cluster.daemon-log-level<br>
> Attention: @atin<br>
> Review: <a href="https://review.gluster.org/c/glusterfs/+/20442" rel="noreferrer" target="_blank">https://review.gluster.org/c/<wbr>glusterfs/+/20442</a><br>
> <br>
> <br>
> This option has to be used based on extreme need basis and this is why<br>
> it has been mentioned as GLOBAL_NO_DOC. So ideally this shouldn't be<br>
> documented.<br>
> <br>
> Do we still want to capture it in the release notes?<br>
<br>
</span>This is an interesting catch-22, when we want users to use the option<br>
(say to provide better logs for troubleshooting), we have nothing to<br>
point to, and it would be instructions (repeated over the course of<br>
time) over mails.<br>
<br>
I would look at adding this into an options section in the docs, but the<br>
best I can find in there is<br>
<a href="https://docs.gluster.org/en/latest/Administrator%20Guide/Managing%20Volumes/" rel="noreferrer" target="_blank">https://docs.gluster.org/en/<wbr>latest/Administrator%20Guide/<wbr>Managing%20Volumes/</a><br>
<br>
I would say we need to improve the way we deal with options and the<br>
required submissions around the same.<br>
<br></blockquote><div>No argument there. I will take a look and get back on what we can improve in the docs.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thoughts?<br>
<br>
> <br>
> <<a href="https://review.gluster.org/c/glusterfs/+/20442" rel="noreferrer" target="_blank">https://review.gluster.org/c/<wbr>glusterfs/+/20442</a>><br>
<span class="">> <br>
> Option: ctime-invalidation<br>
> Attention: @Du<br>
> Review: <a href="https://review.gluster.org/c/glusterfs/+/20286" rel="noreferrer" target="_blank">https://review.gluster.org/c/<wbr>glusterfs/+/20286</a><br>
> <br>
> Option: shard-lru-limit<br>
> Attention: @krutika<br>
> Review: <a href="https://review.gluster.org/c/glusterfs/+/20544" rel="noreferrer" target="_blank">https://review.gluster.org/c/<wbr>glusterfs/+/20544</a><br>
> <br>
> Option: shard-deletion-rate<br>
> Attention: @krutika<br>
> Review: <a href="https://review.gluster.org/c/glusterfs/+/19970" rel="noreferrer" target="_blank">https://review.gluster.org/c/<wbr>glusterfs/+/19970</a><br>
> <br>
> Please send in the required text ASAP, as we are almost towards the end<br>
> of the release.<br>
> <br>
> Thanks,<br>
> Shyam<br>
> <br>
</span>______________________________<wbr>_________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">https://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a><br>
</blockquote></div><br></div></div>