Description of problem: ====================== When performing attach-tier , it will be good to create the subvolume/bricks in the same order the bricks are specified in the command. For example: gluster volume tier testvol attach replica 3 rhsauto019.lab.eng.blr.redhat.com:/bricks/brick2/testvol_tier0 rhsauto020.lab.eng.blr.redhat.com:/bricks/brick2/testvol_tier1 rhsauto021.lab.eng.blr.redhat.com:/bricks/brick1/testvol_tier2 rhsauto022.lab.eng.blr.redhat.com:/bricks/brick1/testvol_tier3 rhsauto019.lab.eng.blr.redhat.com:/bricks/brick3/testvol_tier4 rhsauto020.lab.eng.blr.redhat.com:/bricks/brick3/testvol_tier5 " This would mean my first brick will be "rhsauto019.lab.eng.blr.redhat.com:/bricks/brick2/testvol_tier0", second brick is "rhsauto020.lab.eng.blr.redhat.com:/bricks/brick2/testvol_tier1 " and so on. But when i see the volume info, my first brick in the hot-tier will be "rhsauto020.lab.eng.blr.redhat.com:/bricks/brick3/testvol_tier5" which is misleading. Volume Name: testvol Type: Tier Volume ID: 50b291c4-68ec-4b40-8ca3-cd2a1524f43f Status: Started Number of Bricks: 12 Transport-type: tcp Hot Tier : Hot Tier Type : Distributed-Replicate Number of Bricks: 2 x 3 = 6 Brick1: rhsauto020.lab.eng.blr.redhat.com:/bricks/brick3/testvol_tier5 Brick2: rhsauto019.lab.eng.blr.redhat.com:/bricks/brick3/testvol_tier4 Brick3: rhsauto022.lab.eng.blr.redhat.com:/bricks/brick1/testvol_tier3 Brick4: rhsauto021.lab.eng.blr.redhat.com:/bricks/brick1/testvol_tier2 Brick5: rhsauto020.lab.eng.blr.redhat.com:/bricks/brick2/testvol_tier1 Brick6: rhsauto019.lab.eng.blr.redhat.com:/bricks/brick2/testvol_tier0 Cold Tier: Cold Tier Type : Distributed-Replicate Number of Bricks: 2 x 3 = 6 Brick7: rhsauto019.lab.eng.blr.redhat.com:/bricks/brick0/testvol_brick0 Brick8: rhsauto020.lab.eng.blr.redhat.com:/bricks/brick0/testvol_brick1 Brick9: rhsauto021.lab.eng.blr.redhat.com:/bricks/brick0/testvol_brick2 Brick10: rhsauto022.lab.eng.blr.redhat.com:/bricks/brick0/testvol_brick3 Brick11: rhsauto019.lab.eng.blr.redhat.com:/bricks/brick1/testvol_brick4 Brick12: rhsauto020.lab.eng.blr.redhat.com:/bricks/brick1/testvol_brick5 Options Reconfigured: cluster.watermark-hi: 90 cluster.watermark-low: 75 cluster.tier-mode: cache features.ctr-enabled: on performance.readdir-ahead: on Version-Release number of selected component (if applicable): ============================================================== glusterfs-server-3.7.5-13.el7rhgs.x86_64
I think this bug is an important to be fixed if we need to support arbiter with tiering. I am seeing many upstream queries on gluster-users as well asking for this combination.
Thank you for your bug report. We are no longer working on any improvements for Tier. This bug will be set to CLOSED WONTFIX to reflect this. Please reopen if the rfe is deemed critical.