Re: Improving real world performance by moving files closer to their target workloads

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

 



I think im getting a little closer to understanding this. So the
metadata (file atributes AFR settings ect) is stored as a header on
the actual file and the central name space cache stores information to
do with file lookup, node its stored on ect. Does this sound correct?
If this is the case is it possible to update this namespace info as
the file is accessed or will that be dificult as they are currently
concidered static. i can see this as a potential issue where the local
and central caches may have consistancy issues. Would this problem be
lessened any by distributing the namespace cache? (im assuming a DHT
type solution) Would this just mean that consistancy problems would
occur in the instance of a node failure?

Thanks
Luke McGregor




[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