[Linux-cachefs] cachefs and index keys

[Ion Badulescu]

Hi Grant,

We hit the same problem with cachefs and the isilon smartconnect 
feature. We ended up generating the autofs maps by hashing the clients 
to individual smartconnect addresses, so one client will always connect 
to one and only one NFS IP address. It may not be the right solution for 
you, but it works for us...

Thanks,
-Ion


On 09/04/2014 08:47 PM, Grant Street wrote:
> Just for completeness I am adding to this for future reference
>
> This has stalled with redhat and I have had no correspondence on this
> from the cachefs team.
>
> Because of the architecture of isilon it defeats the cachefs caching
> mechanism.
>
> Grant
>
>
> On 06/01/14 11:51, Grant Street wrote:
>> Hi
>>
>> We are using EMC's Isilon storage as a NFS server consisting of over 50
>> storage and networking nodes. It presents itself as one hostname eg
>> isilon.sample.com and one very large directory tree, but dynamically
>> resolves to multiple IP addresses. These IP addresses have the advantage
>> of floating to different physical nodes in order to help balance the
>> networking load when thousands of clients are connecting.
>>
>> The downside of this scheme is that currently cachefs would invalidate
>> the cache if the IP address (resolved from isilon.sample.com) changes on
>> reboot or automount expire and remount. This is because the cache key is
>> based on the IP address rather than the fqdn.
>>
>> I have a case with redhat 00922150 and a bugzilla id 1018358. I was
>> wondering what your thoughts would be on changing the cache key to a
>> fqdn rather than an IP address?
>>
>> Unfortunately with the size of the isilon cluster we would not be able
>> to do anything with traditional IP load balancers as the throughput and
>> number of clients is too high.
>>
>> Thanks in advance.
>>
>> Grant
>>
>
> --
> Linux-cachefs mailing list
> Linux-cachefs at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cachefs