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

awsMaxRetries is not working #170

Open
dsinghal-nice opened this issue Apr 19, 2024 · 3 comments
Open

awsMaxRetries is not working #170

dsinghal-nice opened this issue Apr 19, 2024 · 3 comments

Comments

@dsinghal-nice
Copy link

Hello All,

I am using MSK IAM authentication mechanism to authenticate my consumer with MSK cluster and topic, I have added below configuration

software.amazon.msk.auth.iam.IAMLoginModule required awsRoleArn="%s" awsRoleSessionName="%s" awsDebugCreds=%s awsMaxRetries="3";

My assume role arn doesn't have permission for a specific Topic and the kafka consumer throws error for the same only one time, it doesn't tries to retry after default waiting time to again do assume role and check for authorization.

Can you please help me for looking into this use case.

@jvdadda
Copy link
Contributor

jvdadda commented Apr 22, 2024

Hi @dsinghal-nice, you have the problem with which version ? 2.0.x or 2.1.x ? And if you can try with the version that you do not use to target the problem

Thanks

@dsinghal-nice
Copy link
Author

Hi @jvdadda, I am currently using 2.1.0 version I can try with 2.0.0 as well.

@dsinghal-nice
Copy link
Author

Hi @jvdadda, I also noticed one more issue we are assuming role in other account, and suppose the first time it has access to the Topic it will fetch the messages from the broker. (This IAM session lasts long for an hour) Now when we turn off the Topic permission, it starts to throw the Topic Authorization Error immediately after 1-2 mins. But now when I turn back the Topic permission back it doesn't tries to start a new session again and start consuming even after 1 hour of session expiry.

Can you please check if there is any mechanism to handle this issue or is it a bug ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants