Unify methods of history tasks in shard component #6868
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Shaddoll
requested review from
neil-xie,
davidporter-id-au,
Groxx,
shijiesheng,
jakobht,
3vilhamster,
sankari165,
dkrotx,
taylanisikdemir and
demirkayaender
as code owners
taylanisikdemir
approved these changes
Apr 29, 2025
| @@ -157,7 +157,7 @@ func NewTimerQueueProcessor( | |||
| status: common.DaemonStatusInitialized, | |||
| shutdownChan: make(chan struct{}), | |||
|
|
|||
| ackLevel: shard.GetTimerAckLevel(), | |||
| ackLevel: shard.GetQueueAckLevel(persistence.HistoryTaskCategoryTimer).ScheduledTime, | |||
There was a problem hiding this comment.
can we move this to Start()?
There was a problem hiding this comment.
I can do it in a separate PR.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Unify methods of history tasks in shard component
Why?
Code refactoring
How did you test it?
unit tests
Potential risks
If there is a mistake, the ack level, read level of history queues will not be retrieved or stored correctly.
Release notes
Documentation Changes