Am 04.08.2011 12:52, schrieb Michael McCandless:
This file is actually optional; its there for redundancy in case the
filesystem is not "reliable" when listing a directory. Ie, normally,
we list the directory to find the latest segments_N file; but if this
is wrong (eg the file system might have stale a cache) then we
fallback to reading the segments.gen file.
For example this is sometimes needed for NFS.
Likely replication is just skipping it?
That was my first idea. If not changed and touched then it will be skipped.
While being smart I deleted it on slave from index dir and then
replicated, but segment.gen was not replicated.
Due to your explanation NFS could not be reliable any more.
So my idea either a bug or a feature and the experts will know :-)
Regards
Bernd
Mike McCandless
http://blog.mikemccandless.com
On Thu, Aug 4, 2011 at 3:38 AM, Bernd Fehling
<bernd.fehl...@uni-bielefeld.de> wrote:
I have now updated to solr 3.3 but segment.gen is still not replicated.
Any idea why, is it a bug or a feature?
Should I write a jira issue for it?
Regards
Bernd
Am 29.07.2011 14:10, schrieb Bernd Fehling:
Dear list,
is there a deeper logic behind why the segment.gen file is not
replicated with solr 3.2?
Is it obsolete because I have a single segment?
Regards,
Bernd
