Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

FSSlaveDirectoryProvider could retry several times when the current marker file is not found

Description

The FSMasterDirectoryProvider has a hole in the startup procedure where it is possible for the FSSlaveDirectoryProvider to not being able to find the current marker file. At the moment the startup for the slave will fail in this case. We could let the FSSlaveDirectoryProvider retry for a couple of times to allow the master to create the marker file.

This problem can also occur during runtime, but there the FSSlaveDirectoryProvider just skips a sync. However, we log this as error. Probably should just be a warning.

Activity

Show:

Emmanuel Bernard November 6, 2010 at 7:27 PM

People can define a retry_marker_lookup property

We retry every 5 seconds

Emmanuel Bernard October 8, 2010 at 5:11 PM

I wonder if it's the right thing to do actually.
We know the system won't boot properly today if the master is not started first and initialize the directory structure. Adding a retry n times would only be here to hide the fundamental weakness. Or is there a use case I am missing?

Christian Strzadala May 31, 2010 at 1:45 AM

Affected version also should include 3.1.1.GA

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created May 28, 2010 at 11:04 AM
Updated September 11, 2011 at 6:19 PM
Resolved November 6, 2010 at 7:27 PM