Dose kafka connector rest aoi support multiple thread access?

Dear teams, We use Kafka-1.1.0 connector to load data,And start a connector using rest api by application. Before we start a connector,we'll check it was not  existed and then create it. This was  encapsulated in a Quartz job.And each connector  had a job. We use spring resttemplate as

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

See Changes: [wangguoz] Fix the missing ApiUtils tests in streams module. (#6003) -- [...truncated 2.24 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

Hi, Ryanne, Regarding the single connect cluster model, yes, the co-existence of a MM2 REST API and the nearly identical Connect API is one of my concerns. Implementation wise, my understanding is that the producer URL in a SourceTask is always obtained from the connect worker's configuration.

[jira] [Created] (KAFKA-7734) Metrics tags should use LinkedHashMap to guarantee ordering

Guozhang Wang created KAFKA-7734: Summary: Metrics tags should use LinkedHashMap to guarantee ordering Key: KAFKA-7734 URL: https://issues.apache.org/jira/browse/KAFKA-7734 Project: Kafka

Re: [DISCUSS] KIP-404: Add Kafka Connect configuration parameter for disabling WADL output on OPTIONS request

Thanks, Alex. The KIP looks good to me. Randall On Wed, Dec 12, 2018 at 10:08 PM Guozhang Wang wrote: > Alex, > > Thanks for putting up this KIP. The proposal lgtm. > > Guozhang > > On Wed, Dec 12, 2018 at 7:41 PM Oleksandr Diachenko > > wrote: > > > Hi all, > > > > I would like to start a

Re: [DISCUSS] KIP-307: Allow to define custom processor names with KStreams DSL

Hi all, Thanks again. I agree with your propositions. Also IMHO, overloading all methods (filter, map) to accept a new control object seems to provide a more natural development experience for users. Actually, this was the first proposition for this KIP, but we have rejected it because this

Jenkins build is back to normal : kafka-2.1-jdk8 #83

See

[jira] [Resolved] (KAFKA-5335) Controller should batch updatePartitionReassignmentData() operation

[ https://issues.apache.org/jira/browse/KAFKA-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-5335. - Resolution: Won't Do > Controller should batch updatePartitionReassignmentData() operation >

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

See Changes: [mjsax] KAFKA-7655 Metadata spamming requests from Kafka Streams under some -- [...truncated 2.25 MB...] kafka.coordinator.group.GroupCoordinatorTest >

Build failed in Jenkins: kafka-2.0-jdk8 #202

See Changes: [matthias] KAFKA-7655 Metadata spamming requests from Kafka Streams under some -- [...truncated 436.12 KB...] kafka.zk.ReassignPartitionsZNodeTest >

Re: [DISCUSS] KIP-201: Rationalising Policy interfaces

Hi Anna, Firstly, let me apologise again about having missed your previous emails about this. Thank you for the feedback. You raise some valid points about ambiguity. The problem with pulling the metadata into CreateTopicRequest and AlterTopicRequest is that you lose the benefit of being able to

[jira] [Resolved] (KAFKA-2124) gradlew is not working on a fresh checkout

[ https://issues.apache.org/jira/browse/KAFKA-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke resolved KAFKA-2124. Resolution: Duplicate Assignee: Grant Henke > gradlew is not working on a fresh checkout >

Re: [DISCUSS] KIP-391: Allow Producing with Offsets for Cluster Replication

Hi, as we haven't got any more feedback, we'd like to start a vote on KIP-391 on Monday https://cwiki.apache.org/confluence/display/KAFKA/KIP-391%3A+Allow+Producing+with+Offsets+for+Cluster+Replication -- Edoardo Comar IBM Event Streams IBM UK

Re: [DISCUSS] KIP-307: Allow to define custom processor names with KStreams DSL

Hi again, all, Matthias, I agree with you. Florian, thanks for your response. I think your proposal is the best way to address the ask for hiding the name() getter. But I'd like to question that ask and instead propose that we just make the name() getter part of the public API. The desire to

Need help on how to commit kafka consumer with other threads

I implemented one application using @kafkaListener. All listened events will be kept in Redis for some time. WIth the help of Spring scheduler, above events will be spanned across multiple threads and processed some business logic. Can you suggest me how to commit the events to kafka after

[jira] [Created] (KAFKA-7733) MockConsumer doesn't respect reset strategy

Stig Rohde Døssing created KAFKA-7733: - Summary: MockConsumer doesn't respect reset strategy Key: KAFKA-7733 URL: https://issues.apache.org/jira/browse/KAFKA-7733 Project: Kafka Issue

[jira] [Resolved] (KAFKA-7655) Metadata spamming requests from Kafka Streams under some circumstances, potential DOS

[ https://issues.apache.org/jira/browse/KAFKA-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7655. Resolution: Fixed Fix Version/s: 2.0.2 2.1.1

Re: [DISCUSS] KIP-402: Improve fairness in SocketServer processors

Thanks for the details Rajini. It would be great if you can add a few details to the KIP, on how many connections you are able to handle in your cluster with number 20 to give some context. Thanks, Harsha On Tue, Dec 11, 2018, at 10:22 AM, Rajini Sivaram wrote: > Hi Harsha, > > Thanks for

[jira] [Created] (KAFKA-7732) Kafka broker lag metrics is more than 0, but no partitions are under replicated

Mathias Kub created KAFKA-7732: -- Summary: Kafka broker lag metrics is more than 0, but no partitions are under replicated Key: KAFKA-7732 URL: https://issues.apache.org/jira/browse/KAFKA-7732 Project:

Re: [DISCUSS] KIP-401 TransformerSupplier/ProcessorSupplier enhancements

Just a meta comment: do we really need to deprecate existing `transform()` etc methods? The last argument is a vararg, and thus, just keeping the existing API for this part seems to work too, allowing to implement both patterns? Also, instead of adding a default method, we could also add a new

Re: [DISCUSS] KIP-307: Allow to define custom processor names with KStreams DSL

Just catching up on this discussion. My overall personal take is, that I am not a big fan of the interface `Named` that is used as a factory. I would rather prefer to add a control object parameter to all methods that don't have one yet. This KIP was started a while ago, and we added new naming

[jira] [Created] (KAFKA-7731) JMX metrics for client connections: how many, what version, what language, source ip etc...

Antony Stubbs created KAFKA-7731: Summary: JMX metrics for client connections: how many, what version, what language, source ip etc... Key: KAFKA-7731 URL: https://issues.apache.org/jira/browse/KAFKA-7731

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

For store updates, records are first serialized and afterwards put into the store and written into the changelog topic. In the current implementation, if the send() into the changelog topic produces an error and the handler skips over it, the local store content and the changelog topic diverge.

Re: Vote for KIP-393 (Fix time windowed serde to deserialize changelog topic)

+1 (binding) On Wed, 12 Dec 2018 at 13:27, Adam Bellemare wrote: > +1 (non-binding) from me. Looks like a pretty clear-cut case. > > > > On Tue, Dec 11, 2018 at 1:11 AM Shawn Nguyen > wrote: > > > Thanks for the feedback Guozhang! I updated the KIP. > > > > In the meantime, could I ask for

[jira] [Created] (KAFKA-7730) Limit total number of active connections in the broker

Rajini Sivaram created KAFKA-7730: - Summary: Limit total number of active connections in the broker Key: KAFKA-7730 URL: https://issues.apache.org/jira/browse/KAFKA-7730 Project: Kafka Issue

[jira] [Created] (KAFKA-7729) Mysterious disk increase when switching to RedHat OpenJDK

Dimitris Mandalidis created KAFKA-7729: -- Summary: Mysterious disk increase when switching to RedHat OpenJDK Key: KAFKA-7729 URL: https://issues.apache.org/jira/browse/KAFKA-7729 Project: Kafka