Build failed in Jenkins: kafka-trunk-jdk14 #21

See Changes: [github] MINOR: Partition is under reassignment when adding and removing (#8364) -- [...truncated 6.06 MB...] org.apache.kafka.streams.TopologyTestDriverTest

[jira] [Resolved] (KAFKA-9901) TimeoutError: Never saw message indicating StreamsTest finished startup on ducker@ducker07

[ https://issues.apache.org/jira/browse/KAFKA-9901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiamei xie resolved KAFKA-9901. --- Resolution: Duplicate > TimeoutError: Never saw message indicating StreamsTest finished startup on >

Build failed in Jenkins: kafka-trunk-jdk8 #4470

See Changes: [github] MINOR: Partition is under reassignment when adding and removing (#8364) -- [...truncated 3.01 MB...] org.apache.kafka.streams.TopologyTestDriverTes

[jira] [Created] (KAFKA-9920) Fix NetworkDegradeTest.test_rate test error

jiamei xie created KAFKA-9920: - Summary: Fix NetworkDegradeTest.test_rate test error Key: KAFKA-9920 URL: https://issues.apache.org/jira/browse/KAFKA-9920 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-596 Safely abort Producer transactions during application shutdown

Sorry, but this KIP is still open to discussion, any comments and ideas would be appreciated, Thanks. 张祥 于2020年4月17日周五 下午1:04写道： > Guozhang, thanks for the valuable suggestion. > > A new part called "suggested coding pattern" has been added and I copy the > core code here: > > try { > produc

[jira] [Resolved] (KAFKA-9906) Is bytesSinceLastIndexEntry updated correctly in LogSegment.append()?

[ https://issues.apache.org/jira/browse/KAFKA-9906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiang Zhang resolved KAFKA-9906. Resolution: Not A Problem > Is bytesSinceLastIndexEntry updated correctly in LogSegment.append()? >

Jenkins build is back to normal : kafka-trunk-jdk14 #20

See

Build failed in Jenkins: kafka-trunk-jdk11 #1389

See Changes: [github] MINOR: reduce allocations in log start and recovery checkpoints (#8467) -- [...truncated 3.03 MB...] org.apache.kafka.streams.TopologyTestDriverTe

[jira] [Created] (KAFKA-9919) Add logging to KafkaBasedLog

Chris Egerton created KAFKA-9919: Summary: Add logging to KafkaBasedLog Key: KAFKA-9919 URL: https://issues.apache.org/jira/browse/KAFKA-9919 Project: Kafka Issue Type: Improvement

Build failed in Jenkins: kafka-trunk-jdk8 #4469

See Changes: [github] MINOR: reduce allocations in log start and recovery checkpoints (#8467) -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node env

Re: [DISCUSS] KIP-598: Augment TopologyDescription with store and source / sink serde information

Hi John, Thanks for the review! Replied inline. On Fri, Apr 24, 2020 at 8:09 PM John Roesler wrote: > Hi Guozhang, > > Thanks for the KIP! I took a quick look, and I'm really happy to see this > underway. > > Some quick questions: > > 1. Can you elaborate on the reason that stores just have a

Re: [DISCUSS] KIP-585: Conditional SMT

Hi Andrew, I know a DSL seems like overkill, and I'm not attached to it by any means, but I do think it serves a vital purpose in that it allows people who don't know how or have the time to write Java code to act on data being processed by connectors. Are you proposing that the "RecordPredicate"

Re: [VOTE] KIP-584: Versioning scheme for features

Hi Colin, Thanks for the explanation! I agree with you, and I have updated the KIP. Here is a link to relevant section: https://cwiki.apache.org/confluence/display/KAFKA/KIP-584%3A+Versioning+scheme+for+features#KIP-584:Versioningschemeforfeatures-Controller:ZKnodebootstrapwithdefaultvalues Chee

Re: [Discuss] KIP-582 Add a "continue" option for Kafka Connect error handling

Hi Zihan, Thanks for the changes and the clarifications! I agree that the complexity of maintaining a second topic and a second connector is a fair amount of work; to Andrew's question, it seems less about the cost of just running another connector, and more about managing that second connector (a

Re: [Discuss] KIP-582 Add a "continue" option for Kafka Connect error handling

Hi Zihan, Thanks for the KIP. I have a question about the proposal. Why do you think putting a broken record somewhere other than a dead-letter topic is better? For a reliable system, you really want zero broken records, or perhaps close to zero. Broken records represent exceptions that need to

[jira] [Created] (KAFKA-9918) SslEngineFactory is NOT closed when channel is closing

Chia-Ping Tsai created KAFKA-9918: - Summary: SslEngineFactory is NOT closed when channel is closing Key: KAFKA-9918 URL: https://issues.apache.org/jira/browse/KAFKA-9918 Project: Kafka Issue