Re: [DISCUSS] KIP-399: Extend ProductionExceptionHandler to cover serialization exceptions

Walker, thanks for picking up this KIP. Did you read the previous discussion? It's still unclear if we want to apply the handler to repartition topics or not, and how errors for stores and changelog topic should be handled. For the Processor API, users could catch `SerializationException` but for

[jira] [Created] (KAFKA-9048) Improve partition scalability in replica fetcher

Lucas Bradstreet created KAFKA-9048: --- Summary: Improve partition scalability in replica fetcher Key: KAFKA-9048 URL: https://issues.apache.org/jira/browse/KAFKA-9048 Project: Kafka Issue Ty

Build failed in Jenkins: kafka-2.3-jdk8 #126

See Changes: [rhauch] KAFKA-9014: Fix AssertionError when SourceTask.poll returns an empty -- [...truncated 2.85 MB...] kafka.log.LogCleanerTest > testSegmentWithOffsetOverf

Jenkins build is back to normal : kafka-2.0-jdk8 #297

See

Build failed in Jenkins: kafka-2.4-jdk8 #16

See Changes: [wangguoz] MINOR: remove unused import in QueryableStateIntegrationTest (#7521) [matthias] KAFKA-8122: Fix Kafka Streams EOS integration test (#7470) [matthias] MINOR: code and JavaDoc cleanup (#7462)

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

See Changes: [wangguoz] MINOR: remove unused import in QueryableStateIntegrationTest (#7521) [rhauch] KAFKA-9014: Fix AssertionError when SourceTask.poll returns an empty [matthias] KAFKA-9030: Document client-

[jira] [Resolved] (KAFKA-8125) Check for topic existence in CreateTopicsRequest prior to creating replica assignment

[ https://issues.apache.org/jira/browse/KAFKA-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhruvil Shah resolved KAFKA-8125. - Resolution: Duplicate > Check for topic existence in CreateTopicsRequest prior to creating replic

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

See Changes: [wangguoz] KAFKA-8942: Document RocksDB metrics [jason] KAFKA-8813: Refresh log config if it's updated before initialization -- [...truncated 5.43 MB...] o

[jira] [Created] (KAFKA-9047) AdminClient group operations may not respect backoff

Jason Gustafson created KAFKA-9047: -- Summary: AdminClient group operations may not respect backoff Key: KAFKA-9047 URL: https://issues.apache.org/jira/browse/KAFKA-9047 Project: Kafka Issue

Jenkins build is back to normal : kafka-1.0-jdk7 #279

See

[DISCUSS] KIP-537: Increase default zookeeper session timeout

Hi All, I have a short KIP to raise the default zk session timeout: https://cwiki.apache.org/confluence/display/KAFKA/KIP-537%3A+Increase+default+zookeeper+session+timeout. Please take a look. Thanks, Jason

[jira] [Resolved] (KAFKA-8947) Connect framework incorrectly instantiates TaskStates for REST extensions

[ https://issues.apache.org/jira/browse/KAFKA-8947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-8947. -- Resolution: Fixed > Connect framework incorrectly instantiates TaskStates for REST extensions >

[jira] [Reopened] (KAFKA-8947) Connect framework incorrectly instantiates TaskStates for REST extensions

[ https://issues.apache.org/jira/browse/KAFKA-8947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reopened KAFKA-8947: -- > Connect framework incorrectly instantiates TaskStates for REST extensions > -

[jira] [Resolved] (KAFKA-8945) Incorrect null check in the constructor for ConnectorHealth and AbstractState

[ https://issues.apache.org/jira/browse/KAFKA-8945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-8945. -- Resolution: Fixed > Incorrect null check in the constructor for ConnectorHealth and AbstractSta

[jira] [Resolved] (KAFKA-9030) Document Instance-level Metrics

[ https://issues.apache.org/jira/browse/KAFKA-9030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-9030. Fix Version/s: 2.4.0 Resolution: Fixed > Document Instance-level Metrics > -

Build failed in Jenkins: kafka-2.1-jdk8 #235

See Changes: [rhauch] KAFKA-9014: Fix AssertionError when SourceTask.poll returns an empty -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environme

Build failed in Jenkins: kafka-1.1-jdk7 #274

See Changes: [rhauch] KAFKA-9014: Fix AssertionError when SourceTask.poll returns an empty -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environme

Build failed in Jenkins: kafka-2.2-jdk8 #176

See Changes: [rhauch] KAFKA-9014: Fix AssertionError when SourceTask.poll returns an empty -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environme

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

See Changes: [wangguoz] KAFKA-8942: Document RocksDB metrics [jason] KAFKA-8813: Refresh log config if it's updated before initialization [github] KAFKA-4422 / KAFKA-8700 / KAFKA-5566: Wait for state to transit

[jira] [Resolved] (KAFKA-9033) Change default client-id in consumer / producer to be more meaningful

[ https://issues.apache.org/jira/browse/KAFKA-9033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9033. Fix Version/s: 2.4.0 Resolution: Fixed > Change default client-id in consumer / prod

[jira] [Resolved] (KAFKA-9014) AssertionError thrown by SourceRecordWriteCounter when SourceTask.poll returns an empty list

[ https://issues.apache.org/jira/browse/KAFKA-9014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-9014. -- Reviewer: Randall Hauch Resolution: Fixed Merged onto the `trunk`, `2.3`, `2.2`, `2.1`, `

Build failed in Jenkins: kafka-2.4-jdk8 #15

See Changes: [wangguoz] KAFKA-8942: Document RocksDB metrics [jason] KAFKA-8725; Improve LogCleanerManager#grabFilthiestLog error handling [jason] KAFKA-8813: Refresh log config if it's updated before initializatio

Re: [VOTE] KIP-458: Connector Client Config Override Policy

Hi all, I'd like to bring attention to a feature that was added as part of the KIP but never actually documented: the new "admin." prefix and how it's used by workers to compute the configuration for admin clients when using the DLQ for a connector. I've written up a more detailed description of

[jira] [Created] (KAFKA-9046) Connect worker configs require undocumented 'admin.' prefix to configure DLQ for connectors

Chris Egerton created KAFKA-9046: Summary: Connect worker configs require undocumented 'admin.' prefix to configure DLQ for connectors Key: KAFKA-9046 URL: https://issues.apache.org/jira/browse/KAFKA-9046

[jira] [Created] (KAFKA-9045) Flaky Test DelegationTokenEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

Matthias J. Sax created KAFKA-9045: -- Summary: Flaky Test DelegationTokenEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl Key: KAFKA-9045 URL: https://issues.apache.org/jira/browse/K

Re: [VOTE] KIP-534: Retain tombstones for approximately delete.retention.ms milliseconds

Hi, Richard, Thanks for the updated KIP. +1 from me. Jun On Tue, Oct 15, 2019 at 12:46 PM Richard Yu wrote: > Hi Jun, > > I've updated the link accordingly. :) > Here is the updated KIP link: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-534%3A+Retain+tombstones+and+transaction+mar

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

Walker, thanks for picking up the KIP and reworking it for the changed API. Overall, the updated API suggestions make sense to me. The seem to align quite nicely with our current API design. One nit: In `CogroupedKStream#aggregate(...)` the type parameter of `Materialized` should be `V`, not `VR

Re: [VOTE] KIP-534: Retain tombstones for approximately delete.retention.ms milliseconds

Hi Jun, I've updated the link accordingly. :) Here is the updated KIP link: https://cwiki.apache.org/confluence/display/KAFKA/KIP-534%3A+Retain+tombstones+and+transaction+markers+for+approximately+delete.retention.ms+milliseconds Cheers, Richard On Mon, Oct 14, 2019 at 5:12 PM Jun Rao wrote: >

Re: [DISCUSS] KIP-535: Allow state stores to serve stale reads during rebalance

>>I get your point. But suppose there is a replica which has just become active, so in that case replica will still be building itself from scratch and this active will go to restoring state till it catches up with previous active, wouldn't serving from a restoring active make more sense than a rep

[jira] [Resolved] (KAFKA-5566) Flaky Test QueryableStateIntegrationTest.shouldAllowToQueryAfterThreadDied

[ https://issues.apache.org/jira/browse/KAFKA-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5566. -- Fix Version/s: (was: 1.0.0) 2.4.0 Resolution: Fixed > Flaky Test

[jira] [Resolved] (KAFKA-8700) Flaky Test QueryableStateIntegrationTest#queryOnRebalance

[ https://issues.apache.org/jira/browse/KAFKA-8700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-8700. -- Assignee: Guozhang Wang Resolution: Fixed This is a duplicate of KAFKA-4222. > Flaky Tes

[jira] [Resolved] (KAFKA-4222) Flaky Test QueryableStateIntegrationTest.queryOnRebalance

[ https://issues.apache.org/jira/browse/KAFKA-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4222. -- Fix Version/s: (was: 0.11.0.0) 2.4.0 Assignee: Guozhang Wang

[jira] [Resolved] (KAFKA-8813) Race condition when creating topics and changing their configuration

[ https://issues.apache.org/jira/browse/KAFKA-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8813. Fix Version/s: 2.4.0 2.3.2 Resolution: Fixed > Race condition whe

[jira] [Resolved] (KAFKA-8942) Document RocksDB metrics

[ https://issues.apache.org/jira/browse/KAFKA-8942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-8942. -- Fix Version/s: 2.4.0 Resolution: Fixed Issue resolved by pull request 7490 [https://gith

[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. > doInnerJoinFilte

[jira] [Created] (KAFKA-9044) Brokers occasionally (randomly?) dropping out of clusters

Peter Bukowinski created KAFKA-9044: --- Summary: Brokers occasionally (randomly?) dropping out of clusters Key: KAFKA-9044 URL: https://issues.apache.org/jira/browse/KAFKA-9044 Project: Kafka

[DISCUSS] KIP-399: Extend ProductionExceptionHandler to cover serialization exceptions

Hello all, I would like to restart the discussion of this KIP 399 . I think it is some low hanging fruit that could be quite beneficial. Thanks, Walker

[jira] [Resolved] (KAFKA-4280) Document REST resource for showing available connector plugin configs

[ https://issues.apache.org/jira/browse/KAFKA-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-4280. -- Resolution: Fixed The `GET /connector-plugins` endpoint has since been documented on https://k

[jira] [Resolved] (KAFKA-4278) Undocumented REST resources

[ https://issues.apache.org/jira/browse/KAFKA-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-4278. -- Resolution: Fixed These have since been documented. > Undocumented REST resources > --

[jira] [Resolved] (KAFKA-4598) Create new SourceTask commit callback method that takes offsets param

[ https://issues.apache.org/jira/browse/KAFKA-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-4598. -- Resolution: Implemented Marking as implemented via KAFKA-7500, via the `SourceTask.commitRecord

[jira] [Resolved] (KAFKA-5067) java.sql.SQLDataException on TimeStamp column when using AWS Redshift as a JDBC source

[ https://issues.apache.org/jira/browse/KAFKA-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-5067. -- Resolution: Invalid Resolving as INVALID since the reported problem is not on an Apache Kafka

[jira] [Resolved] (KAFKA-5741) Prioritize threads in Connect distributed worker process

[ https://issues.apache.org/jira/browse/KAFKA-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-5741. -- Resolution: Won't Fix Resolving as WONTFIX, since there is no clear indication that this is a p

[jira] [Resolved] (KAFKA-5740) Use separate file for HTTP logs

[ https://issues.apache.org/jira/browse/KAFKA-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-5740. -- Resolution: Won't Fix Resolving as WONTFIX > Use separate file for HTTP logs > ---

[jira] [Resolved] (KAFKA-5828) Allow explicitly setting polling interval for Kafka connectors

[ https://issues.apache.org/jira/browse/KAFKA-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-5828. -- Resolution: Won't Fix Use quotas instead. > Allow explicitly setting polling interval for Kafk

[jira] [Resolved] (KAFKA-5938) Oracle jdbc-source-connector with kafka-connect distributed mode will result in http 500 error

[ https://issues.apache.org/jira/browse/KAFKA-5938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-5938. -- Resolution: Invalid Resolving as INVALID since this issue appears to report a problem with a c

[jira] [Resolved] (KAFKA-7529) Kafka Connect JDBC doesn't push new records to Kafka Topic unless the connector is restarted

[ https://issues.apache.org/jira/browse/KAFKA-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-7529. -- Resolution: Invalid Resolving as INVALID since this issue does indeed appear to be on the Confl

Jenkins build is back to normal : kafka-trunk-jdk8 #3970

See

Re: [DISCUSS] KIP-535: Allow state stores to serve stale reads during rebalance

Hi Vinoth, Thanks for the feedback.  Can we link the JIRA, discussion thread also to the KIP.>> Added. Based on the discussion on KAFKA-6144, I was under the impression that this KIP is also going to cover exposing of the standby information in StreamsMetadata and thus subsume KAFKA-8994 . That

Build failed in Jenkins: kafka-2.4-jdk8 #14

See Changes: [matthias] MINOR: unify calls to get committed offsets and metadata (#7463) [matthias] KAFKA-8671: NullPointerException occurs if topic associated with -- [...t

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

See Changes: [github] MINOR: unify calls to get committed offsets and metadata (#7463) [matthias] KAFKA-8671: NullPointerException occurs if topic associated with -- [..