[jira] [Created] (KAFKA-3958) To set the maximum no of consumers which can consume from the particular topic.

Sharad Gupta created KAFKA-3958: --- Summary: To set the maximum no of consumers which can consume from the particular topic. Key: KAFKA-3958 URL: https://issues.apache.org/jira/browse/KAFKA-3958 Project:

[jira] [Commented] (KAFKA-3101) Optimize Aggregation Outputs

[ https://issues.apache.org/jira/browse/KAFKA-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15374085#comment-15374085 ] Bill Bejeck commented on KAFKA-3101: [~enothereska] [~guozhang] With regards to the performance

[jira] [Updated] (KAFKA-3945) kafka-console-producer.sh does not accept request-required-acks=all

[ https://issues.apache.org/jira/browse/KAFKA-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-3945: --- Status: Patch Available (was: Open) > kafka-console-producer.sh does not accept

[jira] [Commented] (KAFKA-3945) kafka-console-producer.sh does not accept request-required-acks=all

[ https://issues.apache.org/jira/browse/KAFKA-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373912#comment-15373912 ] ASF GitHub Bot commented on KAFKA-3945: --- GitHub user vahidhashemian opened a pull request:

[GitHub] kafka pull request #1618: KAFKA-3945: Fix validation of 'acks' config in con...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1618 KAFKA-3945: Fix validation of 'acks' config in console producer The `acks` config that is provided to console producer with `request-required-acks` comes with `all`, `-1`, `0`, `1` as valid

[jira] [Commented] (KAFKA-1120) Controller could miss a broker state change

[ https://issues.apache.org/jira/browse/KAFKA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373872#comment-15373872 ] Maysam Yabandeh commented on KAFKA-1120: [~junrao] This is currently a major pain point for us. If

[jira] [Assigned] (KAFKA-3945) kafka-console-producer.sh does not accept request-required-acks=all

[ https://issues.apache.org/jira/browse/KAFKA-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-3945: -- Assignee: Vahid Hashemian > kafka-console-producer.sh does not accept

[jira] [Comment Edited] (KAFKA-3957) consumer timeout not being respected when kafka broker is not available

[ https://issues.apache.org/jira/browse/KAFKA-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373823#comment-15373823 ] Vahid Hashemian edited comment on KAFKA-3957 at 7/12/16 10:30 PM: -- This

[jira] [Commented] (KAFKA-3957) consumer timeout not being respected when kafka broker is not available

[ https://issues.apache.org/jira/browse/KAFKA-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373823#comment-15373823 ] Vahid Hashemian commented on KAFKA-3957: This is already filed under an earlier JIRA

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

See

Re: [VOTE] KIP-67: Queryable state for Kafka Streams

Ismael - that is fine with me. Thanks On Tue, 12 Jul 2016 at 14:11 Ismael Juma wrote: > Hi Damian, > > How about StreamsMetadata instead? The general naming pattern seems to > avoid the `Kafka` prefix for everything outside of `KafkaStreams` itself. > > Ismael > > On Tue, Jul

Re: [VOTE] KIP-67: Queryable state for Kafka Streams

Hi Damian, How about StreamsMetadata instead? The general naming pattern seems to avoid the `Kafka` prefix for everything outside of `KafkaStreams` itself. Ismael On Tue, Jul 12, 2016 at 7:14 PM, Damian Guy wrote: > Hi, > > I agree with point 1. application.server is a

Build failed in Jenkins: kafka-0.10.0-jdk7 #147

See Changes: [wangguoz] KAFKA-3931: Fix transient failures in pattern subscription tests [wangguoz] MINOR: Check null in SmokeTestDriver to avoid NPE -- [...truncated 1120 lines...]

Re: [VOTE] KIP-67: Queryable state for Kafka Streams

Hi Damian, After running the example code in mind with these two approaches I'm sold on your arguments :) Guozhang On Tue, Jul 12, 2016 at 12:49 PM, Sriram Subramanian wrote: > I liked abstracting the metadata approach as well. It also helps to evolve > in the future. > >

[GitHub] kafka pull request #1617: syncing mine with upstream

Github user prabcs closed the pull request at: https://github.com/apache/kafka/pull/1617 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] kafka pull request #1617: syncing mine with upstream

GitHub user prabcs opened a pull request: https://github.com/apache/kafka/pull/1617 syncing mine with upstream You can merge this pull request into a Git repository by running: $ git pull https://github.com/prabcs/kafka trunk Alternatively you can review and apply these

Re: [VOTE] KIP-67: Queryable state for Kafka Streams

I liked abstracting the metadata approach as well. It also helps to evolve in the future. On Tue, Jul 12, 2016 at 12:42 PM, Michael Noll wrote: > Like Damian I'd also favor a proper type (KafkaStreamsMetadata) rather than > a Map-based construct. > > -Michael > > On Tue,

Re: [VOTE] KIP-67: Queryable state for Kafka Streams

Like Damian I'd also favor a proper type (KafkaStreamsMetadata) rather than a Map-based construct. -Michael On Tue, Jul 12, 2016 at 8:45 PM, Damian Guy wrote: > One more thing on the above, the methods on KafkaStreams should be changed > to something like: > > Collection

[GitHub] kafka pull request #1611: MINOR: Check null in SmokeTestDriver to avoid NPE

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1611 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-2946) DeleteTopic - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-2946: --- Status: Patch Available (was: In Progress) > DeleteTopic - protocol and server side implementation >

Re: [VOTE] KIP-67: Queryable state for Kafka Streams

One more thing on the above, the methods on KafkaStreams should be changed to something like: Collection allMetadata() Collection allMetadataForStore(final String storeName) KafkaStreamsMetadata metadataWithKey(final String storeName, final K key,

[jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created

[ https://issues.apache.org/jira/browse/KAFKA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373430#comment-15373430 ] ASF GitHub Bot commented on KAFKA-2857: --- Github user imandhan closed the pull request at:

[jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created

[ https://issues.apache.org/jira/browse/KAFKA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373431#comment-15373431 ] ASF GitHub Bot commented on KAFKA-2857: --- GitHub user imandhan reopened a pull request:

[GitHub] kafka pull request #1548: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

GitHub user imandhan reopened a pull request: https://github.com/apache/kafka/pull/1548 KAFKA-2857 ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created Added a check to make sure different cases

[GitHub] kafka pull request #1548: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

Github user imandhan closed the pull request at: https://github.com/apache/kafka/pull/1548 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-2946) DeleteTopic - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373418#comment-15373418 ] ASF GitHub Bot commented on KAFKA-2946: --- GitHub user granthenke opened a pull request:

[GitHub] kafka pull request #1616: KAFKA-2946: DeleteTopic - protocol and server side...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1616 KAFKA-2946: DeleteTopic - protocol and server side implementation You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka

[GitHub] kafka pull request #1594: KAFKA-3931: Fix transient failures in pattern subs...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1594 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-3931) kafka.api.PlaintextConsumerTest.testPatternUnsubscription transient failure

[ https://issues.apache.org/jira/browse/KAFKA-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373417#comment-15373417 ] ASF GitHub Bot commented on KAFKA-3931: --- Github user asfgit closed the pull request at:

[jira] [Updated] (KAFKA-3931) kafka.api.PlaintextConsumerTest.testPatternUnsubscription transient failure

[ https://issues.apache.org/jira/browse/KAFKA-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3931: - Resolution: Fixed Fix Version/s: 0.10.0.1 Status: Resolved (was: Patch

Re: [VOTE] KIP-67: Queryable state for Kafka Streams

Hi, I agree with point 1. application.server is a better name for the config (we'll change this). However, on point 2 I think we should stick mostly with what we already have. I've tried both ways of doing this when working on the JIRA and building examples and I find the current approach more

[jira] [Commented] (KAFKA-3950) kafka mirror maker tool is not respecting whitelist option

[ https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373307#comment-15373307 ] ASF GitHub Bot commented on KAFKA-3950: --- GitHub user omkreddy opened a pull request:

[GitHub] kafka pull request #1615: KAFKA-3950: kafka mirror maker tool is not respect...

GitHub user omkreddy opened a pull request: https://github.com/apache/kafka/pull/1615 KAFKA-3950: kafka mirror maker tool is not respecting whitelist option You can merge this pull request into a Git repository by running: $ git pull https://github.com/omkreddy/kafka

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373244#comment-15373244 ] Ravi Peri commented on KAFKA-1194: -- Sriharsha, I will send out a PR with patch request today. Thanks r

[jira] [Created] (KAFKA-3957) consumer timeout not being respected when kafka broker is not available

Vincent Fumo created KAFKA-3957: --- Summary: consumer timeout not being respected when kafka broker is not available Key: KAFKA-3957 URL: https://issues.apache.org/jira/browse/KAFKA-3957 Project: Kafka

[jira] [Commented] (KAFKA-3252) compression type for a topic should be used during log compaction

[ https://issues.apache.org/jira/browse/KAFKA-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373182#comment-15373182 ] Ashish K Singh commented on KAFKA-3252: --- [~junrao] [~omkreddy] what should be the expected behavior

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

See Changes: [junrao] KAFKA-2945; CreateTopic - protocol and server side implementation -- [...truncated 1333 lines...] kafka.server.EdgeCaseRequestTest > testInvalidApiVersionRequest PASSED

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

See Changes: [junrao] KAFKA-2945; CreateTopic - protocol and server side implementation -- [...truncated 3341 lines...] kafka.message.ByteBufferMessageSetTest > testValidBytes PASSED

[jira] [Commented] (KAFKA-3956) MockProducer.send() sends a message before completeNext() or errorNext() are called

[ https://issues.apache.org/jira/browse/KAFKA-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373134#comment-15373134 ] Gavin Manning commented on KAFKA-3956: -- {{monospaced}} {noformat} @Test public void

[jira] [Created] (KAFKA-3956) MockProducer.send() sends a message before completeNext() or errorNext() are called

Gavin Manning created KAFKA-3956: Summary: MockProducer.send() sends a message before completeNext() or errorNext() are called Key: KAFKA-3956 URL: https://issues.apache.org/jira/browse/KAFKA-3956

[jira] [Commented] (KAFKA-3950) kafka mirror maker tool is not respecting whitelist option

[ https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373115#comment-15373115 ] Manikumar Reddy commented on KAFKA-3950: I was also thinking similar lines. Instead of removing

[jira] [Commented] (KAFKA-3952) VerifyConsumerRebalance cannot succeed when checking partition owner

[ https://issues.apache.org/jira/browse/KAFKA-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373067#comment-15373067 ] ASF GitHub Bot commented on KAFKA-3952: --- Github user swwl1992 closed the pull request at:

[jira] [Commented] (KAFKA-3952) VerifyConsumerRebalance cannot succeed when checking partition owner

[ https://issues.apache.org/jira/browse/KAFKA-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373068#comment-15373068 ] ASF GitHub Bot commented on KAFKA-3952: --- GitHub user swwl1992 reopened a pull request:

[GitHub] kafka pull request #1612: KAFKA-3952: Consumer rebalance verifier never succ...

GitHub user swwl1992 reopened a pull request: https://github.com/apache/kafka/pull/1612 KAFKA-3952: Consumer rebalance verifier never succeed due to type mismatch You can merge this pull request into a Git repository by running: $ git pull https://github.com/swwl1992/kafka

[GitHub] kafka pull request #1612: KAFKA-3952: Consumer rebalance verifier never succ...

Github user swwl1992 closed the pull request at: https://github.com/apache/kafka/pull/1612 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373066#comment-15373066 ] Sriharsha Chintalapani commented on KAFKA-1194: --- [~rperi] any update on this. > The kafka

[jira] [Updated] (KAFKA-2945) CreateTopic - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2945: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1489

[jira] [Commented] (KAFKA-2945) CreateTopic - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373060#comment-15373060 ] ASF GitHub Bot commented on KAFKA-2945: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request #1489: KAFKA-2945: CreateTopic - protocol and server side...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1489 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-3950) kafka mirror maker tool is not respecting whitelist option

[ https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372991#comment-15372991 ] Ismael Juma commented on KAFKA-3950: My point is that if you are missing the authorization for a topic

[jira] [Commented] (KAFKA-3950) kafka mirror maker tool is not respecting whitelist option

[ https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372982#comment-15372982 ] TAO XIAO commented on KAFKA-3950: - As only the topics that the users have permission to read are returned

[jira] [Created] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

Tom Crayford created KAFKA-3955: --- Summary: Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot Key: KAFKA-3955 URL: https://issues.apache.org/jira/browse/KAFKA-3955

[jira] [Commented] (KAFKA-3933) Kafka OOM During Log Recovery Due to Leaked Native Memory

[ https://issues.apache.org/jira/browse/KAFKA-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372882#comment-15372882 ] ASF GitHub Bot commented on KAFKA-3933: --- GitHub user tcrayford opened a pull request:

[GitHub] kafka pull request #1614: KAFKA-3933: close deepIterator during log recovery

GitHub user tcrayford opened a pull request: https://github.com/apache/kafka/pull/1614 KAFKA-3933: close deepIterator during log recovery Avoids leaking native memory and hence crashing brokers on bootup due to running out of memory. Introduces

[jira] [Commented] (KAFKA-1464) Add a throttling option to the Kafka replication tool

[ https://issues.apache.org/jira/browse/KAFKA-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372870#comment-15372870 ] Ralph Weires commented on KAFKA-1464: - Another related idea then, since those consumer rebalancing

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372831#comment-15372831 ] Trevor Dodds commented on KAFKA-1194: - I'm running 0.10.0.0 on windows and seeing the same error, this

[jira] [Comment Edited] (KAFKA-3950) kafka mirror maker tool is not respecting whitelist option

[ https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372740#comment-15372740 ] Ismael Juma edited comment on KAFKA-3950 at 7/12/16 11:39 AM: -- [~xiaotao183],

[jira] [Commented] (KAFKA-3950) kafka mirror maker tool is not respecting whitelist option

[ https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372740#comment-15372740 ] Ismael Juma commented on KAFKA-3950: [~xiaotao183], that's a good point, we can perhaps change the

Re: [VOTE] KIP-67: Queryable state for Kafka Streams

> 1. Re StreamsConfig.USER_ENDPOINT_CONFIG: > > I agree with Neha that Kafka Streams can provide the bare minimum APIs just > for host/port, and user's implemented layer can provide URL / proxy address > they want to build on top of it. In this case I second Neha's suggestion to give that

[jira] [Commented] (KAFKA-3950) kafka mirror maker tool is not respecting whitelist option

[ https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372705#comment-15372705 ] TAO XIAO commented on KAFKA-3950: - How about we still keep the filtering on client side and fix the broken

[jira] [Comment Edited] (KAFKA-3950) kafka mirror maker tool is not respecting whitelist option

[ https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372705#comment-15372705 ] TAO XIAO edited comment on KAFKA-3950 at 7/12/16 11:18 AM: --- How about we still

Re: [DISCUSS] KIP-62: Allow consumer to send heartbeats from a background thread

Hi, An issue I have regarding rebalancing, is that a call to poll() triggers the JoinGroupRequest when rebalancing is in process. In cases where a consumer is streaming more than a single batch at a time, there is no opportunity to attempt to flush any consumed batches through prior to the

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372565#comment-15372565 ] Andy Coates commented on KAFKA-3919: [~junrao] Good stuff. Look forward to hearing from you and

[jira] [Commented] (KAFKA-3954) Consumer should use internal topics information returned by the broker

[ https://issues.apache.org/jira/browse/KAFKA-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372557#comment-15372557 ] ASF GitHub Bot commented on KAFKA-3954: --- GitHub user ijuma opened a pull request:

[GitHub] kafka pull request #1613: KAFKA-3954; Consumer should use internal topics in...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1613 KAFKA-3954; Consumer should use internal topics information returned by the broker It previously hardcoded it. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (KAFKA-3954) Consumer should use internal topics information returned by the broker

Ismael Juma created KAFKA-3954: -- Summary: Consumer should use internal topics information returned by the broker Key: KAFKA-3954 URL: https://issues.apache.org/jira/browse/KAFKA-3954 Project: Kafka

[jira] [Created] (KAFKA-3953) start kafka fail

ffh created KAFKA-3953: -- Summary: start kafka fail Key: KAFKA-3953 URL: https://issues.apache.org/jira/browse/KAFKA-3953 Project: Kafka Issue Type: Bug Affects Versions: 0.8.2.2

[jira] [Commented] (KAFKA-3950) kafka mirror maker tool is not respecting whitelist option

[ https://issues.apache.org/jira/browse/KAFKA-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372516#comment-15372516 ] Ismael Juma commented on KAFKA-3950: [~omkreddy], yes, it's a current limitation that if you use

Re: [DISCUSS] KIP-66 Kafka Connect Transformers for messages

As Gwen said, my initial thought is that message transformations that are "more than trivial" should rather be done by Kafka Streams, rather than by Kafka Connect (for the reasons that Gwen mentioned). Transforming one message at a time would be a good fit for Kafka Connect. An important use case