Kotresh Hiremath Ravishankar
2020-Apr-21 12:59 UTC
[Gluster-users] Volume parameters listed more than once
On Mon, Apr 20, 2020 at 9:37 PM Yaniv Kaul <ykaul at redhat.com> wrote:> > > On Mon, Apr 20, 2020 at 5:38 PM Dmitry Antipov <dmantipov at yandex.ru> > wrote: > >> # gluster volume info >> >> Volume Name: TEST0 >> Type: Distributed-Replicate >> Volume ID: ca63095f-58dd-4ba8-82d6-7149a58c1423 >> Status: Created >> Snapshot Count: 0 >> Number of Bricks: 3 x 3 = 9 >> Transport-type: tcp >> Bricks: >> Brick1: HOST-001:/mnt/SSD-0003 >> Brick2: HOST-001:/mnt/SSD-0004 >> Brick3: HOST-002:/mnt/SSD-0003 >> Brick4: HOST-002:/mnt/SSD-0004 >> Brick5: HOST-002:/mnt/SSD-0005 >> Brick6: HOST-003:/mnt/SSD-0002 >> Brick7: HOST-003:/mnt/SSD-0003 >> Brick8: HOST-003:/mnt/SSD-0004 >> Brick9: HOST-004:/mnt/SSD-0002 >> Options Reconfigured: >> storage.fips-mode-rchecksum: on >> transport.address-family: inet >> nfs.disable: on >> performance.client-io-threads: off >> >> # gluster volume get TEST0 all | grep performance.cache-size >> performance.cache-size 32MB >> performance.cache-size 128MB >> > > I suspect these are for different translators and regretfully have the > same name... > performance/io-cache and performance/quick-read. > > >> >> ??? >> >> # gluster volume get TEST0 all | grep features.ctime >> features.ctime on >> features.ctime on >> > > Same - storage/posix and features/utime translators. >Yes, that's correct. These two xlators are dependent. Initially it was two different options to enable each xlators to enable ctime feature. The consumer had to enable both xlators with two different commands to enable ctime feature. So it was decided to provide the same key "features.ctime" to enable both xlators internally resulting in two entries in volume info.> > Worth filing an issue about it, as it is indeed somewhat confusing. > Y. > > >> ??? >> >> Dmitry >> ________ >> >> >> >> Community Meeting Calendar: >> >> Schedule - >> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC >> Bridge: https://bluejeans.com/441850968 >> >> Gluster-users mailing list >> Gluster-users at gluster.org >> https://lists.gluster.org/mailman/listinfo/gluster-users >> >> >> ________ > > > > Community Meeting Calendar: > > Schedule - > Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC > Bridge: https://bluejeans.com/441850968 > > Gluster-users mailing list > Gluster-users at gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-users >-- Thanks and Regards, Kotresh H R -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200421/d903275c/attachment.html>
Dmitry Antipov
2020-Apr-21 13:08 UTC
[Gluster-users] Volume parameters listed more than once
On 4/21/20 3:59 PM, Kotresh Hiremath Ravishankar wrote:> Yes, that's correct. These two xlators are dependent. Initially it was two different options to enable each xlators to enable ctime feature. > The consumer had to enable both xlators with two different commands to enable ctime feature. So it was decided > to provide the same key "features.ctime" to enable both xlators internally resulting in two entries in volume info.Hmm...what about network.tcp-window-size? Dmitry