[jira] [Resolved] (KAFKA-7595) Kafka Streams: KTrable to KTable join introduces duplicates in downstream KTable

[ https://issues.apache.org/jira/browse/KAFKA-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7595. Resolution: Not A Bug > Kafka Streams: KTrable to KTable join introduces duplicates in

Tentative release date for KAFKA-7280 and its possible workaround

Hi,I am using Kafka 1.1.0 java client and my brokers are also on the same version. I am running into the same issue as reported in [KAFKA-7280] ConcurrentModificationException in FetchSessionHandler in heartbeat thread - ASF JIRA.  | | | | [KAFKA-7280] ConcurrentModificationException in

[jira] [Created] (KAFKA-7601) Handle message format downgrades during upgrade of message format version

Jason Gustafson created KAFKA-7601: -- Summary: Handle message format downgrades during upgrade of message format version Key: KAFKA-7601 URL: https://issues.apache.org/jira/browse/KAFKA-7601 Project:

Re: [VOTE] 2.1.0 RC0

Hey Satish, Yes! We will have another RC to include e.g. https://github.com/apache/kafka/pull/5857. Thanks, Dong On Mon, Nov 5, 2018 at 8:14 PM Satish Duggana wrote: > Hi Dong, > Is there a RC1 planned with configs documentation fixes and > https://github.com/apache/kafka/pull/5857 ? > >

[jira] [Resolved] (KAFKA-7559) ConnectStandaloneFileTest system tests do not pass

[ https://issues.apache.org/jira/browse/KAFKA-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-7559. - Resolution: Fixed > ConnectStandaloneFileTest system tests do not pass >

Re: [VOTE] KIP-386: Standardize on Min/Avg/Max metrics' default values

+1 (binding) -Harsha On Nov 6, 2018, 8:04 AM -0800, Kevin Lu , wrote: > +1 (non-binding) > > Regards, > Kevin > > On Tue, Nov 6, 2018 at 1:01 AM Stanislav Kozlovski > wrote: > > > Hey everybody, > > > > I'm starting a vote thread on KIP-386: Standardize on Min/Avg/Max metrics' > > default values

Re: [VOTE] KIP-354 Time-based log compaction policy

bump Xiongqi (Wesley) Wu On Thu, Sep 27, 2018 at 4:20 PM xiongqi wu wrote: > > Thanks Eno, Brett, Dong, Guozhang, Colin, and Xiaohe for feedback. > Can I have more feedback or VOTE on this KIP? > > > Xiongqi (Wesley) Wu > > > On Wed, Sep 19, 2018 at 10:52 AM xiongqi wu wrote: > >> Any other

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

See Changes: [jason] MINOR: Modify Connect service's startup timeout to be passed via the [lindong28] KAFKA-7481; Add upgrade/downgrade notes for 2.1.x -- [...truncated

[jira] [Resolved] (KAFKA-7313) StopReplicaRequest should attempt to remove future replica for the partition only if future replica exists

[ https://issues.apache.org/jira/browse/KAFKA-7313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-7313. - Resolution: Fixed > StopReplicaRequest should attempt to remove future replica for the partition > only

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

See

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

See Changes: [jason] MINOR: Modify Connect service's startup timeout to be passed via the [lindong28] KAFKA-7481; Add upgrade/downgrade notes for 2.1.x -- [...truncated

Re: [DISCUSS]KIP-216: IQ should throw different exceptions for different errors

Hey Vito, I saw that you updated your PR, but did not reply to my last comments. Any thoughts? -Matthias On 10/19/18 10:34 AM, Matthias J. Sax wrote: > Glad to have you back Vito :) > > Some follow up thoughts: > > - the current `InvalidStateStoreException` is documents as being > sometimes

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

See Changes: [lindong28] KAFKA-7313; StopReplicaRequest should attempt to remove future replica -- [...truncated 887.49 KB...] kafka.controller.PartitionStateMachineTest >

[jira] [Created] (KAFKA-7602) Improve usage of @see tag in Streams JavaDocs

Matthias J. Sax created KAFKA-7602: -- Summary: Improve usage of @see tag in Streams JavaDocs Key: KAFKA-7602 URL: https://issues.apache.org/jira/browse/KAFKA-7602 Project: Kafka Issue Type:

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

See Changes: [jason] MINOR: Modify Connect service's startup timeout to be passed via the [lindong28] KAFKA-7481; Add upgrade/downgrade notes for 2.1.x -- [...truncated

Re: [DISCUSS] KIP-354 Time-based log compaction policy

Hey Xiongqi, Thanks for the update. A few more comments below 1) According to the definition of kafka.log:type=LogCleaner,name=max-compaction-delay, it seems that the metric value will be a large negative number if max.compaction.lag.ms is MAX_LONG. Would this be a problem? Also, it seems weird

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

See

Re: Apache Kafka blog on more partitions support

The blog is now published to https://blogs.apache.org/kafka/entry/apache-kafka-supports-more-partitions Thanks, Jun On Fri, Nov 2, 2018 at 2:36 PM, Jun Rao wrote: > Hi, Mayuresh, > > Most of the controlled shutdown time is in leader election. The controller > currently doesn't wait for

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

See Changes: [jason] MINOR: Modify Connect service's startup timeout to be passed via the -- [...truncated 2.50 MB...] org.apache.kafka.streams.TopologyTest >

Re: [DISCUSS] How hard is it to separate the logic layer and the storage layer of Kafka broker?

Hi, Yulin, I assume the performance issue that you mentioned is for writes instead of reads. By default, Kafka flushes data to disks asynchronously in batches. So, even when there are multiple files to write, the batching can amortize the HDD seek overhead. It would be useful to understand the

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

See Changes: [junrao] KAFKA-7537: Avoid sending full UpdateMetadataRequest to existing -- [...truncated 2.73 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Re: [DISCUSS] KIP-354 Time-based log compaction policy

Dong, Thanks for the comments. I have updated the KIP based on your comments. below is reply to your questions: 1. We only calculate this metric for log compaction that is determined by max compaction lag. So we only collect non-negative metrics. The log cleaner is consistently running with

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

Thanks Matthias for bringing this awesome proposal up! I shall take a deeper look and make a comparison between the two proposals. Meanwhile for the scale down specifically for stateful streaming, we could actually introduce a new status called "learner" where the newly up hosts could try to

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

See

Re: [DISCUSS] KIP-362: Dynamic Session Window Support

Any update on this KIP? On 9/20/18 3:30 PM, Matthias J. Sax wrote: > Thanks for following up. Very nice examples! > > I think, that the window definition for Flink is semantically > questionable. If there is only a single record, why is the window > defined as [ts, ts+gap]? To me, this

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

Hey, there was quite a pause on this KIP discussion and in the mean time, a new design for incremental cooporative rebalance was suggested: https://cwiki.apache.org/confluence/display/KAFKA/Incremental+Cooperative+Rebalancing%3A+Support+and+Policies We should make sure that the proposal and

[jira] [Resolved] (KAFKA-7537) Only include live brokers in the UpdateMetadataRequest sent to existing brokers if there is no change in the partition states

[ https://issues.apache.org/jira/browse/KAFKA-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-7537. Resolution: Fixed Fix Version/s: 2.2.0 Merged the PR to trunk. > Only include live brokers in the

[jira] [Reopened] (KAFKA-7481) Consider options for safer upgrade of offset commit value schema

[ https://issues.apache.org/jira/browse/KAFKA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin reopened KAFKA-7481: - > Consider options for safer upgrade of offset commit value schema >

[jira] [Resolved] (KAFKA-7481) Consider options for safer upgrade of offset commit value schema

[ https://issues.apache.org/jira/browse/KAFKA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-7481. - Resolution: Fixed > Consider options for safer upgrade of offset commit value schema >

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

See

[VOTE] KIP-386: Standardize on Min/Avg/Max metrics' default values

Hey everybody, I'm starting a vote thread on KIP-386: Standardize on Min/Avg/Max metrics' default values In short, after the discussion thread

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

See Changes: [ismael] KAFKA-7559: Correct standalone system tests to use the correct external -- [...truncated 428.22 KB...]

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

See Changes: [ismael] KAFKA-7559: Correct standalone system tests to use the correct external -- [...truncated 2.73 MB...]

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

See Changes: [ismael] KAFKA-7559: Correct standalone system tests to use the correct external -- [...truncated 435.72 KB...] kafka.controller.PartitionStateMachineTest >

[jira] [Created] (KAFKA-7597) Trogdor - Support transactions in ProduceBenchWorker

Stanislav Kozlovski created KAFKA-7597: -- Summary: Trogdor - Support transactions in ProduceBenchWorker Key: KAFKA-7597 URL: https://issues.apache.org/jira/browse/KAFKA-7597 Project: Kafka

[jira] [Created] (KAFKA-7598) SIGSEGV on scala library Set

Antoine Tran created KAFKA-7598: --- Summary: SIGSEGV on scala library Set Key: KAFKA-7598 URL: https://issues.apache.org/jira/browse/KAFKA-7598 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-7599) Trogdor - Allow configuration for not throttling Benchmark Workers and expose messages per second

Stanislav Kozlovski created KAFKA-7599: -- Summary: Trogdor - Allow configuration for not throttling Benchmark Workers and expose messages per second Key: KAFKA-7599 URL:

[jira] [Created] (KAFKA-7600) Provide capability to rename cluster id

Yeva Byzek created KAFKA-7600: - Summary: Provide capability to rename cluster id Key: KAFKA-7600 URL: https://issues.apache.org/jira/browse/KAFKA-7600 Project: Kafka Issue Type: Improvement

Re: [VOTE] KIP-386: Standardize on Min/Avg/Max metrics' default values

+1 (non-binding) Regards, Kevin On Tue, Nov 6, 2018 at 1:01 AM Stanislav Kozlovski wrote: > Hey everybody, > > I'm starting a vote thread on KIP-386: Standardize on Min/Avg/Max metrics' > default values > > > In