[jira] [Commented] (KAFKA-9259) suppress() for windowed-Serdes does not work with default serdes

[ https://issues.apache.org/jira/browse/KAFKA-9259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997447#comment-16997447 ] John Roesler commented on KAFKA-9259: - Hi [~omanges], yes, of course! Although this work doesn't

[jira] [Commented] (KAFKA-9302) Allow custom partitioning in foreign-key joins

[ https://issues.apache.org/jira/browse/KAFKA-9302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997432#comment-16997432 ] John Roesler commented on KAFKA-9302: - Thanks for the report, [~mjsax]. It also comes to mind that we

[jira] [Resolved] (KAFKA-9138) Add system test covering Foreign Key joins (KIP-213)

[ https://issues.apache.org/jira/browse/KAFKA-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-9138. - Resolution: Fixed Added the system test in

[jira] [Commented] (KAFKA-6078) Investigate failure of ReassignPartitionsClusterTest.shouldExpandCluster

[ https://issues.apache.org/jira/browse/KAFKA-6078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16993754#comment-16993754 ] John Roesler commented on KAFKA-6078: - This had just failed for me on

[jira] [Commented] (KAFKA-9289) consolidate all the streams smoke system tests

[ https://issues.apache.org/jira/browse/KAFKA-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16992681#comment-16992681 ] John Roesler commented on KAFKA-9289: - See

[jira] [Updated] (KAFKA-9289) consolidate all the streams smoke system tests

[ https://issues.apache.org/jira/browse/KAFKA-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9289: Labels: system-tests (was: ) > consolidate all the streams smoke system tests >

[jira] [Created] (KAFKA-9289) consolidate all the streams smoke system tests

John Roesler created KAFKA-9289: --- Summary: consolidate all the streams smoke system tests Key: KAFKA-9289 URL: https://issues.apache.org/jira/browse/KAFKA-9289 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-9234) Consider using @Nullable and @Nonnull annotations

[ https://issues.apache.org/jira/browse/KAFKA-9234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990681#comment-16990681 ] John Roesler commented on KAFKA-9234: - Hi [~hmed06], The answer is yes, you can just assign any

[jira] [Commented] (KAFKA-9034) kafka-run-class.sh will fail if JAVA_HOME has space

[ https://issues.apache.org/jira/browse/KAFKA-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990678#comment-16990678 ] John Roesler commented on KAFKA-9034: - Either way, it would be a best practice to quote bash

[jira] [Commented] (KAFKA-9275) Print assignment and IP address in the log message when consumer leaves/removed from the group

[ https://issues.apache.org/jira/browse/KAFKA-9275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990553#comment-16990553 ] John Roesler commented on KAFKA-9275: - Yeah, to be honest, I was a little concerned about printing

[jira] [Commented] (KAFKA-9275) Print assignment and IP address in the log message when consumer leaves/removed from the group

[ https://issues.apache.org/jira/browse/KAFKA-9275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990311#comment-16990311 ] John Roesler commented on KAFKA-9275: - Hi [~dengziming], It looks like you should be able to assign

[jira] [Commented] (KAFKA-9274) Gracefully handle timeout exceptions on Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-9274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989980#comment-16989980 ] John Roesler commented on KAFKA-9274: - Yep, something like that is what I would propose, although,

[jira] [Commented] (KAFKA-9270) KafkaStream crash on offset commit failure

[ https://issues.apache.org/jira/browse/KAFKA-9270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989968#comment-16989968 ] John Roesler commented on KAFKA-9270: - Hi [~rohan26may], No problem. I was actually referring to

[jira] [Commented] (KAFKA-9270) KafkaStream crash on offset commit failure

[ https://issues.apache.org/jira/browse/KAFKA-9270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989401#comment-16989401 ] John Roesler commented on KAFKA-9270: - Hey Rohan, I see where you’re coming from, but I definitely

[jira] [Commented] (KAFKA-9225) kafka fail to run on linux-aarch64

[ https://issues.apache.org/jira/browse/KAFKA-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989225#comment-16989225 ] John Roesler commented on KAFKA-9225: - I see what you did there :) Forking RocksDB is also a viable

[jira] [Commented] (KAFKA-9225) kafka fail to run on linux-aarch64

[ https://issues.apache.org/jira/browse/KAFKA-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989201#comment-16989201 ] John Roesler commented on KAFKA-9225: - Hey [~guozhang], Yes, I think it would be ok to plan to

[jira] [Comment Edited] (KAFKA-9274) Gracefully handle timeout exceptions on Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-9274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989195#comment-16989195 ] John Roesler edited comment on KAFKA-9274 at 12/5/19 9:47 PM: -- Thanks for

[jira] [Commented] (KAFKA-9274) Gracefully handle timeout exceptions on Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-9274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989195#comment-16989195 ] John Roesler commented on KAFKA-9274: - Thanks for starting this, [~bchen225242]! One thing we should

[jira] [Commented] (KAFKA-9270) KafkaStream crash on offset commit failure

[ https://issues.apache.org/jira/browse/KAFKA-9270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989123#comment-16989123 ] John Roesler commented on KAFKA-9270: - Agreed, [~bchen225242], and I'm actually on board with your

[jira] [Commented] (KAFKA-9268) Follow-on: Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988953#comment-16988953 ] John Roesler commented on KAFKA-9268: - The only compatibility concern I'm aware of is that 2.2.1+

[jira] [Commented] (KAFKA-9270) KafkaStream crash on offset commit failure

[ https://issues.apache.org/jira/browse/KAFKA-9270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988923#comment-16988923 ] John Roesler commented on KAFKA-9270: - Hey Rohan, There is a Consumer config to control how long it

[jira] [Commented] (KAFKA-9088) Consolidate InternalMockProcessorContext and MockInternalProcessorContext

[ https://issues.apache.org/jira/browse/KAFKA-9088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988913#comment-16988913 ] John Roesler commented on KAFKA-9088: - Thanks, Bruno, I don’t want you to feel besieged. It seems

[jira] [Commented] (KAFKA-9231) Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987992#comment-16987992 ] John Roesler commented on KAFKA-9231: - Opened https://issues.apache.org/jira/browse/KAFKA-9268 as a

[jira] [Updated] (KAFKA-9268) Follow-on: Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9268: Description: While testing Streams in EOS mode under frequent and heavy network partitions, I've

[jira] [Updated] (KAFKA-9268) Follow-on: Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9268: Attachment: 2.2-eos-failures-1.txt 2.2-eos-failures-2.txt > Follow-on: Streams

[jira] [Assigned] (KAFKA-9268) Follow-on: Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reassigned KAFKA-9268: --- Assignee: (was: John Roesler) > Follow-on: Streams Threads may die from recoverable

[jira] [Updated] (KAFKA-9268) Follow-on: Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9268: Description: While testing Streams in EOS mode under frequent and heavy network partitions, I've

[jira] [Updated] (KAFKA-9268) Follow-on: Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9268: Affects Version/s: (was: 2.4.0) 2.2.0 > Follow-on: Streams Threads may

[jira] [Updated] (KAFKA-9268) Follow-on: Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9268: Priority: Major (was: Blocker) > Follow-on: Streams Threads may die from recoverable errors with

[jira] [Created] (KAFKA-9268) Follow-on: Streams Threads may die from recoverable errors with EOS enabled

John Roesler created KAFKA-9268: --- Summary: Follow-on: Streams Threads may die from recoverable errors with EOS enabled Key: KAFKA-9268 URL: https://issues.apache.org/jira/browse/KAFKA-9268 Project:

[jira] [Commented] (KAFKA-9088) Consolidate InternalMockProcessorContext and MockInternalProcessorContext

[ https://issues.apache.org/jira/browse/KAFKA-9088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987985#comment-16987985 ] John Roesler commented on KAFKA-9088: - Thanks for the justification, [~cadonna]. Since the classes

[jira] [Commented] (KAFKA-9225) kafka fail to run on linux-aarch64

[ https://issues.apache.org/jira/browse/KAFKA-9225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987953#comment-16987953 ] John Roesler commented on KAFKA-9225: - When we discussed this before, we didn’t have the

[jira] [Commented] (KAFKA-9088) Consolidate InternalMockProcessorContext and MockInternalProcessorContext

[ https://issues.apache.org/jira/browse/KAFKA-9088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987478#comment-16987478 ] John Roesler commented on KAFKA-9088: - Hey all, I can see I've missed some discussions here. I've

[jira] [Comment Edited] (KAFKA-9231) Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987395#comment-16987395 ] John Roesler edited comment on KAFKA-9231 at 12/4/19 1:14 AM: -- Fixed in 2.4

[jira] [Resolved] (KAFKA-9231) Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-9231. - Resolution: Fixed Fixed in 2.4 by

[jira] [Commented] (KAFKA-6718) Rack Aware Stand-by Task Assignment for Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987281#comment-16987281 ] John Roesler commented on KAFKA-6718: - Hey [~lkokhreidze]. I know Matthias pinged me a while back...

[jira] [Updated] (KAFKA-9263) Reocurrence: Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs

[ https://issues.apache.org/jira/browse/KAFKA-9263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9263: Affects Version/s: 2.4.0 > Reocurrence: Transient failure in >

[jira] [Updated] (KAFKA-9263) Reocurrence: Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs

[ https://issues.apache.org/jira/browse/KAFKA-9263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9263: Fix Version/s: (was: 1.1.0) > Reocurrence: Transient failure in >

[jira] [Updated] (KAFKA-9264) Reocurrence: Flaky Test DelegationTokenEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

[ https://issues.apache.org/jira/browse/KAFKA-9264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9264: Reporter: John Roesler (was: Matthias J. Sax) > Reocurrence: Flaky Test >

[jira] [Updated] (KAFKA-9263) Reocurrence: Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs

[ https://issues.apache.org/jira/browse/KAFKA-9263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9263: Description: This test has failed for me on

[jira] [Assigned] (KAFKA-9263) Reocurrence: Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs

[ https://issues.apache.org/jira/browse/KAFKA-9263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reassigned KAFKA-9263: --- Assignee: (was: Dong Lin) > Reocurrence: Transient failure in >

[jira] [Updated] (KAFKA-9263) Reocurrence: Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs

[ https://issues.apache.org/jira/browse/KAFKA-9263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9263: Reporter: John Roesler (was: Guozhang Wang) > Reocurrence: Transient failure in >

[jira] [Updated] (KAFKA-9263) Reocurrence: Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs

[ https://issues.apache.org/jira/browse/KAFKA-9263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9263: Component/s: (was: unit tests) clients > Reocurrence: Transient failure in >

[jira] [Updated] (KAFKA-9263) Reocurrence: Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs

[ https://issues.apache.org/jira/browse/KAFKA-9263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9263: Labels: flaky-test (was: ) > Reocurrence: Transient failure in >

[jira] [Created] (KAFKA-9263) Reocurrence: Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs

John Roesler created KAFKA-9263: --- Summary: Reocurrence: Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs Key: KAFKA-9263

[jira] [Updated] (KAFKA-9263) Reocurrence: Transient failure in kafka.api.AdminClientIntegrationTest.testLogStartOffsetCheckpointkafka.api.AdminClientIntegrationTest.testAlterReplicaLogDirs

[ https://issues.apache.org/jira/browse/KAFKA-9263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9263: Description: This test has failed for me on

[jira] [Updated] (KAFKA-9264) Reocurrence: Flaky Test DelegationTokenEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

[ https://issues.apache.org/jira/browse/KAFKA-9264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9264: Description: This test has failed again for me, so apparently it's not fixed:

[jira] [Created] (KAFKA-9264) Reocurrence: Flaky Test DelegationTokenEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

John Roesler created KAFKA-9264: --- Summary: Reocurrence: Flaky Test DelegationTokenEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl Key: KAFKA-9264 URL:

[jira] [Reopened] (KAFKA-8937) Flaky Test SaslPlainSslEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

[ https://issues.apache.org/jira/browse/KAFKA-8937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reopened KAFKA-8937: - This test has just failed again for me. Apparently, it is not fixed. Unfortunately, Jenkins didn't

[jira] [Commented] (KAFKA-9259) suppress() for windowed-Serdes does not work with default serdes

[ https://issues.apache.org/jira/browse/KAFKA-9259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986546#comment-16986546 ] John Roesler commented on KAFKA-9259: - Thanks for the report, [~mjsax]! Just a quick additional note

[jira] [Comment Edited] (KAFKA-9231) Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985429#comment-16985429 ] John Roesler edited comment on KAFKA-9231 at 11/30/19 8:32 PM: --- In addition

[jira] [Updated] (KAFKA-9231) Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9231: Priority: Blocker (was: Major) > Streams Threads may die from recoverable errors with EOS enabled

[jira] [Commented] (KAFKA-9231) Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16985429#comment-16985429 ] John Roesler commented on KAFKA-9231: - In addition to the error I listed above

[jira] [Updated] (KAFKA-9231) Streams Threads may die from recoverable errors with EOS enabled

[ https://issues.apache.org/jira/browse/KAFKA-9231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9231: Summary: Streams Threads may die from recoverable errors with EOS enabled (was:

[jira] [Commented] (KAFKA-8769) Consider computing stream time independently per key

[ https://issues.apache.org/jira/browse/KAFKA-8769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16983091#comment-16983091 ] John Roesler commented on KAFKA-8769: - Yes, that is a problem. It’s why I mentioned the “low-traffic”

[jira] [Created] (KAFKA-9231) ProducerFencedException may cause Streams Thread to die

John Roesler created KAFKA-9231: --- Summary: ProducerFencedException may cause Streams Thread to die Key: KAFKA-9231 URL: https://issues.apache.org/jira/browse/KAFKA-9231 Project: Kafka Issue

[jira] [Commented] (KAFKA-7663) Custom Processor supplied on addGlobalStore is not used when restoring state from topic

[ https://issues.apache.org/jira/browse/KAFKA-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16981693#comment-16981693 ] John Roesler commented on KAFKA-7663: - Hey, all, I just became aware of this ticket via another SO

[jira] [Updated] (KAFKA-7663) Custom Processor supplied on addGlobalStore is not used when restoring state from topic

[ https://issues.apache.org/jira/browse/KAFKA-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-7663: Issue Type: Improvement (was: Bug) > Custom Processor supplied on addGlobalStore is not used when

[jira] [Commented] (KAFKA-7940) Flaky Test CustomQuotaCallbackTest#testCustomQuotaCallback

[ https://issues.apache.org/jira/browse/KAFKA-7940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980512#comment-16980512 ] John Roesler commented on KAFKA-7940: - Failed again in https://github.com/apache/kafka/pull/7722 on

[jira] [Commented] (KAFKA-9222) StreamPartitioner for internal repartition topics does not match defaults for to() operation

[ https://issues.apache.org/jira/browse/KAFKA-9222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16979700#comment-16979700 ] John Roesler commented on KAFKA-9222: - Thanks for the report! It does sound like a bug in the

[jira] [Commented] (KAFKA-9169) Standby Tasks point ask for incorrect offsets on resuming post suspension

[ https://issues.apache.org/jira/browse/KAFKA-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16975723#comment-16975723 ] John Roesler commented on KAFKA-9169: - Thanks, Navinder. I’ve set the affected version field to 1.1.0

[jira] [Updated] (KAFKA-9169) Standby Tasks point ask for incorrect offsets on resuming post suspension

[ https://issues.apache.org/jira/browse/KAFKA-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9169: Affects Version/s: (was: 2.3.0) 1.1.0 > Standby Tasks point ask for

[jira] [Commented] (KAFKA-9169) Standby Tasks point ask for incorrect offsets on resuming post suspension

[ https://issues.apache.org/jira/browse/KAFKA-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16974430#comment-16974430 ] John Roesler commented on KAFKA-9169: - Aha, that makes more sense... Thanks, [~mjsax] n.b., 2.3.0 is

[jira] [Resolved] (KAFKA-9169) Standby Tasks point ask for incorrect offsets on resuming post suspension

[ https://issues.apache.org/jira/browse/KAFKA-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-9169. - Resolution: Fixed This was fixed in https://github.com/apache/kafka/pull/7681/ and merged to

[jira] [Updated] (KAFKA-9169) Standby Tasks point ask for incorrect offsets on resuming post suspension

[ https://issues.apache.org/jira/browse/KAFKA-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9169: Fix Version/s: 2.5.0 > Standby Tasks point ask for incorrect offsets on resuming post suspension >

[jira] [Commented] (KAFKA-9169) Standby Tasks point ask for incorrect offsets on resuming post suspension

[ https://issues.apache.org/jira/browse/KAFKA-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16972911#comment-16972911 ] John Roesler commented on KAFKA-9169: - After testing, I've determined that the bug is pre-existing in

[jira] [Updated] (KAFKA-9169) Standby Tasks point ask for incorrect offsets on resuming post suspension

[ https://issues.apache.org/jira/browse/KAFKA-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9169: Affects Version/s: 2.3.2 2.3.1 2.3.0 > Standby Tasks

[jira] [Updated] (KAFKA-9169) Standby Tasks point ask for incorrect offsets on resuming post suspension

[ https://issues.apache.org/jira/browse/KAFKA-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9169: Priority: Critical (was: Blocker) > Standby Tasks point ask for incorrect offsets on resuming

[jira] [Updated] (KAFKA-9169) Standby Tasks point ask for incorrect offsets on resuming post suspension

[ https://issues.apache.org/jira/browse/KAFKA-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9169: Priority: Blocker (was: Critical) > Standby Tasks point ask for incorrect offsets on resuming

[jira] [Updated] (KAFKA-9169) Standby Tasks point ask for incorrect offsets on resuming post suspension

[ https://issues.apache.org/jira/browse/KAFKA-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9169: Affects Version/s: 2.4.0 > Standby Tasks point ask for incorrect offsets on resuming post

[jira] [Updated] (KAFKA-9169) Standby Tasks point ask for incorrect offsets on resuming post suspension

[ https://issues.apache.org/jira/browse/KAFKA-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9169: Issue Type: Bug (was: New Feature) > Standby Tasks point ask for incorrect offsets on resuming

[jira] [Assigned] (KAFKA-9169) Standby Tasks point ask for incorrect offsets on resuming post suspension

[ https://issues.apache.org/jira/browse/KAFKA-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reassigned KAFKA-9169: --- Assignee: John Roesler > Standby Tasks point ask for incorrect offsets on resuming post

[jira] [Commented] (KAFKA-9134) Refactor the StreamsPartitionAssignor for more code sharing with the FutureStreamsPartitionAssignor

[ https://issues.apache.org/jira/browse/KAFKA-9134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969829#comment-16969829 ] John Roesler commented on KAFKA-9134: - Thanks for calling this out [~ableegoldman]. Recently, while

[jira] [Assigned] (KAFKA-7895) Ktable supress operator emitting more than one record for the same key per window

[ https://issues.apache.org/jira/browse/KAFKA-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reassigned KAFKA-7895: --- Assignee: John Roesler (was: Guozhang Wang) > Ktable supress operator emitting more than

[jira] [Assigned] (KAFKA-7895) Ktable supress operator emitting more than one record for the same key per window

[ https://issues.apache.org/jira/browse/KAFKA-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reassigned KAFKA-7895: --- Assignee: Guozhang Wang (was: John Roesler) > Ktable supress operator emitting more than

[jira] [Commented] (KAFKA-9148) Consider forking RocksDB for Streams

[ https://issues.apache.org/jira/browse/KAFKA-9148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968534#comment-16968534 ] John Roesler commented on KAFKA-9148: - Thanks for the additional detail. I had one other (probably

[jira] [Commented] (KAFKA-9148) Consider forking RocksDB for Streams

[ https://issues.apache.org/jira/browse/KAFKA-9148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968097#comment-16968097 ] John Roesler commented on KAFKA-9148: - Thanks for bringing this up, Sophie. It does seem like this

[jira] [Created] (KAFKA-9138) Add system test covering Foreign Key joins (KIP-213)

John Roesler created KAFKA-9138: --- Summary: Add system test covering Foreign Key joins (KIP-213) Key: KAFKA-9138 URL: https://issues.apache.org/jira/browse/KAFKA-9138 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-9103) KIP-441: Add TaskLags to SubscriptionInfo

John Roesler created KAFKA-9103: --- Summary: KIP-441: Add TaskLags to SubscriptionInfo Key: KAFKA-9103 URL: https://issues.apache.org/jira/browse/KAFKA-9103 Project: Kafka Issue Type:

[jira] [Assigned] (KAFKA-8410) Strengthen the types of Processors, at least in the DSL, maybe in the PAPI as well

[ https://issues.apache.org/jira/browse/KAFKA-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reassigned KAFKA-8410: --- Assignee: John Roesler > Strengthen the types of Processors, at least in the DSL, maybe in

[jira] [Comment Edited] (KAFKA-8882) It's not possible to restart Kafka Streams using StateListener

[ https://issues.apache.org/jira/browse/KAFKA-8882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954815#comment-16954815 ] John Roesler edited comment on KAFKA-8882 at 10/18/19 5:03 PM: --- Hey

[jira] [Commented] (KAFKA-8882) It's not possible to restart Kafka Streams using StateListener

[ https://issues.apache.org/jira/browse/KAFKA-8882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954815#comment-16954815 ] John Roesler commented on KAFKA-8882: - Hey [~cjub], Sorry I didn't reply! It seems like the "unable

[jira] [Resolved] (KAFKA-8902) Benchmark cooperative vs eager rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-8902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-8902. - Resolution: Fixed I wrote a simple Streams application using the Processor API to update 10

[jira] [Created] (KAFKA-9058) Foreign Key Join should not require a queriable store

John Roesler created KAFKA-9058: --- Summary: Foreign Key Join should not require a queriable store Key: KAFKA-9058 URL: https://issues.apache.org/jira/browse/KAFKA-9058 Project: Kafka Issue

[jira] [Commented] (KAFKA-9022) Flaky Test KTableKTableForeignKeyJoinIntegrationTest. doInnerJoinFilterOutRapidlyChangingForeignKeyValues

[ https://issues.apache.org/jira/browse/KAFKA-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952184#comment-16952184 ] John Roesler commented on KAFKA-9022: - It isn't a true duplicate, but both flaky tests have the same

[jira] [Resolved] (KAFKA-9022) Flaky Test KTableKTableForeignKeyJoinIntegrationTest. doInnerJoinFilterOutRapidlyChangingForeignKeyValues

[ https://issues.apache.org/jira/browse/KAFKA-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-9022. - Resolution: Duplicate > Flaky Test KTableKTableForeignKeyJoinIntegrationTest. >

[jira] [Commented] (KAFKA-9032) Serializer is invoked with null when foreignValue=null

[ https://issues.apache.org/jira/browse/KAFKA-9032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951519#comment-16951519 ] John Roesler commented on KAFKA-9032: - I'll pick this one up. I've reproduced the issue. The root

[jira] [Updated] (KAFKA-9000) Flaky Test KTableKTableForeignKeyJoinIntegrationTest.doLeftJoinFromRightThenDeleteRightEntity

[ https://issues.apache.org/jira/browse/KAFKA-9000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9000: Priority: Blocker (was: Major) > Flaky Test >

[jira] [Updated] (KAFKA-9000) Flaky Test KTableKTableForeignKeyJoinIntegrationTest.doLeftJoinFromRightThenDeleteRightEntity

[ https://issues.apache.org/jira/browse/KAFKA-9000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler updated KAFKA-9000: Affects Version/s: 2.4.0 > Flaky Test >

[jira] [Assigned] (KAFKA-9032) Serializer is invoked with null when foreignValue=null

[ https://issues.apache.org/jira/browse/KAFKA-9032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reassigned KAFKA-9032: --- Assignee: John Roesler > Serializer is invoked with null when foreignValue=null >

[jira] [Commented] (KAFKA-9006) Flaky Test KTableKTableForeignKeyJoinIntegrationTest.doLeftJoinFilterOutRapidlyChangingForeignKeyValues

[ https://issues.apache.org/jira/browse/KAFKA-9006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951517#comment-16951517 ] John Roesler commented on KAFKA-9006: - It isn't a true duplicate, but both flaky tests have the same

[jira] [Resolved] (KAFKA-9006) Flaky Test KTableKTableForeignKeyJoinIntegrationTest.doLeftJoinFilterOutRapidlyChangingForeignKeyValues

[ https://issues.apache.org/jira/browse/KAFKA-9006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-9006. - Resolution: Duplicate > Flaky Test >

[jira] [Assigned] (KAFKA-9000) Flaky Test KTableKTableForeignKeyJoinIntegrationTest.doLeftJoinFromRightThenDeleteRightEntity

[ https://issues.apache.org/jira/browse/KAFKA-9000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reassigned KAFKA-9000: --- Assignee: John Roesler > Flaky Test >

[jira] [Assigned] (KAFKA-9006) Flaky Test KTableKTableForeignKeyJoinIntegrationTest.doLeftJoinFilterOutRapidlyChangingForeignKeyValues

[ https://issues.apache.org/jira/browse/KAFKA-9006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reassigned KAFKA-9006: --- Assignee: John Roesler > Flaky Test >

[jira] [Assigned] (KAFKA-9006) Flaky Test KTableKTableForeignKeyJoinIntegrationTest.doLeftJoinFilterOutRapidlyChangingForeignKeyValues

[ https://issues.apache.org/jira/browse/KAFKA-9006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reassigned KAFKA-9006: --- Assignee: (was: John Roesler) > Flaky Test >

[jira] [Assigned] (KAFKA-8940) Flaky Test SmokeTestDriverIntegrationTest.shouldWorkWithRebalance

[ https://issues.apache.org/jira/browse/KAFKA-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reassigned KAFKA-8940: --- Assignee: John Roesler > Flaky Test SmokeTestDriverIntegrationTest.shouldWorkWithRebalance

[jira] [Assigned] (KAFKA-9006) Flaky Test KTableKTableForeignKeyJoinIntegrationTest.doLeftJoinFilterOutRapidlyChangingForeignKeyValues

[ https://issues.apache.org/jira/browse/KAFKA-9006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler reassigned KAFKA-9006: --- Assignee: John Roesler > Flaky Test >

[jira] [Commented] (KAFKA-8970) StateDirectory creation fails with Exception

[ https://issues.apache.org/jira/browse/KAFKA-8970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944039#comment-16944039 ] John Roesler commented on KAFKA-8970: - Also, do you mean you are trying to run two instances of

[jira] [Commented] (KAFKA-8690) Flakey test ConnectWorkerIntegrationTest#testAddAndRemoveWorke

[ https://issues.apache.org/jira/browse/KAFKA-8690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16943865#comment-16943865 ] John Roesler commented on KAFKA-8690: - Note: this test failed for all three builds on

[jira] [Commented] (KAFKA-8613) Set default grace period to 0

[ https://issues.apache.org/jira/browse/KAFKA-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16936172#comment-16936172 ] John Roesler commented on KAFKA-8613: - Hey [~cadonna], I just learned of this ticket from the

<    4   5   6   7   8   9   10   11   12   13   >