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

See Changes: [matthias] MINOR: update docs JSON serde links (#6465) [matthias] MINOR: updated names for deprecated streams constants (#6466) -- [...truncated 917.83 KB...]

Re: [DISCUSS] KIP-398: Support reading trust store from classpath

Hi, Noa, Thanks for the KIP and sorry for the late response. The KIP itself looks reasonable. My only concern is that it's very specific to SSL. We have other configurations that also depend on files (e.g. keytab in Sasl GSSAPI). It would be inconsistent that we only support the CLASSPATH:

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

See Changes: [jason] MINOR: Improve logging around index files (#6385) -- [...truncated 463.67 KB...] kafka.coordinator.transaction.TransactionCoordinatorTest >

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

See

Re: [VOTE] 2.2.0 RC2

+1 (non-binding) - Ran testAll/releaseTarGzAll successfully with no failures. - Ran through quickstart of core/streams on builds generated from 2.2.0-rc2 tag - Ran few internal apps targeting to topics on 3 node cluster. Thanks for running the release Matthias! On Wed, Mar 20, 2019 at 12:43 AM

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

See Changes: [jason] MINOR: Improve logging around index files (#6385) -- [...truncated 1.93 MB...] org.apache.kafka.streams.StreamsConfigTest >

Re: [DISCUSS] KIP-392: Allow consumers to fetch from the closest replica

Hi Ryanne, Thanks for the comment. If I understand your question correctly, I think the answer is no. I would expect typical selection logic to consider replica availability first before any other factor. In some cases, however, a user may put a higher priority on saving cross-dc traffic costs.

Re: [DISCUSS] KIP-392: Allow consumers to fetch from the closest replica

Jason, awesome KIP. I'm wondering how this change would affect availability of the cluster when a rack is unreachable. Is there a scenario where availability is improved or impaired due to the proposed changes? Ryanne On Tue, Mar 19, 2019 at 4:32 PM Jason Gustafson wrote: > Hi Jun, > > Yes,

Re: [DISCUSS] KIP-236 Interruptible Partition Reassignment

Hi Viktor, Thanks for the review.  If there is reassignment in-progress while the cluster is upgraded with this KIP (upgrade the binary and then do a cluster rolling restart of the brokers), the reassignment JSON in Zookeeper  /admin/reassign_partitions will only have  {topic, partition,

Re: [DISCUSS] KIP-392: Allow consumers to fetch from the closest replica

Hi Jun, Yes, that makes sense to me. I have added a ClientMetadata class which encapsulates various metadata including the rackId and the client address information. Thanks, Jason On Tue, Mar 19, 2019 at 2:17 PM Jun Rao wrote: > Hi, Jason, > > Thanks for the updated KIP. Just one more comment

[jira] [Created] (KAFKA-8129) Shade Kafka client dependencies

Colin P. McCabe created KAFKA-8129: -- Summary: Shade Kafka client dependencies Key: KAFKA-8129 URL: https://issues.apache.org/jira/browse/KAFKA-8129 Project: Kafka Issue Type: Improvement

Re: [DISCUSS] KIP-392: Allow consumers to fetch from the closest replica

Hi, Jason, Thanks for the updated KIP. Just one more comment below. 100. The ReplicaSelector class has the following method. I am wondering if we should additionally pass in the client connection info to the method. For example, if rackId is not set, the plugin could potentially select the

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

See Changes: [bbejeck] KAFKA-8062: Do not remore StateListener when shutting down stream thread -- [...truncated 4.67 MB...]

Re: [VOTE] 2.2.0 RC2

+1 (non-binding) - Verified the artifacts, build from src, ran tests - Verified the quickstart, ran producer/consumer performance tests. Thanks for running release!. Thanks, Manikumar On Wed, Mar 20, 2019 at 12:19 AM David Arthur wrote: > +1 > > Validated signatures, and ran through

Re: [VOTE] 2.2.0 RC2

+1 Validated signatures, and ran through quick-start. Thanks! On Mon, Mar 18, 2019 at 4:00 AM Jakub Scholz wrote: > +1 (non-binding). I used the staged binaries and run some of my tests > against them. All seems to look good to me. > > On Sat, Mar 9, 2019 at 11:56 PM Matthias J. Sax > wrote:

Re: KIP-213- [DISCUSS] - Three follow-up discussion points - topic partitioning, serializers, hashers

Thanks John & Matthias. I have created a report with Confluent ( https://github.com/confluentinc/schema-registry/issues/1061). I will continue on with current work and we can resume the discussion, as Matthias correctly indicates, in the PR. Matthias, thank you for the link to Kafka-. This is

Re: KIP-213- [DISCUSS] - Three follow-up discussion points - topic partitioning, serializers, hashers

Chiming in... 1) Agreed. There is a technical reason 1:1 joins have to be co-partitioned, which does not apply to the many:1 join you've designed. 2) Looking at the Serializer interface, it unfortunately doesn't indicate whether the topic (or the value) is nullable. There are several places in

Re: [DISCUSS] KIP-438: Expose task, connector IDs in Connect API

Thanks Viktor. Yes to both. ConnectorTaskId (which includes both connector name and task ID) is accessible from both WorkerSource/SinkTaskContext, so this change is trivial. Ryanne On Tue, Mar 19, 2019 at 9:26 AM Viktor Somogyi-Vass wrote: > I'm generally +1 on this, although have a couple of

Not able to run

After downloading tar file of I am running the zookeeper command I am getting error message like Kafka-run-class.sh line 243 C:\Program: No such file or directory Version is Kafka_2.11-0.10.0.0

[jira] [Resolved] (KAFKA-8094) Iterating over cache with get(key) is inefficient

[ https://issues.apache.org/jira/browse/KAFKA-8094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck resolved KAFKA-8094. Resolution: Fixed > Iterating over cache with get(key) is inefficient >

Re: [DISCUSS] KIP-437: Custom replacement for MaskField SMT

Hi Adam, Thank you for your response! Dear community members, do you have any other thoughts on this KIP? Would be great if you share them! Regards, Valeria сб, 16 мар. 2019 г. в 18:16, Adam Bellemare : > Hi Valeria > > I am thinking that a full map function via configuration is very unlikely

[jira] [Created] (KAFKA-8128) Dynamic delegation token change possibility for consumer/producer

Gabor Somogyi created KAFKA-8128: Summary: Dynamic delegation token change possibility for consumer/producer Key: KAFKA-8128 URL: https://issues.apache.org/jira/browse/KAFKA-8128 Project: Kafka

Re: [DISCUSS] KIP-438: Expose task, connector IDs in Connect API

I'm generally +1 on this, although have a couple of basic questions. Am I getting that right that you basically want to expose the task id from ConnectorTaskId? And if so, then I guess you'll provide the implementation too? Thanks, Viktor On Tue, Mar 5, 2019 at 6:49 PM Ryanne Dolan wrote: >

[jira] [Resolved] (KAFKA-8062) StateListener is not notified when StreamThread dies

[ https://issues.apache.org/jira/browse/KAFKA-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck resolved KAFKA-8062. Resolution: Fixed > StateListener is not notified when StreamThread dies >

Re: [DISCUSS] KIP-236 Interruptible Partition Reassignment

Hey George, Thanks for the answers. I'll try to block out time this week to review your PR. I have one more point to clarify: I've seen some customers who are managing Kafka as an internal company-wide service and they may or may not know that how certain topics are used within the company. That

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

See Changes: [jason] MINOR: Improve logging around index files (#6385) -- [...truncated 2.33 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

[jira] [Created] (KAFKA-8127) It may need to import scala.io

JieFang.He created KAFKA-8127: - Summary: It may need to import scala.io Key: KAFKA-8127 URL: https://issues.apache.org/jira/browse/KAFKA-8127 Project: Kafka Issue Type: Bug Reporter: