As I understand it, only new files will be sharded, but simply renaming or moving them may be enough in that case.
I'm interested in the arbiter/sharding bug you've mentioned. Could you provide any more details or a link?On 30 March 2017 at 20:25, Laura Bailey <lbailey@xxxxxxxxxx> wrote:
I can't answer all of these, but I think the only way to share existing files is to create a new volume with sharding enabled and copy the files over into it.Cheers,Laura B
On Friday, March 31, 2017, Alessandro Briosi <ab1@xxxxxxxxxxx> wrote:Hi I need some advice.
I'm currently on 3.8.10 and would like to know the following:
1. If I add an arbiter to an existing volume should I also run a rebalance?
2. If I had sharding enabled would adding the arbiter trigger the
corruption bug?
3. What's the procedure to enable sharding on an existing volume so that
it shards already existing files?
4. Suppose I have sharding disabled, then add an arbiter brick, then
enable sharding and execute the procedure for point 3, would this still
trigger the corruption bug?
Thanks,
Alessandro
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
--Laura BaileySenior Technical WriterCustomer Content Services BNE
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
