On Thu, Aug 13, 2009 at 11:03 AM, Sage Weil <s...@newdream.net> wrote: > > So.. how do we know we hit EOF? The client gets notification of > truncation, so if we're entirely below our last known size, we know it's > not EOF. But the rest of the time, we need to get an updated size from > the MDS, which in turn will ask each client for their size. Slow, but > correct.
Not necessarily that slow.. the common case would be for a client to append the file, and if it creates a hole, once the other clients hit it they will be updated with the new file size so that every subsequent calls will already be aware of that. I do agree that there is a valid case, in which one writer writes records in an aligned offset, but with unaligned size (e.g. writes 5000 bytes on a 8192 boundaries) and there's another client following the writes we can have redundant requests, but in order to this have some real effect the 2 clients really need to be synchronized. Yehuda ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Ceph-devel mailing list Ceph-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ceph-devel
