On 01/23/2016 10:02 AM, Dan Lambright wrote:
----- Original Message -----
From: "Pranith Kumar Karampuri" <[email protected]>
To: "Ravishankar N" <[email protected]>, "Gluster Devel"
<[email protected]>, "Dan Lambright"
<[email protected]>, "Joseph Fernandes" <[email protected]>, "Nithya
Balachandran" <[email protected]>,
"Mohammed Rafi K C" <[email protected]>
Sent: Friday, January 22, 2016 10:48:15 PM
Subject: Re: [Gluster-devel] Reverse brick order in tier volume- Why?
On 01/22/2016 03:48 PM, Ravishankar N wrote:
On 01/19/2016 06:44 PM, Ravishankar N wrote:
1) Is there is a compelling reason as to why the bricks of hot-tier
are in the reverse order ?
2) If there isn't one, should we spend time to fix it so that the
bricks appear in the order in which they were given at the time of
volume creaction/ attach-tier *OR* just continue with the way things
are currently because it is not that much of an issue?
Dan / Joseph - any pointers?
This order was an artifact of how the volume is created using legacy code and
data structures in glusterd-volgen.c. Two volume graphs are built (the hot and
the cold). The two graphs are built and combined in a single list. As far as I
know, nobody has run into trouble with this. Refactoring the code would be fine
to ease maintainability.
Cool, the reason we ask is, that in arbiter volumes, 3rd brick is going
to be the arbiter. If the bricks are in reverse order, it will lead to
confusion. We will change it with our implementation of attach-tier for
replica+arbiter bricks.
Pranith
+Nitya, Rafi as well.
-Ravi
_______________________________________________
Gluster-devel mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-devel
