|
From: Yonik S. <yo...@ap...> - 2008-04-09 17:11:42
|
I'm trying to catch up with all the activity... please ignore if this has been addressed in later emails. On Wed, Apr 2, 2008 at 1:36 PM, Doug Cutting <cu...@ap...> wrote: > Second, I don't yet see a way around checking versions when documents > are added or deleted. The ugliest bit is that we have to keep track of > the version of every document that's ever been deleted, in case a > long-offline node comes online and reports a stale addition. That table > could grow without bound. Sigh. Do you see a way around this? > > Perhaps a node could discard old deletions after a time, keeping track > of the log entry number of the oldest retained deletion. Attempts to > sync starting with an older entry number should be rejected and should > trigger a complete copy-based replacement of the stale index. Right, this seems like the right approach. We shouldn't have to support incremental syncs forever. > The > hazard is that, if a document is added to a single node, then that node > goes offline for a long time, then, when it comes online, the addition > will be lost. Not great. If a document is added to a single node, it could be lost permanently anyway (node may never come back). That's why an add should go to multiple nodes. -Yonik |