-
Notifications
You must be signed in to change notification settings - Fork 14k
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
KAFKA-5173: Log jaas.config if broker fails to start #2985
Conversation
Refer to this link for build results (access rights to CI server needed): |
2c2963f
to
80c841d
Compare
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
The additional logging:
|
I think it's a case of not clearing the cached |
65f5c18
to
adbc0fd
Compare
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
retest this please |
@ijuma Can you take a look at this? Thanks. While running tests locally, I found three threads being left behind by the broker after shutdown. This could be one cause for failures in time-sensitve tests like the quota tests that are failing fairly frequently now. As far as I can tell, these threads should never be reloading JAAS config, so they are unlikely to be causing the jaas.config issue. The PR logs JAAS sections and thread stack traces on failure. The last set of tests passed, I am waiting for a failure to see the thread dump. |
@rajinisivaram, your thread leak changes look good. Maybe submit them as a separate PR? |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
@ijuma Yes, will do that under KAFKA-5182. Thanks. |
retest this please |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
retest this please |
Closing this PR. Thread leak was fixed under #3014. JAAS config logging isn't necessary since none of the issues found were related to JAAS config being incorrect. Instead of thread dump on failure, PR #3026 fails if broker controller has not been shutdown. This is better since thread dump at the time of failure will not provide any indication about which tests may have caused the thread leak. |
Refer to this link for build results (access rights to CI server needed): |
No description provided.