You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Otavio Rodolfo Piske (Jira)" <ji...@apache.org> on 2022/03/16 17:29:00 UTC

[jira] [Updated] (CAMEL-17810) camel-resume-api: improve behavior with the master-component

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

Otavio Rodolfo Piske updated CAMEL-17810:
-----------------------------------------
    Description: 
The lifecycle of the resume strategy likely initializes too soon, which causes it to not respect the lifecycle of the master component. This causes it to load offsets too early and have outdated offsets if the primary node goes down and the secondary node goes up.

 

Possible solutions to investigate:
 * initialize along w/ the component
 * allow the components to reload the offsets on demand
 * add a listener on the cluster view, so offsets can be reloaded transparently when the leadership is obtained

  was:
The lifecycle of the resume strategy likely initializes too soon, which causes it to not respect the lifecycle of the master component. This causes it to load offsets too early and have outdated offsets if the primary node goes down and the secondary node goes up.

 

Likely, it may need to initialize along w/ the component OR reload the offsets.


> camel-resume-api: improve behavior with the master-component
> ------------------------------------------------------------
>
>                 Key: CAMEL-17810
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17810
>             Project: Camel
>          Issue Type: Task
>          Components: camel-master, camel-resume-api
>    Affects Versions: 3.17.0
>            Reporter: Otavio Rodolfo Piske
>            Assignee: Otavio Rodolfo Piske
>            Priority: Major
>
> The lifecycle of the resume strategy likely initializes too soon, which causes it to not respect the lifecycle of the master component. This causes it to load offsets too early and have outdated offsets if the primary node goes down and the secondary node goes up.
>  
> Possible solutions to investigate:
>  * initialize along w/ the component
>  * allow the components to reload the offsets on demand
>  * add a listener on the cluster view, so offsets can be reloaded transparently when the leadership is obtained



--
This message was sent by Atlassian Jira
(v8.20.1#820001)