[CAMEL-10448] File read lock - idempotent and change/rename should be possible

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.19.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 07/Nov/16 08:46
• Updated: 07/Nov/16 09:28
• Resolved: 07/Nov/16 09:28

Description

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.