+++ This bug was initially created as a clone of Bug #1193929 +++ I hope this bug is never fixed. The upstream patch process requires that each patch have an associated bug ID before it can be merged. However, there is no requirement that the bug contain any information or receive any kind of signoff before the patch can proceed. As a result, many of our developers have the habit of creating such "placeholder" bugs every time they want to make a change, even if it's just a random cleanup/idea and not an actual bug fix or requested/tracked feature request. Also, any patch with the dreaded "rfc" bug ID (which would be appropriate for such changes) is unlikely to be reviewed. This bug exists to satisfy our process requirement, without the additional negatives of clogging up our triage/tracking processes and making it appear that the code has more bugs (which would be bad) when in fact a developer had more ideas (which is generally good).
REVIEW: https://review.gluster.org/22197 (fuse: reflect the actual default for lru-limit option) posted (#3) for review on release-6 by Shyamsundar Ranganathan
REVIEW: https://review.gluster.org/22197 (fuse: reflect the actual default for lru-limit option) merged (#4) on release-6 by Shyamsundar Ranganathan
REVIEW: https://review.gluster.org/22960 (tests/utils: Fix py2/py3 util python scripts) posted (#1) for review on release-6 by Xavi Hernandez
REVIEW: https://review.gluster.org/22960 (tests/utils: Fix py2/py3 util python scripts) merged (#1) on release-6 by Xavi Hernandez
REVIEW: https://review.gluster.org/24206 (dht - selfheal code cleaning) posted (#2) for review on master by Barak Sason Rofman
This bug is moved to https://github.com/gluster/glusterfs/issues/1002, and will be tracked there from now on. Visit GitHub issues URL for further details