On 10/26/2011 1:32 PM, Booker Bense wrote: > The symptom we see is thread exhaustion due to write callbacks from many > clients for a single volume[1]. The problem is insidious as it's not a > gradual failure, because everything works just fine > until you hit a tipping point in the number of batch jobs. > > It's often a file that the user isn't even aware they are opening, but > is a small file used by some library they are > using. Sometimes tracking down the file can take significant > effort.
The issue is not going to be callbacks on a volume since callbacks are not issued on a per volume basis for read/write volumes and I assume that these jobs are not issuing volume releases which would trigger callback breaks on readonly volumes. The more likely scenario are: . file lock requests/releases on a specific file . data stores to a particular file . directory content changes (create, rename, link, unlink) in a single directory Jeffrey Altman
signature.asc
Description: OpenPGP digital signature
