Camel
  1. Camel
  2. CAMEL-4271

jdbc aggregation repository - recovery taks and cluster issue

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.8.0
    • Fix Version/s: Future
    • Component/s: camel-core, camel-sql
    • Labels:
      None

      Description

      If you enable recovery on the aggregator eip when using a persistent repository such as the jdbc, then you may have a race condition when having multiple camel apps running in a cluster. As the aggregate recover task is running on each Camel app (node) in the cluster. So they may potentially all pickup recovery tasks, and execute those, which may cause duplicate messages being recovered.

      What is needed is a lock table or some other way to ensure only one recover tasks "wins" and executes.

      We may want to enhance the API in camel to facilitate this kind of locking. As with hawtdb you may have a shared file on the SAN and thus have the same racing issue.

        Issue Links

          Activity

          Claus Ibsen created issue -
          Ben D'Herville made changes -
          Field Original Value New Value
          Link This issue relates to CAMEL-8010 [ CAMEL-8010 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Claus Ibsen
            • Votes:
              6 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Development