Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[#ISSUE 8066] Fix tiered storage skip dispatch and destroy when broker role is Slave #8067

Closed
wants to merge 0 commits into from
Closed

[#ISSUE 8066] Fix tiered storage skip dispatch and destroy when broker role is Slave #8067

wants to merge 0 commits into from

Conversation

bxfjb
Copy link
Contributor

@bxfjb bxfjb commented Apr 25, 2024

Which Issue(s) This PR Fixes

Fixes #8066

Brief Description

How Did You Test This Change?

@bxfjb bxfjb changed the title fix tiered storage skip dispatch and destroy when broker role is Slave [#ISSUE 8066] Fix tiered storage skip dispatch and destroy when broker role is Slave Apr 25, 2024
@bxfjb bxfjb closed this Apr 26, 2024
@bxfjb bxfjb force-pushed the fix-tiered-data-collision branch from 95e27b9 to b37d283 Compare April 26, 2024 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[Enhancement] Support tiered storage run in primary/backup mode
1 participant
@bxfjb