FSSlaveDirectoryProvider initialize

samd · **Joined:** Fri Oct 05, 2007 3:22 am **Posts:** 69

Has there been issues with this on shared drives? The reason why I'm asking is that I'm constantly see this exception

Code:

No current marker in source directory

Now when I debug the initialize method for the following code section:

Code:

if ( ! new File(source, "current1").exists() && ! new File(source, "current2").exists() ) {
         throw new IllegalStateException("No current marker in source directory");
      }

The source directory points to the shared drive where the master is copying its index files so that is correct, looking in that directory I do see either a current1 or current2 file so that is fine.

I was assuming that this may be some form of race condition where the check is happening at the time where that file is being replaced which is still a situation which HS should take into account but doesn't appear to do so.

The problem though is this is happening quite frequently too frequently actually.

sanne.grinovero · **Posted:** Sat Jan 31, 2009 5:17 am

you're right that's a race condition we should solve.
Still you could have another problem, since I think this can't show up "quite frequently".
What do you mean? and how often do you synch the indexes?

samd · **Joined:** Fri Oct 05, 2007 3:22 am **Posts:** 69

This looks like it might be a kernel issue with the version of the OS we are using.