[jira] [Created] (KAFKA-6701) synchronize Log modification between delete cleanup and async delete

Sumant Tambe created KAFKA-6701: --- Summary: synchronize Log modification between delete cleanup and async delete Key: KAFKA-6701 URL: https://issues.apache.org/jira/browse/KAFKA-6701 Project: Kafka

Re: [DISCUSS] KIP-268: Simplify Kafka Streams Rebalance Metadata Upgrade

Thanks for following up James. > Is this the procedure that happens during every rebalance? The reason I ask > is that this step: As long as the leader (before or after upgrade) receives at least one old version X Subscription it always sends version Assignment X back (the encoded supported

Jenkins build is back to normal : kafka-trunk-jdk7 #3277

See

Re: Subject: [VOTE] 1.1.0 RC3

Hi, Closing of this vote thread as there will be another RC. Thanks, Damian On Mon, 19 Mar 2018 at 23:47 Ismael Juma wrote: > Vahid, > > The Java 9 Connect issue is similar to the one being fixed for Trogdor in > the following PR: > >

Re: [DISCUSS] KIP-272: Add API version tag to broker's RequestsPerSec metric

Creating new metric and deprecating existing one seems better from compatibility point of view. Original message From: James Cheng Date: 3/21/18 1:39 AM (GMT-08:00) To: dev@kafka.apache.org Subject: Re: [DISCUSS] KIP-272: Add API version tag to broker's

[jira] [Created] (KAFKA-6699) When one of two Kafka nodes are dead, streaming API cannot handle messaging

Seweryn Habdank-Wojewodzki created KAFKA-6699: - Summary: When one of two Kafka nodes are dead, streaming API cannot handle messaging Key: KAFKA-6699 URL:

Re: [VOTE] KIP-268: Simplify Kafka Streams Rebalance Metadata Upgrade

+1 On Wed, 21 Mar 2018 at 01:44 abel-sun wrote: > >Thanks you of your offer ,agree with you! > > On 2018/03/21 00:56:11, Richard Yu wrote: > > Hi Matthias, > > Thanks for setting up the upgrade path. > > > > +1 (non-binding) > > > >

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

See Changes: [ismael] MINOR: Fix flaky TestUtils functions (#4743) [jason] MINOR: Remove acceptor creation in network thread update code (#4742) -- [...truncated 417.03

Re: [DISCUSS] KIP-272: Add API version tag to broker's RequestsPerSec metric

Can we retain total RequestsPerSec metric and add new version tag metric? When monitoring with simple jconsole/jmx based tools, It is useful to have total metric to monitor request rate. Thanks, On Wed, Mar 21, 2018 at 11:01 AM, Gwen Shapira wrote: > I love this. Not much

Re: [DISCUSS] KIP-268: Simplify Kafka Streams Rebalance Metadata Upgrade

Sorry, I see that the VOTE started already, but I have a late question on this KIP. In the "version probing" protocol: > Detailed upgrade protocol from metadata version X to Y (with X >= 1.2): > On startup/rolling-bounce, an instance does not know what version the leader > understands and

Build failed in Jenkins: kafka-1.0-jdk7 #176

See Changes: [ismael] MINOR: Fix flaky TestUtils functions (#4743) -- [...truncated 373.20 KB...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[16] STARTED

Build failed in Jenkins: kafka-trunk-jdk7 #3276

See Changes: [ismael] MINOR: Fix flaky TestUtils functions (#4743) -- [...truncated 417.88 KB...] kafka.server.epoch.LeaderEpochFileCacheTest >

[jira] [Created] (KAFKA-6698) ConsumerBounceTest#testClose sometimes fails

Ted Yu created KAFKA-6698: - Summary: ConsumerBounceTest#testClose sometimes fails Key: KAFKA-6698 URL: https://issues.apache.org/jira/browse/KAFKA-6698 Project: Kafka Issue Type: Test

Re: [DISCUSS] KIP-272: Add API version tag to broker's RequestsPerSec metric

Manikumar brings up a good point. This is a breaking change to the existing metric. Do we want to break compatibility, or do we want to add a new metric and (optionally) deprecate the existing metric? For reference, in KIP-153 [1], we changed an existing metric without doing proper

Re: Kafka version and JDK version

Hi Stephane, I don't see why we would increment Kafka versions as quick as Java versions. The way I think it should work is that we support LTS versions for a long time and only support the most recent non LTS version. The latter is to ensure that we catch any issues with newer Java releases

Re: Kafka version and JDK version

Sounds good ! Thanks for the detailed explanation :) On Wed., 21 Mar. 2018, 11:40 am Ismael Juma, wrote: > Hi Stephane, > > I don't see why we would increment Kafka versions as quick as Java > versions. The way I think it should work is that we support LTS versions > for a

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

See Changes: [ismael] MINOR: Fix flaky TestUtils functions (#4743) [jason] MINOR: Remove acceptor creation in network thread update code (#4742) -- [...truncated 3.47

[jira] [Resolved] (KAFKA-6457) Error: NOT_LEADER_FOR_PARTITION leads to NPE

[ https://issues.apache.org/jira/browse/KAFKA-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe resolved KAFKA-6457. Resolution: Resolved I believe this is a duplicate of KAFKA-6260 > Error:

Re: [DISCUSS] KIP-272: Add API version tag to broker's RequestsPerSec metric

I understand the impact to jmx based tools. But adding a new metric is unnecessary for more advanced monitoring systems that can aggregate with or without tags. Duplicating the metric (including the "request" tag) also adds performance cost to the broker, especially for the metric that needs to be

[jira] [Resolved] (KAFKA-6459) By (Re-)joining group StreamThread got NPE

[ https://issues.apache.org/jira/browse/KAFKA-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe resolved KAFKA-6459. Resolution: Duplicate Fix Version/s: 1.0.1 Duplicate of KAFKA-6260 > By

Re: [DISCUSS] KIP-263: Allow broker to skip sanity check of inactive segments on broker startup

Hey Jay, Yeah our existing sanity check only read the last entry in the index files. I must have miscommunicated if I previously said it was reading the full index. Broker appears to be spending a lot of time just to read the last entry of index files for every log segment. This is probably

Re: [DISCUSS] KIP-272: Add API version tag to broker's RequestsPerSec metric

I agree with Allen. Go with the intuitive name, even if it means not deprecating. The impact of breakage here is small since it only breaks monitoring and the folks who watch their dashboards closely are the ones likely to read the release notes carefully and see this change. On Wed, Mar 21,

[jira] [Created] (KAFKA-6700) allow producer performance test to run for a fixed duration

Chris Burroughs created KAFKA-6700: -- Summary: allow producer performance test to run for a fixed duration Key: KAFKA-6700 URL: https://issues.apache.org/jira/browse/KAFKA-6700 Project: Kafka

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hi Jun, I was really seeing progress in our conversation but your latest reply is just devastating. I though we were getting close being on the same page now it feels like we are in different libraries. I just quickly slam my answers in here. If they are to brief I am sorry give me a ping

Re: [DISCUSS] KIP-263: Allow broker to skip sanity check of inactive segments on broker startup

Hey Dong, Makes total sense. What I'm saying is I don't think that the sanity check is part of any formal guarantee we provide. It is true that corruption of data flushed to disk will be a potential problem, but I don't think the sanity check solves that it just has a couple heuristics to help

[jira] [Created] (KAFKA-6702) Wrong className in LoggerFactory.getLogger method

JieFang.He created KAFKA-6702: - Summary: Wrong className in LoggerFactory.getLogger method Key: KAFKA-6702 URL: https://issues.apache.org/jira/browse/KAFKA-6702 Project: Kafka Issue Type:

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

See Changes: [matthias] MINOR: remove obsolete warning in StreamsResetter (#4749) -- [...truncated 415.38 KB...] kafka.coordinator.transaction.TransactionCoordinatorTest >

Re: [DISCUSS] KIP-268: Simplify Kafka Streams Rebalance Metadata Upgrade

Hi Matthias, Just wondering, once this KIP goes through. Could I restart my older KIP to update SubscriptionInfo? Thanks Richard On Wed, Mar 21, 2018 at 11:18 AM, Matthias J. Sax wrote: > Thanks for following up James. > > > Is this the procedure that happens during

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

See Changes: [github] MINOR: remove obsolete warning in StreamsResetter (#4749) -- [...truncated 421.09 KB...] kafka.api.SaslClientsWithInvalidCredentialsTest >

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

See Changes: [github] MINOR: remove obsolete warning in StreamsResetter (#4749) -- [...truncated 421.50 KB...] kafka.security.auth.SimpleAclAuthorizerTest >

[jira] [Resolved] (KAFKA-6692) Kafka Streams internal topics should be prefixed with an underscore

[ https://issues.apache.org/jira/browse/KAFKA-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6692. -- Resolution: Not A Problem > Kafka Streams internal topics should be prefixed with an underscore

[VOTE] #2 KIP-248: Create New ConfigCommand That Uses The New AdminClient

Hi Everyone, I've started a vote on KIP-248 a few weeks ago but at the time I got a couple more comments and