Re: Sharding - what next?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 16/12/15 22:59, Krutika Dhananjay wrote:
I guess I did not make myself clear. Apologies. I meant to say that printing a single list of counts aggregated from all bricks can be tricky and is susceptible to the possibility of same entry getting counted multiple times if the inode needs a heal on multiple bricks. Eliminating such duplicates would be rather difficult.

Or, we could have a sub-command of heal-info dump all the file paths/gfids that need heal from all bricks and you could pipe the output to 'sort | uniq | wc -l' to eliminate duplicates. Would that be OK? :)


Sorry, my fault - I did understand that. Aggregate counts per brick would be fine, I have no desire to complicate things for the devs :)



--
Lindsay Mathieson

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux