[
https://issues.apache.org/jira/browse/CAMEL-10448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-10448.
---------------------------------
Resolution: Fixed
> File read lock - idempotent and change/rename should be possible
> ----------------------------------------------------------------
>
> Key: CAMEL-10448
> URL: https://issues.apache.org/jira/browse/CAMEL-10448
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.19.0
>
>
> Camel readlock strategy in cluster
> ==================================
> Hi Claus,
> We are trying to move to cluster with Apache Camel. So far we had it on one
> node and worked well.
> One node: I have readlock strategy set to 'changed' which keeps track of file
> changes with camelLock file and only when the file has finished downloading,
> it will be picked up for processing. But camel readlock strategy 'changed' is
> discouraged in clustering. According to the camel documentation 'idempotent'
> is recommended. This is what happens when I am testing with 5GB file.
> Two nodes: I have readlock strategy set to 'idempotent' which distributes
> files to one of the nodes but camel starts processing the file even before
> the file has finished downloading.
> Is there a way to stop camel from processing even before file has downloaded
> when readlock strategy is idempotent?
> Thanks.
> -------------------
> We should allow to use idempontent-changed and idempontent-rename as options
> as well so its a combination of the two of them.
> Then it should acquire idempotent first, and then try changed or rename
> afterwards.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
