[jira] [Resolved] (CAMEL-12382) FileConsumer - Allow to delay readLock release tasks on idempotent read-lock

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

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

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

> FileConsumer - Allow to delay readLock release tasks on idempotent read-lock
> ----------------------------------------------------------------------------
>
>                 Key: CAMEL-12382
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12382
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 2.22.0
>
>
> Under certain use-cases where you may use a shared file read-lock idempotent repository for a active/active cluster setup of consuming files from a shared directory, then you may have the idempotent repo setup as readlock strategy. And in this scenario you may want to delay the commit/rollback operation at the end, to expand the processing windows of the given file to avoid other nodes to potentially be able to pickup the file as well.
> This requires both a sync vs async way. So users can setup a scheduled thread pool that can delay the work for the commit/rollback so the same node can continue processing the next file.
> By default this should be turned off.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)