[
https://issues.apache.org/jira/browse/TUBEMQ-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041660#comment-17041660
]
Guocheng Zhang commented on TUBEMQ-37:
--------------------------------------
Cause of the problem: When the Broker is offline, it will call close () to
close the service. During the close process of the Broker, the consumer
initiates a business call, it will call loadOffset () to load the offset and
check whether current offset over the maximum value. Because relevant
parameters (such as writeIndexStartPos and cacheIndexSize) have been cleared,
the maximum value pulled by calling getIndexLastWritePos () or
getDataLastWritePos () is 0, and it caused the offset to be set to 0.
I'll fix it.
> Offset is set to 0 when Broker goes offline
> -------------------------------------------
>
> Key: TUBEMQ-37
> URL: https://issues.apache.org/jira/browse/TUBEMQ-37
> Project: Apache TubeMQ
> Issue Type: Bug
> Reporter: Guocheng Zhang
> Assignee: Guocheng Zhang
> Priority: Major
>
> When Broker shuts down and goes offline, there is a certain chance that the
> offset of the consumer group is set to 0
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
