[jira] [Created] (KAFKA-6581) ConsumerGroupCommand hangs if even one of the partition is unavailable

Sahil Aggarwal created KAFKA-6581: - Summary: ConsumerGroupCommand hangs if even one of the partition is unavailable Key: KAFKA-6581 URL: https://issues.apache.org/jira/browse/KAFKA-6581 Project:

[jira] [Resolved] (KAFKA-6577) Connect standalone SASL file source and sink test fails without explanation

[ https://issues.apache.org/jira/browse/KAFKA-6577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-6577. --- Resolution: Fixed Fix Version/s: 1.2.0 Issue resolved by pull request 4610

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

See

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

See

[jira] [Created] (KAFKA-6584) Session expiration concurrent with ZooKeeper leadership failover may lead to broker registration failure

Chris Thunes created KAFKA-6584: --- Summary: Session expiration concurrent with ZooKeeper leadership failover may lead to broker registration failure Key: KAFKA-6584 URL:

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

Yes, let's revert the incompatible changes. There was no mention of compatibility impact on the KIP and we should ensure that is the case for 1.1.0. Ismael On Thu, Feb 22, 2018 at 9:55 AM, Jason Gustafson wrote: > I know it's a been a while since this vote passed, but I

[jira] [Created] (KAFKA-6583) Metadata should include number of state stores for task

Richard Yu created KAFKA-6583: - Summary: Metadata should include number of state stores for task Key: KAFKA-6583 URL: https://issues.apache.org/jira/browse/KAFKA-6583 Project: Kafka Issue Type:

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

I know it's a been a while since this vote passed, but I think we need to reconsider the incompatible changes to the consumer reset tool. Specifically, we have removed the --execute option without deprecating it first, and we have changed the default behavior to execute rather than do a dry run.

RE: [DISCUSS]KIP-235 DNS alias and secured connections

Hi, Could anyone take a look at the pull request, so that if ok I can start a VOTE thread ? Regards, Jonathan Skrzypek -Original Message- From: Skrzypek, Jonathan [Tech] Sent: 09 February 2018 13:57 To: 'dev@kafka.apache.org' Subject: RE: [DISCUSS]KIP-235 DNS alias and secured

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

See Changes: [jason] MINOR: Refactor GroupMetadataManager cleanupGroupMetadata (#4504) -- [...truncated 416.74 KB...] kafka.utils.json.JsonValueTest >

[jira] [Created] (KAFKA-6585) Sonsolidate duplicated logic on reset tools

Guozhang Wang created KAFKA-6585: Summary: Sonsolidate duplicated logic on reset tools Key: KAFKA-6585 URL: https://issues.apache.org/jira/browse/KAFKA-6585 Project: Kafka Issue Type:

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

Hi Guozhang, To clarify my comment: any change with a backwards compatibility impact should be mentioned in the "Compatibility, Deprecation, and Migration Plan" section (in addition to the deprecation period and only happening in a major release as you said). Ismael On Thu, Feb 22, 2018 at

[DISCUSS] KIP-261: Add Single Value Fetch in Window Stores

Hi all, I have submitted KIP-261 to add a new API for window stores in order to optimize our current windowed aggregation implementations inside Streams DSL : https://cwiki.apache.org/confluence/display/KAFKA/KIP-261%3A+Add+Single+Value+Fetch+in+Window+Stores This change would require people

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

Just to clarify, the KIP itself has mentioned about the change so the PR was not un-intentional: " 3. Keep execution parameters uniform between both tools: It will execute by default, and have a `dry-run` parameter just show the results. This will involve change current `ConsumerGroupCommand` to

[jira] [Created] (KAFKA-6586) Refactor Connect executables

Randall Hauch created KAFKA-6586: Summary: Refactor Connect executables Key: KAFKA-6586 URL: https://issues.apache.org/jira/browse/KAFKA-6586 Project: Kafka Issue Type: Improvement

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

Yup, agreed. On Thu, Feb 22, 2018 at 11:46 AM, Ismael Juma wrote: > Hi Guozhang, > > To clarify my comment: any change with a backwards compatibility impact > should be mentioned in the "Compatibility, Deprecation, and Migration Plan" > section (in addition to the deprecation

Re: [VOTE] 1.0.1 RC2

+1 MetricsTest#testMetricsLeak failed but it is flaky test On Wed, Feb 21, 2018 at 4:06 PM, Ewen Cheslack-Postava wrote: > Hello Kafka users, developers and client-developers, > > This is the third candidate for release of Apache Kafka 1.0.1. > > This is a bugfix release for

Re: [DISCUSS] KIP-261: Add Single Value Fetch in Window Stores

+1 There were some typos: CachingWindowedStore -> CachingWindowStore RocksDBWindowedStore -> RocksDBWindowStore KStreamWindowedAggregate -> KStreamWindowAggregate KStreamWindowedReduce -> KStreamWindowReduce Cheers On Thu, Feb 22, 2018 at 1:34 PM, Guozhang Wang wrote: > Hi

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

I like Colin's suggestion for the longer term. If you don't provide --dry-run or --execute, then the command will prompt you. -Jason On Thu, Feb 22, 2018 at 11:10 AM, Guozhang Wang wrote: > Just to clarify, the KIP itself has mentioned about the change so the PR > was not

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

Perhaps, if the user doesn't pass the --execute flag, the tool should print a prompt like "would you like to perform this reset?" and wait for a Y / N (or yes or no) input from the command-line. Then, if the --execute flag is passed, we skip this. That seems 99% compatible, and also

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

Hi, Dong, Regarding deleting partitions, Gwen's point is right on. In some of the usage of Kafka, the traffic can be bursty. When the traffic goes up, adding partitions is a quick way of shifting some traffic to the newly added brokers. Once the traffic goes down, the newly added brokers will be

Build failed in Jenkins: kafka-trunk-jdk9 #427

See Changes: [rajinisivaram] MINOR: Fix javadoc for consumer offsets lookup APIs which do not block -- [...truncated 1.48 MB...] kafka.zk.KafkaZkClientTest >

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

See Changes: [rajinisivaram] MINOR: Fix javadoc for consumer offsets lookup APIs which do not block -- [...truncated 3.50 MB...] kafka.utils.json.JsonValueTest >

Re: [DISCUSS] KIP-261: Add Single Value Fetch in Window Stores

Thanks Ted, have updated the wiki page. On Thu, Feb 22, 2018 at 1:48 PM, Ted Yu wrote: > +1 > > There were some typos: > CachingWindowedStore -> CachingWindowStore > RocksDBWindowedStore -> RocksDBWindowStore > KStreamWindowedAggregate -> KStreamWindowAggregate >

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

Overall this is a very useful feature. With this we can finally scale keyed messages. +1 on the ability to remove partitions. This will greatly increase Kafka's scalability in cloud. For example, when there is traffic increase, we can add brokers and assign new partitions to the new brokers.

Re: Contributor

Done. On 2/22/18 6:44 AM, Sebastian Toader wrote: > Hi Kafka Dev team, > > Can you please add me the contributor list as I would like to contribute to > the Kafka project? > > My apache username: stoader > > > Thank you, > Sebastian > signature.asc Description: OpenPGP digital signature

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

Dong, thanks a lot for the KIP! Can you elaborate how this would work for compacted topics? If it does not work for compacted topics, I think Streams API cannot allow to scale input topics. This question seems to be particularly interesting for deleting partitions: assume that a key is never

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

Hey Dong, Two questions: 1. How will this work with Streams and Connect? 2. How does this compare to a solution where we physically split partitions using a linear hashing approach (the partition number is equivalent to the hash bucket in a hash table)?

[jira] [Resolved] (KAFKA-6578) Connect distributed and standalone worker 'main()' methods should catch and log all exceptions

[ https://issues.apache.org/jira/browse/KAFKA-6578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6578. Resolution: Fixed Fix Version/s: 1.1.0 > Connect distributed and standalone worker

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

One more thought: What about older Producer/Consumers? They don't understand the new protocol. How can we guarantee backward compatibility? Or would this "only" imply, that there is no ordering guarantee for older clients? -Matthias On 2/22/18 6:24 PM, Matthias J. Sax wrote: > Dong, > >

Are there plans to migrate some/all of the command line tools to use the new AdminClient?

I've dug around jira and the list of KIPs for a bit now, but could not really find anything specific on plans to move the command line tools over to the new AdminClient. Did I miss something or is that not currently planned? Most of the current command line tools require access to Zookeeper,

[jira] [Created] (KAFKA-6582) Partitions get underreplicated, with a single ISR, and doesn't recover. Other brokers do not take over and we need to manually restart the broker.

Jurriaan Pruis created KAFKA-6582: - Summary: Partitions get underreplicated, with a single ISR, and doesn't recover. Other brokers do not take over and we need to manually restart the broker. Key: KAFKA-6582

Contributor

Hi Kafka Dev team, Can you please add me the contributor list as I would like to contribute to the Kafka project? My apache username: stoader Thank you, Sebastian