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.

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

[Bug][TubeMQ] The updated version causes the consumer group permissions to be abnormal #6579

Closed
1 of 2 tasks
FvvSuu opened this issue Nov 20, 2022 · 3 comments · Fixed by #6597
Closed
1 of 2 tasks
Assignees
Labels
Milestone

Comments

@FvvSuu
Copy link

FvvSuu commented Nov 20, 2022

What happened

The updated version causes the consumer group permissions to be abnormal

What you expected to happen

The consumeEnable of some consumer groups becomes false, and the data cannot be consumed.

How to reproduce

updated version

Environment

No response

InLong version

master

InLong Component

InLong TubeMQ

Are you willing to submit PR?

  • Yes, I am willing to submit a PR!

Code of Conduct

@FvvSuu FvvSuu added the type/bug Something is wrong label Nov 20, 2022
@dockerzhang
Copy link
Contributor

@gosonzhang PTAL, thanks.

@healchow healchow added this to the 1.5.0 milestone Nov 21, 2022
@gosonzhang
Copy link
Contributor

@FvvSuu, thanks

@gosonzhang
Copy link
Contributor

I reproduced this problem in the environment: when adding the authorization information of the consumer group first through the API admin_add_authorized_consumergroup_info, and then adding the filter information of the consumer group throuth the API admin_add_group_filtercond_info, the authorization of the consumer group will be set to STATUS_DISABLE.

The reason for the problem lies in the following implementation points :
image
https://github.com/apache/inlong/blob/master/inlong-tubemq/tubemq-server/src/main/java/org/apache/inlong/tubemq/server/master/metamanage/metastore/impl/AbsConsumeCtrlMapperImpl. java#L86

Then, I found that the field processing of the EnableStatus class is not very good, and I will improve it together.

Thanks @FvvSuu again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment