You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@inlong.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/07/28 12:10:01 UTC
[jira] [Updated] (INLONG-372) Is there any strategy to ensure
consumer start up smoothly
[ https://issues.apache.org/jira/browse/INLONG-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated INLONG-372:
----------------------------------
Labels: pull-request-available (was: )
> Is there any strategy to ensure consumer start up smoothly
> ----------------------------------------------------------
>
> Key: INLONG-372
> URL: https://issues.apache.org/jira/browse/INLONG-372
> Project: Apache InLong
> Issue Type: Improvement
> Components: inlong-tubemq
> Reporter: dashuye4
> Priority: Major
> Labels: pull-request-available
> Attachments: 89bd93bb-fbb0-4d10-ad00-cbdbb0728894.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Nowadays I have encounter a problem when start up tube consumer from failover client，
> by telling me the inconsistent session key I configured.
> !89bd93bb-fbb0-4d10-ad00-cbdbb0728894.png|width=1463,height=109!
> After searching around, this may caused by the zombie consumer process which does not exit successfully from last session under the same consume group.
> My question is: are there any solutions for user-friendly start up from unexpected failover.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)