[jira] [Created] (KAFKA-7786) Fast update of leader epoch may stall partition fetching due to FENCED_LEADER_EPOCH

Anna Povzner created KAFKA-7786: --- Summary: Fast update of leader epoch may stall partition fetching due to FENCED_LEADER_EPOCH Key: KAFKA-7786 URL: https://issues.apache.org/jira/browse/KAFKA-7786 Proje

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

See

Re: [DISCUSS] KIP-408: Add Asynchronous Processing to Kafka Streams

Hi Boyang, Interesting article. Although something crossed my mind. When skipping bad records, we couldn't go back to them to process again to guarantee ordering i.e (both exactly-once and at-least-once would not be supported, only at-most-once). Also, in Kafka, when it comes to individually ackin

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

See Changes: [wangguoz] KAFKA-7734: Metrics tags should use LinkedHashMap to guarantee ordering -- [...truncated 2.25 MB...] org.apache.kafka.streams.test.OutputVerifier

Re: [DISCUSS] KIP-408: Add Asynchronous Processing to Kafka Streams

Hey Richard, thanks for the explanation. Recently I read an interesting blog post from Apache Pulsar (written long time ago), where they define the concept of individual ack which means we could skip records and leave certain records remain on t

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

See Changes: [harsha] KAFKA-6431: Shard purgatory to mitigate lock contention (#5338) -- [...truncated 2.25 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shou

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

[ https://issues.apache.org/jira/browse/KAFKA-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7734. -- Resolution: Fixed Fix Version/s: 2.2.0 > Metrics tags should use LinkedHashMap to guaran

Re: [VOTE] KIP-345: Introduce static membership protocol to reduce consumer rebalances

+1 (binding). Thanks, Harsha On Wed, Jan 2, 2019, at 9:59 AM, Boyang Chen wrote: > Thanks Jason for the comment! I answered it on the discuss thread. > > Folks, could we continue the vote for this KIP? This is a very critical > improvement for our streaming system > stability and we need to get

Re: Tests to emulate leader change(investigation of KAFKA-7680)

Hello Nikolay, I've left a comment on the ticket. Guozhang On Sun, Dec 23, 2018 at 11:54 PM Nikolay Izhikov wrote: > Hello, Guys. > > I started investigating of KAFKA-7680 [1] > > Jun Rao wrote that this issue can be reproduced with leader change. > > Please, give me the advice. > How can I e

Re: [DISCUSS] KIP-408: Add Asynchronous Processing to Kafka Streams

Hi all, Just bumping this KIP. Would be great if we got some discussion. On Sun, Dec 30, 2018 at 5:13 PM Richard Yu wrote: > Hi all, > > I made some recent changes to the KIP. It should be more relevant with the > issue now (involves Processor API in detail). > It would be great if you could c

Re: [DISCUSS] KIP-262 Metadata should include the number of state stores for task

Hi Matthias, I guess this is no longer necessary. I am open to anything honestly. I suppose we should close it (if its not already). On Fri, Oct 19, 2018 at 11:06 AM Matthias J. Sax wrote: > Any thought on my last email about discarding this KIP? > > > -Matthias > > On 9/14/18 11:44 AM, Matthi

Re: [DISCUSS] KIP-360: Improve handling of unknown producer

You're right about the dangling txn since it will actually block read-committed consumers from proceeding at all. I'd agree that since this is a very rare case, we can consider fixing it not via broker-side logic but via tooling in a future work. I've also discovered some related error handling lo

Re: Suggestion to make 0 grace period the default for suppress

Kafka Streams does not change topic configs if a topic exists already. Thus, there should be no impact in existing application if they are upgraded. However, I share the backward compatibility concern in general. Furthermore, for windowing, retention period must be at least window size IIRC, thus,

Re: Suggestion to make 0 grace period the default for suppress

Thanks for the proposal Jingguo. Guozhang when you mention to "change the default value of retention to 0 consistently", will we introduce any backward incompatible issue since the retention cutoff might change on the changelog topics that are unexpected. Boyang

Re: Suggestion to make 0 grace period the default for suppress

Thanks for reporting this Jingguo, personally I'd favor we change the default value of retention to 0 consistently, regardless of whether suppress is used, if we would ever consider changing it. Since it is a public API change (i.e. changing the default value), it should be discussed and voted via

Re: [EXTERNAL] [VOTE] KIP-382 MirrorMaker 2.0

Happy New Year all! Current tally is: +12 non-binding +1 binding Thanks for the support so far! Ryanne On Wed, Jan 2, 2019 at 5:26 AM Skrzypek, Jonathan wrote: > +1 (non-binding) > > Jonathan Skrzypek > > -Original Message- > From: Mickael Maison > Sent: 02 January 2019 11:10 > To: dev

[jira] [Created] (KAFKA-7785) Move DefaultPartitionGrouper (and PartitionGrouper) to o.a.k.streams.processor.internals package

Jacek Laskowski created KAFKA-7785: -- Summary: Move DefaultPartitionGrouper (and PartitionGrouper) to o.a.k.streams.processor.internals package Key: KAFKA-7785 URL: https://issues.apache.org/jira/browse/KAFKA-7785

Re: Use KafkaAdminClient to get broker dynamic config “leader.replication.throttled.rate” and “follower.replication.throttled.rate” ，but returned null

KafkaAdminClent#describeConfigs currently only returns values of non-sensitive configs that are defined in `KafkaConfig`. Since ` leader.replication.throttled.rate` is not defined in `KafkaConfig`, it is handled as a custom config and hence the value is not returned. We could however change this be

[jira] [Created] (KAFKA-7784) Producer & message format : better management when inter.broker.protocol.version is overrided

Hervé RIVIERE created KAFKA-7784: Summary: Producer & message format : better management when inter.broker.protocol.version is overrided Key: KAFKA-7784 URL: https://issues.apache.org/jira/browse/KAFKA-7784

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

See Changes: [cshapi] MINOR: Upgrade to Gradle 4.10.3 -- [...truncated 736.97 KB...] kafka.api.GroupEndToEndAuthorizationTest > testNoGroupAcl STARTED kafka.api.GroupEndToEnd