"robert engels" <[EMAIL PROTECTED]> wrote: > But merging segments doesn't delete the old, it only creates new, > unless the segments meet the "purge old criteria".
What's the "purge old criteria"? Normally a segment merge once committed immediately deletes the segments it had just merged. > A reopen() is supposed to open the latest version in the directory > by definition, so this seems rather a remote possibility. Well, if a commit is in-flight then likely the reopen will hit an exception and then retry. This is the same as a normal open. > If it occurs due to low system resources (meaning that during a > reopen some expected segments were already deleted, throw an > StaleIndexException) and the client can reissue the reopen() call > (similar to if it could not get the write lock). I'm not sure what you mean by "low system resources". Missing some files because they were deleted by a commit in process isn't a low system resources sort of situation. Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
