Newbie JIRAs

Hi,I want to contribute to Apache Kafka.Can you please let me know any newbie JIRAs I could pick up?ThanksSrabasti

Re: [DISCUSS] Remove beta label from the new Java consumer

We have been using the (new) Java consumer API in 0.9.0.1 for a while now. We have some well known issues with it - like heart beats being part of the same thread causing the consumer to sometimes be considered dead. I understand that this has been fixed in 0.10.0.1 but we haven't yet had a cha

[jira] [Assigned] (KAFKA-4103) DumpLogSegments cannot print data from offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-4103: -- Assignee: Jason Gustafson > DumpLogSegments cannot print data from offsets topic >

[jira] [Resolved] (KAFKA-4062) Require --print-data-log if --offsets-decoder is enabled for DumpLogOffsets

[ https://issues.apache.org/jira/browse/KAFKA-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4062. -- Resolution: Fixed Fix Version/s: 0.10.1.0 Issue resolved by pull request

[jira] [Commented] (KAFKA-4062) Require --print-data-log if --offsets-decoder is enabled for DumpLogOffsets

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

[GitHub] kafka pull request #1797: KAFKA-4062: Require --print-data-log if --offsets-...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1797 --- 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 enab

[jira] [Commented] (KAFKA-4103) DumpLogSegments cannot print data from offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451076#comment-15451076 ] Ewen Cheslack-Postava commented on KAFKA-4103: -- cc [~hachikuji] since it look

[jira] [Created] (KAFKA-4103) DumpLogSegments cannot print data from offsets topic

Ewen Cheslack-Postava created KAFKA-4103: Summary: DumpLogSegments cannot print data from offsets topic Key: KAFKA-4103 URL: https://issues.apache.org/jira/browse/KAFKA-4103 Project: Kafka

Re: [VOTE] KIP-77: Improve Kafka Streams Join Semantics

+1 (binding) On Tue, Aug 30, 2016 at 5:33 PM Ewen Cheslack-Postava wrote: > +1 (binding) > > I think the major gap I notice in the PR is a lack of docs updates to > notify people of the change. Given these are improvements and streams is > still new, I wouldn't necessarily call them out as anyth

[DISCUSS] KIP-79 - ListOffsetRequest v1 and offsetForTime() method in new consumer.

Hi Kafka devs, I created KIP-79 to allow consumer to precisely query the offsets based on timestamp. In short we propose to : 1. add a ListOffsetRequest/ListOffsetResponse v1, and 2. add an offsetForTime() method in new consumer. The KIP wiki is the following: https://cwiki.apache.org/confluence

[jira] [Commented] (KAFKA-3410) Unclean leader election and "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450881#comment-15450881 ] Maysam Yabandeh commented on KAFKA-3410: [~wushujames] I do not think KAFKA-3924 i

[jira] [Updated] (KAFKA-4023) Add thread id as prefix in Kafka Streams thread logging

[ https://issues.apache.org/jira/browse/KAFKA-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-4023: --- Status: Patch Available (was: In Progress) > Add thread id as prefix in Kafka Streams thread logging

[jira] [Commented] (KAFKA-4023) Add thread id as prefix in Kafka Streams thread logging

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

[GitHub] kafka pull request #1803: KAFKA-4023: add thread/task id for logging prefix

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/1803 KAFKA-4023: add thread/task id for logging prefix You can merge this pull request into a Git repository by running: $ git pull https://github.com/bbejeck/kafka KAFKA-4023_add_thread_id_prefix

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450732#comment-15450732 ] Alex Loddengaard commented on KAFKA-3144: - I'll pile on another feature request: i

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450713#comment-15450713 ] Jun Rao commented on KAFKA-3144: Related to this. It will also be useful to optionally sho

Re: [DISCUSS] KIP-78: Cluster Id

The KIP doc is well written, thanks Ismael! About logging / debugging with the cluster id: I think the random UUID itself may not be very helpful for human-readable debugging information, and we'd better use the cluster name mentioned in future work in logging. Guozhang On Tue, Aug 30, 2016 at

Re: [VOTE] KIP-77: Improve Kafka Streams Join Semantics

+1 (binding) I think the major gap I notice in the PR is a lack of docs updates to notify people of the change. Given these are improvements and streams is still new, I wouldn't necessarily call them out as anything critical, but the changes should be noted somewhere. -Ewen On Tue, Aug 30, 2016

[jira] [Commented] (KAFKA-3410) Unclean leader election and "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450532#comment-15450532 ] James Cheng commented on KAFKA-3410: KAFKA-3924 has not fixed this issue. I followed

Re: [VOTE] KIP-33 - Add a time based log index

Hi folks, Here is another update on the change of time based log rolling. After the latest implementation, we encountered KAFKA-4099. The issue is that if users move replicas, for the messages in the old segments, the new replica will create one log segment for each message. The root cause of thi

Re: [VOTE] KIP-77: Improve Kafka Streams Join Semantics

+1 (binding) Thanks! On Tue, Aug 30, 2016 at 2:42 AM, Damian Guy wrote: > +1 > > On Mon, 29 Aug 2016 at 18:07 Eno Thereska wrote: > > > +1 (non-binding) > > > > > On 29 Aug 2016, at 12:22, Bill Bejeck wrote: > > > > > > +1 > > > > > > On Mon, Aug 29, 2016 at 5:50 AM, Matthias J. Sax < > matth

[jira] [Commented] (KAFKA-1981) Make log compaction point configurable

[ https://issues.apache.org/jira/browse/KAFKA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450387#comment-15450387 ] Eric Wasserman commented on KAFKA-1981: --- Opened new pull request at: https://github.

[jira] [Commented] (KAFKA-4099) Change the time based log rolling to base on the file create time instead of timestamp of the first message.

[ https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450309#comment-15450309 ] Jun Rao commented on KAFKA-4099: [~becket_qin], thanks for the proposal. Your suggestion s

Kafka unable to process message

Hi there, What does the below error mean and how to avoid this? I see this error one of the kafkaServer.out file when other broker is down. And not able to process any message as we see o.a.k.c.c.i.AbstractCoordinator - Issuing group metadata request to broker 5 from application log [2016-08

[jira] [Commented] (KAFKA-4099) Change the time based log rolling to base on the file create time instead of timestamp of the first message.

[ https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450166#comment-15450166 ] Jiangjie Qin commented on KAFKA-4099: - [~junrao] Any thoughts? Thanks. > Change the t

[GitHub] kafka pull request #1756: KAFKA-4058: Failure in org.apache.kafka.streams.in...

Github user mjsax closed the pull request at: https://github.com/apache/kafka/pull/1756 --- 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 enabl

[jira] [Commented] (KAFKA-4058) Failure in org.apache.kafka.streams.integration.ResetIntegrationTest.testReprocessingFromScratchAfterReset

[ https://issues.apache.org/jira/browse/KAFKA-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450063#comment-15450063 ] ASF GitHub Bot commented on KAFKA-4058: --- Github user mjsax closed the pull request a

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

See Changes: [wangguoz] KAFKA-4058: Failure in -- [...truncated 5728 lines...] org.apache.kafka.streams.kstream.UnlimitedWindowsTest > shouldIncludeRecordsThatHappenedAfterWindowStart PASSED

[jira] [Commented] (KAFKA-3993) Console producer drops data

[ https://issues.apache.org/jira/browse/KAFKA-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15450054#comment-15450054 ] Roger Hoover commented on KAFKA-3993: - Thanks, [~cotedm]. I tried to set acks=all but

[jira] [Comment Edited] (KAFKA-4095) When a topic is deleted and then created with the same name, 'committed' offsets are not reset

[ https://issues.apache.org/jira/browse/KAFKA-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1544#comment-1544 ] Vahid Hashemian edited comment on KAFKA-4095 at 8/30/16 8:13 PM: ---

[jira] [Commented] (KAFKA-4095) When a topic is deleted and then created with the same name, 'committed' offsets are not reset

[ https://issues.apache.org/jira/browse/KAFKA-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1544#comment-1544 ] Vahid Hashemian commented on KAFKA-4095: [~glikson] I believe what you are observi

Re: Kafka KIP meeting Aug 30 at 11:00am PST

The following are the notes from today's KIP discussion. - KIP48 (delegation tokens): Harsha will update the wiki with more details on how to use delegation tokens and how to configure it. - KIP-78 (cluster id): There was discussion on adding human readable tags later. No major concern

[jira] [Commented] (KAFKA-3984) Broker doesn't retry reconnecting to an expired Zookeeper connection

[ https://issues.apache.org/jira/browse/KAFKA-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449702#comment-15449702 ] Steve Niemitz commented on KAFKA-3984: -- A related issue here is ANY exception occurri

Re: [DISCUSS] KIP-72 Allow Sizing Incoming Request Queue in Bytes

My apologies for the delay in response. I agree with the concerns about OOM reading from the actual sockets and blocking the network threads - messing with the request queue itself would not do. I propose instead a memory pool approach - the broker would have a non blocking memory pool. upon read

[GitHub] kafka pull request #1802: wrong property was mentioned in doc

GitHub user yourspraveen opened a pull request: https://github.com/apache/kafka/pull/1802 wrong property was mentioned in doc max.fetch.wait is mentioned in document where it should have been fetch.wait.max.ms You can merge this pull request into a Git repository by running: $

[GitHub] kafka pull request #1801: MINOR: Include TopicPartition in warning when log ...

GitHub user dpkp opened a pull request: https://github.com/apache/kafka/pull/1801 MINOR: Include TopicPartition in warning when log cleaner resets dirty offset Typically this error condition is caused by topic-level configuration issues, so it is useful to say include which topic p

ApacheCon Seville CFP closes September 9th

It's traditional. We wait for the last minute to get our talk proposals in for conferences. Well, the last minute has arrived. The CFP for ApacheCon Seville closes on September 9th, which is less than 2 weeks away. It's time to get your talks in, so that we can make this the best ApacheCon yet. I

[jira] [Commented] (KAFKA-4101) java.lang.IllegalStateException in org.apache.kafka.common.network.Selector.channelOrFail

[ https://issues.apache.org/jira/browse/KAFKA-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449055#comment-15449055 ] Andrey Savov commented on KAFKA-4101: - Yes, there were a lot of closing sockets due to

[jira] [Commented] (KAFKA-2063) Bound fetch response size

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449045#comment-15449045 ] ASF GitHub Bot commented on KAFKA-2063: --- Github user nepal closed the pull request a

[GitHub] kafka pull request #1683: KAFKA-2063: Add possibility to bound fetch respons...

Github user nepal closed the pull request at: https://github.com/apache/kafka/pull/1683 --- 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 enabl

Re: [DISCUSS] KIP-78: Cluster Id

Hi Harsha, It's a good question. If your broker connects to a different zookeeper root (whether on the same server or not), the outcome depends on whether a cluster id already exists there. If it does, then that cluster id will be used. If not, a new cluster id will be generated. The existing KIP

Re: [DISCUSS] KIP-78: Cluster Id

Hi Gwen, That's a good point. I updated the KIP to mention that. Thanks, Ismael On Sun, Aug 28, 2016 at 12:47 AM, Gwen Shapira wrote: > Thanks Ismael, this looks great. > > One of the things you mentioned is that cluster ID will be useful in > log aggregation. Perhaps it makes sense to include

[jira] [Updated] (KAFKA-3282) Change tools to use new consumer if zookeeper is not specified

[ https://issues.apache.org/jira/browse/KAFKA-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3282: --- Description: This only applies to tools that support the new consumer and it's similar to what we did

[jira] [Updated] (KAFKA-3282) Change tools to use new consumer if zookeeper is not specified

[ https://issues.apache.org/jira/browse/KAFKA-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3282: --- Summary: Change tools to use new consumer if zookeeper is not specified (was: Change tools to use --n

[jira] [Commented] (KAFKA-3282) Change tools to use --new-consumer by default and introduce --old-consumer

[ https://issues.apache.org/jira/browse/KAFKA-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448837#comment-15448837 ] Ismael Juma commented on KAFKA-3282: PR link https://github.com/apache/kafka/pull/1376

[jira] [Updated] (KAFKA-3282) Change tools to use --new-consumer by default

[ https://issues.apache.org/jira/browse/KAFKA-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3282: --- Summary: Change tools to use --new-consumer by default (was: Change tools to use --new-consumer by de

[jira] [Commented] (KAFKA-3283) Consider marking the new consumer as production-ready

[ https://issues.apache.org/jira/browse/KAFKA-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448807#comment-15448807 ] Ismael Juma commented on KAFKA-3283: [~hachikuji], do you think you could do a PR for

Re: [DISCUSS] Remove beta label from the new Java consumer

Thanks for the feedback everyone. Since Harsha said that he is OK either way and everyone else is in favour, I think we should go ahead with this. Since we committed to API stability for the new Java consumer in 0.10.0.0 via KIP-45, this is simply a documentation change and I don't think we need an

Question regarding Producer and Duplicates

Hi all, I am using kafka_2.11-0.10.0.1, my understanding is that the producer API batches records per partition to send efficient requests. We can configure batch.size to increase the throughtput. However, in case of failure all records within the batch failed ? If that is true, does that mean t

Re: [VOTE] KIP-77: Improve Kafka Streams Join Semantics

+1 On Mon, 29 Aug 2016 at 18:07 Eno Thereska wrote: > +1 (non-binding) > > > On 29 Aug 2016, at 12:22, Bill Bejeck wrote: > > > > +1 > > > > On Mon, Aug 29, 2016 at 5:50 AM, Matthias J. Sax > > wrote: > > > >> I’d like to initiate the voting process for KIP-77: > >> > >> https://cwiki.apache.o

[jira] [Assigned] (KAFKA-4081) Consumer API consumer new interface commitSyn does not verify the validity of offset

[ https://issues.apache.org/jira/browse/KAFKA-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison reassigned KAFKA-4081: - Assignee: Mickael Maison > Consumer API consumer new interface commitSyn does not verify