Re: [DISCUSS] KIP-358: Migrate Streams API to Duration instead of long ms times

Hello, I want to start VOTE for this KIP today. Any objections? В Пн, 27/08/2018 в 10:20 +0300, Nikolay Izhikov пишет: > Hello, Matthias, John. > > Thanks in advance. > > > I wanted to let you know that we have dropped the `grace(long)` method from > > the Windows interface > >

Query related to Kafka Consumer Limit

Hi, I am from Intuit. We want to use Kafka as message bus where Single Producer produces message and 1 Million Consumer listens it. Requirement – 1. Single producer and 1 Million Consumer and one particular Topic with message. 2. When Pushed Message thru producer, should be received by

Re: [DISCUSS] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

I was wondering if it would be much simpler to just do a pass-through so that we can support any topic setting added in Kafka without any code changes in connect. Since these are for topics that will have the actual data stream, users might possibly need more flexibility in terms of how the topics

[jira] [Created] (KAFKA-7354) Fix IdlePercent and NetworkProcessorAvgIdlePercent metric calculation

huxihx created KAFKA-7354: - Summary: Fix IdlePercent and NetworkProcessorAvgIdlePercent metric calculation Key: KAFKA-7354 URL: https://issues.apache.org/jira/browse/KAFKA-7354 Project: Kafka Issue

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

See Changes: [jason] KAFKA-7128; Follower has to catch up to offset within current leader -- [...truncated 581.88 KB...] kafka.api.SaslSslAdminClientIntegrationTest >

Re: [DISCUSS] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

Do you think we should support name-value pairs, too? On Tue, Aug 28, 2018 at 6:41 PM Magesh Nandakumar wrote: > Randall, > > Thanks a lot for the KIP. I think this would be a great addition for many > source connectors. > One clarification I had was regarding the topic settings that can be >

Re: [DISCUSS] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

Randall, Thanks a lot for the KIP. I think this would be a great addition for many source connectors. One clarification I had was regarding the topic settings that can be configured. Is it limited to the setting exposed in the TopicSettings interface? Thanks Magesh On Tue, Aug 21, 2018 at 7:59

Jenkins build is back to normal : kafka-trunk-jdk10 #441

See

Re: [VOTE] KIP-275 - Indicate "isClosing" in the SinkTaskContext

Given that voting and discussion have stalled out it seems like this is a thing that folks aren't particularly interested in. I'll be moving the KIP status to abandoned unless I hear an objection in the next day or so. :) On Thu, May 31, 2018 at 12:39 PM Matt Farmer wrote: > Bumping this again

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

See Changes: [jason] KAFKA-7164; Follower should truncate after every missed leader epoch [jason] KAFKA-7128; Follower has to catch up to offset within current leader --

[jira] [Created] (KAFKA-7353) Connect logs 'this' for anonymous inner classes

Kevin Lafferty created KAFKA-7353: - Summary: Connect logs 'this' for anonymous inner classes Key: KAFKA-7353 URL: https://issues.apache.org/jira/browse/KAFKA-7353 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-367 Introduce close(Duration) to Producer instead of close(long, TimeUnit)

Thanks for the KIP. Makes sense to me. Should we make a similar change to AdminClient? -Jason On Tue, Aug 28, 2018 at 2:32 AM, Chia-Ping Tsai wrote: > (re-start the thread for KIP-367 because I enter the incorrect topic in > first post) > > hi all > > I would like to start a discussion of

Re: [VOTE] KIP-336: Consolidate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer

+1 Thanks for the updates. On Tue, Aug 28, 2018 at 1:15 AM, Viktor Somogyi-Vass < viktorsomo...@gmail.com> wrote: > Sure, I've added it. I'll also do the testing today. > > On Mon, Aug 27, 2018 at 5:03 PM Ismael Juma wrote: > > > Thanks Viktor. I think it would be good to verify that existing >

Re: [DISCUSS] KIP-359: Verify leader epoch in produce requests

Hey Dong, Yes, that was the intent. I fixed the proposal. Thanks for reviewing! -Jason On Tue, Aug 28, 2018 at 10:23 AM, Dong Lin wrote: > Hey Jason, > > Thanks for the KIP. The KIP looks good overall. > > I have one minor question. The KIP says that "If the producer sees either > the

Build failed in Jenkins: kafka-trunk-jdk10 #440

See Changes: [jason] KAFKA-7128; Follower has to catch up to offset within current leader -- [...truncated 1.53 MB...]

[jira] [Resolved] (KAFKA-6801) Restrict Consumer to fetch data from secure port only, and deny from non-secure port.

[ https://issues.apache.org/jira/browse/KAFKA-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6801. -- Resolution: Information Provided Closing as per above comment. > Restrict Consumer to fetch data

[jira] [Resolved] (KAFKA-7242) Externalized secrets are revealed in task configuration

[ https://issues.apache.org/jira/browse/KAFKA-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-7242. -- Resolution: Fixed Fix Version/s: 2.1.0 2.0.1 Issue

[jira] [Resolved] (KAFKA-5962) java.io.IOException: Map failed

[ https://issues.apache.org/jira/browse/KAFKA-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5962. -- Resolution: Fixed Closing as docs added in KAFKA-6343 > java.io.IOException: Map failed >

[jira] [Resolved] (KAFKA-1712) Excessive storage usage on newly added node

[ https://issues.apache.org/jira/browse/KAFKA-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1712. -- Resolution: Fixed Fixed via https://issues.apache.org/jira/browse/KAFKA-2511 > Excessive storage

[jira] [Resolved] (KAFKA-1665) controller state gets stuck in message after execute

[ https://issues.apache.org/jira/browse/KAFKA-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1665. -- Resolution: Auto Closed Closing inactive issue. Closing as per above comments. > controller state

[jira] [Resolved] (KAFKA-2127) Running TopicCommand --alter causes connection close/reset errors in kafka logs

[ https://issues.apache.org/jira/browse/KAFKA-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2127. -- Resolution: Auto Closed Closing inactive issue. Please reopen if the issue still exists in newer

[jira] [Resolved] (KAFKA-7291) kafka-console-consumer.sh waits on inexistent topic

[ https://issues.apache.org/jira/browse/KAFKA-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7291. -- Resolution: Fixed Fixed in newer versions. Yes, you need to upgrade to latest versions. >

[jira] [Resolved] (KAFKA-7128) Lagging high watermark can lead to committed data loss after ISR expansion

[ https://issues.apache.org/jira/browse/KAFKA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7128. Resolution: Fixed Fix Version/s: 2.1.0 2.0.1

Re: [DISCUSS] KIP-359: Verify leader epoch in produce requests

Hey Jason, Thanks for the KIP. The KIP looks good overall. I have one minor question. The KIP says that "If the producer sees either the FENCED_LEADER_EPOCH or the UNKNOWN_LEADER_EPOCH in the response from the broker, it will refresh metadata and retry". Given that UNKNOWN_LEADER_EPOCH is

Re: [DISCUSS] KIP-359: Verify leader epoch in produce requests

Hey All, I didn't expect many comments here. This is mostly for consistency and to improve debugging now that we have leader epoch in the metadata. I'll go ahead and start a vote shortly. Thanks, Jason On Sat, Aug 18, 2018 at 2:10 PM, Jason Gustafson wrote: > Hi All, > > I've added a short

[DISCUSS] KIP 368: Allow SASL Connections to Periodically Re-Authenticate

Hi everyone. I created KIP 368: Allow SASL Connections to Periodically Re-Authenticate (

[jira] [Created] (KAFKA-7352) KIP-368: Allow SASL Connections to Periodically Re-Authenticate

Ron Dagostino created KAFKA-7352: Summary: KIP-368: Allow SASL Connections to Periodically Re-Authenticate Key: KAFKA-7352 URL: https://issues.apache.org/jira/browse/KAFKA-7352 Project: Kafka

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

Okay, I will implement John's suggestion of namespacing the external headers prior to processing, and then removing the namespacing prior to emitting. A potential future KIP could be to provide this namespacing automatically. I would also appreciate any other additional comments on the workflow.

[jira] [Created] (KAFKA-7351) Wrong logic in method ClusterConnectionStates.isDisconnected

Boris Zhguchev created KAFKA-7351: - Summary: Wrong logic in method ClusterConnectionStates.isDisconnected Key: KAFKA-7351 URL: https://issues.apache.org/jira/browse/KAFKA-7351 Project: Kafka

[DISCUSS] KIP-367 Introduce close(Duration) to Producer instead of close(long, TimeUnit)

(re-start the thread for KIP-367 because I enter the incorrect topic in first post) hi all I would like to start a discussion of KIP-367 [1]. It is similar to KIP-358 and KIP-266 which is trying to substitute Duration for (long, TimeUnit). [1]

RE: [VOTE] KIP-235 Add DNS alias support for secured connection

Hi, Could someone take a look at https://github.com/apache/kafka/pull/4485 and merge if ok ? Jonathan Skrzypek -Original Message- From: Skrzypek, Jonathan [Tech] Sent: 27 June 2018 17:52 To: dev Subject: RE: [VOTE] KIP-235 Add DNS alias support for secured connection Hi, I've

Re: [DISCUSS] KIP-367 Introduce close(Duration) to Producer instead of close(long, TimeUnit)

fix the topic of this discussion :( On 2018/08/28 08:59:36, Chia-Ping Tsai wrote: > hi all > > I would like to start a discussion of KIP-367 [1]. It is similar to KIP-358 > and KIP-266 which is trying to substitute Duration for (long, TimeUnit). > > [1]

[DISCUSS]

hi all I would like to start a discussion of KIP-367 [1]. It is similar to KIP-358 and KIP-266 which is trying to substitute Duration for (long, TimeUnit). [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=89070496 -- Chia-Ping

Re: [VOTE] KIP-336: Consolidate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer

Sure, I've added it. I'll also do the testing today. On Mon, Aug 27, 2018 at 5:03 PM Ismael Juma wrote: > Thanks Viktor. I think it would be good to verify that existing > ExtendedSerializer implementations work without recompiling. This could be > done as a manual test. If you agree, I suggest

[jira] [Resolved] (KAFKA-2385) zookeeper-shell does not work

[ https://issues.apache.org/jira/browse/KAFKA-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2385. -- Resolution: Fixed Fixed in new zookeeper (3.4.7 +) versions > zookeeper-shell does not work >

[jira] [Resolved] (KAFKA-2238) KafkaMetricsConfig cannot be configured in broker (KafkaConfig)

[ https://issues.apache.org/jira/browse/KAFKA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2238. -- Resolution: Duplicate Resolving as duplicated of KAFKA-5066 which will add docs for KafkaMetricsConfig

Re: [EXTERNAL] [DISCUSS] KIP-158: Kafka Connect should allow source connectors to set topic-specific settings for new topics

@randall it's more of a "safety net" and making sure an application runs against a topic that's properly configured or crashes. Not absolutely needed On Mon., 27 Aug. 2018, 6:04 pm McCaig, Rhys, wrote: > Randall, > > This KIP looks great to me. As for _updating_ topic configs - It’s a nice > to