ableegoldman commented on pull request #9489:
URL: https://github.com/apache/kafka/pull/9489#issuecomment-757068925
Cherrypicked to 2.7
This is an automated message from the Apache Git Service.
To respond to the message,
ableegoldman commented on pull request #9489:
URL: https://github.com/apache/kafka/pull/9489#issuecomment-757068925
Cherrypicked to 2.7
This is an automated message from the Apache Git Service.
To respond to the message,
ableegoldman commented on pull request #9489:
URL: https://github.com/apache/kafka/pull/9489#issuecomment-727043278
Merged to trunk. Waiting to cherrypick to 2.7 branch until 2.7.0 release has
completed
This is an automated
ableegoldman commented on pull request #9489:
URL: https://github.com/apache/kafka/pull/9489#issuecomment-727042137
Two flaky tests:
`PurgeRepartitionTopicIntegrationTest.shouldRestoreState`
`SslSelectorTest.testCloseOldestConnection`
ableegoldman commented on pull request #9489:
URL: https://github.com/apache/kafka/pull/9489#issuecomment-725045320
Thoughts? @wcarlson5 @vvcephei @abbccdda
This is an automated message from the Apache Git Service.
To
ableegoldman commented on pull request #9489:
URL: https://github.com/apache/kafka/pull/9489#issuecomment-724391259
That's fair. Ok I'll go forward with demoting this and just add a new
INFO-level log that's less frequent, maybe at the max poll interval
ableegoldman commented on pull request #9489:
URL: https://github.com/apache/kafka/pull/9489#issuecomment-723347370
Eh, I'm going back and forth on this. It's definitely valuable information
to have in the absence of any other logging within the main Streams loop at the
INFO level
ableegoldman commented on pull request #9489:
URL: https://github.com/apache/kafka/pull/9489#issuecomment-715639072
@guozhangwang @vvcephei WDYT? I'm generally all for more logs but this is
pretty extreme
This is an
