Adding more permits debug statements to better diagnose permit issues - #10217
Conversation
|
@merlimat @eolivelli Since it's not easy to get debug logs from functions due to #3259, I added more logs to the broker instead. |
|
@devinbost There are few checkstyle violations reported in the CI jobs: |
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
1 similar comment
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
2 similar comments
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
|
@lhotari are you okay with this PR now ? |
|
/pulsarbot run-failure-checks |
@devinbost please rebase your changes. The master branch contains fixes to CI issues. |
…e changes to permits
baa53fc to
14a5c84
Compare
|
/pulsarbot run-failure-checks |
|
Looks like we missed a flaky test. @lhotari [INFO] |
|
/pulsarbot run-failure-checks |
3 similar comments
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
|
I am trying to cherry pick to branch-7.2 and see if it builds properly |
|
@devinbost picked to branch-2.7 as c243d18 |
@devinbost this is fixed in #10248 |
This PR just adds debug statements whenever the broker updates its permits in
broker.service.Consumerand inPersistentDispatcherMultipleConsumers. It also adds batch sizes to some of the debug log statements.That will help with the forensic analysis of problematic permit behavior.