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

See Changes: [jason] KAFKA-7981; Add fetcher and log cleaner thread count metrics (#6514) [jason] KAFKA-8725; Improve LogCleanerManager#grabFilthiestLog error handling -

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

Guozhang Wang created KAFKA-9033: Summary: Change default client-id in consumer / producer to be more meaningful Key: KAFKA-9033 URL: https://issues.apache.org/jira/browse/KAFKA-9033 Project: Kafka

Re: [VOTE] KIP-511: Collect and Expose Client's Name and Version in the Brokers

+1 (binding). Thanks for the KIP this is going to be super useful. Thanks, Harsha On Fri, Oct 11, 2019 at 2:57 PM Guozhang Wang wrote: > Hi David, > > Thanks for the KIP. I know I'm late on voting here but I'd be +1 on this > too! > > Just a quick clarification on the tag "name=Connections" of

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

See Changes: [github] MINOR: Increase spotBugs max heap to 2 GB (#7497) -- [...truncated 5.42 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldNotAllowNu

[jira] [Resolved] (KAFKA-8725) Improve LogCleaner error handling when failing to grab the filthiest log

[ https://issues.apache.org/jira/browse/KAFKA-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8725. Fix Version/s: 2.4.0 Resolution: Fixed > Improve LogCleaner error handling when fail

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

ghassan Yammine created KAFKA-9032: -- Summary: Serializer is invoked with null when foreignValue=null Key: KAFKA-9032 URL: https://issues.apache.org/jira/browse/KAFKA-9032 Project: Kafka Issu

Re: [VOTE] KIP-511: Collect and Expose Client's Name and Version in the Brokers

Hi David, Thanks for the KIP. I know I'm late on voting here but I'd be +1 on this too! Just a quick clarification on the tag "name=Connections" of the third metric, what would be the format of "Connections" here? Would that be the connection listener name? Guozhang On Fri, Oct 11, 2019 at 1:

[jira] [Created] (KAFKA-9031) Add possibility to reset Kafka streams application state to specific point in time

Levani Kokhreidze created KAFKA-9031: Summary: Add possibility to reset Kafka streams application state to specific point in time Key: KAFKA-9031 URL: https://issues.apache.org/jira/browse/KAFKA-9031

Re: [VOTE] KIP-511: Collect and Expose Client's Name and Version in the Brokers

Hi, David, Thanks for the KIP. Just a minor comment below. 100. It seems that the new flexible fields need tag numbers. Could you add them to the wiki? Jun On Mon, Sep 23, 2019 at 11:37 AM Jason Gustafson wrote: > Thanks David for the clarification. That sounds good. > > On Mon, Sep 23, 2019

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

[ https://issues.apache.org/jira/browse/KAFKA-8970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishkam Ravi resolved KAFKA-8970. - Resolution: Fixed > StateDirectory creation fails with Exception > --

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

Bruno Cadonna created KAFKA-9030: Summary: Document Instance-level Metrics Key: KAFKA-9030 URL: https://issues.apache.org/jira/browse/KAFKA-9030 Project: Kafka Issue Type: Bug Compo

[jira] [Created] (KAFKA-9029) Flaky Test CooperativeStickyAssignorTest.testReassignmentWithRandomSubscriptionsAndChanges

Matthias J. Sax created KAFKA-9029: -- Summary: Flaky Test CooperativeStickyAssignorTest.testReassignmentWithRandomSubscriptionsAndChanges Key: KAFKA-9029 URL: https://issues.apache.org/jira/browse/KAFKA-9029

[jira] [Reopened] (KAFKA-5566) Instable test QueryableStateIntegrationTest.shouldAllowToQueryAfterThreadDied

[ https://issues.apache.org/jira/browse/KAFKA-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reopened KAFKA-5566: [https://builds.apache.org/job/kafka-pr-jdk11-scala2.13/2549/] > Instable test QueryableStateI

Jenkins build is back to normal : kafka-trunk-jdk11 #875

See

[jira] [Created] (KAFKA-9028) Replace DeleteAcls request/response with automated protocol

Mickael Maison created KAFKA-9028: - Summary: Replace DeleteAcls request/response with automated protocol Key: KAFKA-9028 URL: https://issues.apache.org/jira/browse/KAFKA-9028 Project: Kafka

[jira] [Created] (KAFKA-9027) Replace CreateAcls request/response with automated protocol

Mickael Maison created KAFKA-9027: - Summary: Replace CreateAcls request/response with automated protocol Key: KAFKA-9027 URL: https://issues.apache.org/jira/browse/KAFKA-9027 Project: Kafka

[jira] [Created] (KAFKA-9026) Replace DescribeAcls request/response with automated protocol

Mickael Maison created KAFKA-9026: - Summary: Replace DescribeAcls request/response with automated protocol Key: KAFKA-9026 URL: https://issues.apache.org/jira/browse/KAFKA-9026 Project: Kafka

Re: [VOTE] KIP-334 Include partitions in exceptions raised during consumer record deserialization/validation

Thanks Jason. I've edited the KIP with the latest proposal. On Thu, Oct 10, 2019 at 2:00 AM Jason Gustafson wrote: > Hi Stanislav, > > Sorry for the late comment. I'm happy with the current proposal. Just one > small request is to include an example which shows how a user could use > this to ski

[jira] [Created] (KAFKA-9025) ZkSecurityMigrator not working with zookeeper chroot

Laurent Millet (o.b.o. Airbus) created KAFKA-9025: - Summary: ZkSecurityMigrator not working with zookeeper chroot Key: KAFKA-9025 URL: https://issues.apache.org/jira/browse/KAFKA-9025 P

RE: [DISCUSS] KIP-519: Make SSL context/engine configuration extensible

Can you clarify a few points for me? The two stumbling blocks we have are: 1) reuse of the validation code in the existing SslFactory 2) the client/server mode on the SSLEngine How do you deal with those issues in your new proposal? My use case is to register a custom SslFactory that returns an

[jira] [Created] (KAFKA-9024) org.apache.kafka.connect.transforms.ValueToKey throws NPE

Robin Moffatt created KAFKA-9024: Summary: org.apache.kafka.connect.transforms.ValueToKey throws NPE Key: KAFKA-9024 URL: https://issues.apache.org/jira/browse/KAFKA-9024 Project: Kafka Issue

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

See Changes: [wangguoz] HOTFIX: fix checkstyle in Streams system test (#7494) -- [...truncated 5.66 MB...] org.apache.kafka.streams.internals.KeyValueStoreFacadeTest > s

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

See Changes: [wangguoz] HOTFIX: fix checkstyle in Streams system test (#7494) -- [...truncated 5.06 MB...] kafka.server.MetadataRequestTest > testControllerId STARTED kafka.

Re: [VOTE] KIP-352: Distinguish URPs caused by reassignment

+1 (non-binding), thanks for bringing it up On Thu, Oct 10, 2019 at 5:48 PM Colin McCabe wrote: > +1. Thanks, Viktor. > > Colin > > On Thu, Oct 10, 2019, at 03:30, Viktor Somogyi-Vass wrote: > > Hi All, > > > > During the code review it came up that we shouldn't count replication > bytes > > to

[jira] [Created] (KAFKA-9023) Producer NETWORK_EXCEPTION response should log more information

Stanislav Kozlovski created KAFKA-9023: -- Summary: Producer NETWORK_EXCEPTION response should log more information Key: KAFKA-9023 URL: https://issues.apache.org/jira/browse/KAFKA-9023 Project: Ka