[jira] [Resolved] (CAMEL-22430) Make FileLockClusterView more resilient to split-brain scenarios

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-22430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-22430.
---------------------------------
    Resolution: Fixed

> Make FileLockClusterView more resilient to split-brain scenarios
> ----------------------------------------------------------------
>
>                 Key: CAMEL-22430
>                 URL: https://issues.apache.org/jira/browse/CAMEL-22430
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-file
>    Affects Versions: 4.14.0
>            Reporter: James Netherton
>            Assignee: James Netherton
>            Priority: Minor
>             Fix For: 4.14.1, 4.15.0
>
>
> In its current state, FileLockClusterView is easily 'tricked' into split-brain type scenarios if the cluster lock file or its parent directory is deleted. This can typically happen with NFS / Samba setups.
> In such scenarios, FileLock.isValid() is not always enough to determine the leadership state. It can return true even if the underlying lock file is no longer present. Thus, another process can obtain the lock and start running.
> We can enhance FileLockClusterView so that it can better track the state of the cluster leader, detect staleness and make it more resilient to changes in the file system state.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)