[jira] [Updated] (KAFKA-5396) Consumer reading uninterrupted from beginning of log can read the same message multiple times.

[ https://issues.apache.org/jira/browse/KAFKA-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5396: Summary: Consumer reading uninterrupted from beginning of log can read the same message multiple tim

[jira] [Commented] (KAFKA-5396) Consumer reading from beginning of log can read the same message multiple times.

[ https://issues.apache.org/jira/browse/KAFKA-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040316#comment-16040316 ] Apurva Mehta commented on KAFKA-5396: - 38012 out of 38500 duplicates were from this on

[jira] [Commented] (KAFKA-5396) Consumer reading from beginning of log can read the same message multiple times.

[ https://issues.apache.org/jira/browse/KAFKA-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040309#comment-16040309 ] Apurva Mehta commented on KAFKA-5396: - Running the following {noformat} amehta-macboo

[jira] [Commented] (KAFKA-5396) Consumer reading from beginning of log can read the same message multiple times.

[ https://issues.apache.org/jira/browse/KAFKA-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040301#comment-16040301 ] Apurva Mehta commented on KAFKA-5396: - Also, there are no aborted transactions in the

[jira] [Commented] (KAFKA-5396) Consumer reading from beginning of log can read the same message multiple times.

[ https://issues.apache.org/jira/browse/KAFKA-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040297#comment-16040297 ] Apurva Mehta commented on KAFKA-5396: - The logs for the entire run (including debug br

[jira] [Updated] (KAFKA-5396) Consumer reading from beginning of log can read the same message multiple times.

[ https://issues.apache.org/jira/browse/KAFKA-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5396: Attachment: KAFKA-5396.tar.gz > Consumer reading from beginning of log can read the same message mul

[jira] [Created] (KAFKA-5396) Consumer reading from beginning of log can read the same message multiple times.

Apurva Mehta created KAFKA-5396: --- Summary: Consumer reading from beginning of log can read the same message multiple times. Key: KAFKA-5396 URL: https://issues.apache.org/jira/browse/KAFKA-5396 Project:

Re: [DISCUSS] KIP-113: Support replicas movement between log directories

I think Ram's point is that in place failure is pretty complicated, and this is meant to be a cost saving feature, we should construct an argument for it grounded in data. Assume an annual failure rate of 1% (reasonable, but data is available online), and assume it takes 3 days to get the drive re

[jira] [Commented] (KAFKA-5395) Distributed Herder Deadlocks on Shutdown

[ https://issues.apache.org/jira/browse/KAFKA-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040257#comment-16040257 ] Michael Jaschob commented on KAFKA-5395: Probably didn't mean to synchronize the p

[jira] [Created] (KAFKA-5395) Distributed Herder Deadlocks on Shutdown

Michael Jaschob created KAFKA-5395: -- Summary: Distributed Herder Deadlocks on Shutdown Key: KAFKA-5395 URL: https://issues.apache.org/jira/browse/KAFKA-5395 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-5385) Transactional Producer allows batches to expire and commits transactions regardless

[ https://issues.apache.org/jira/browse/KAFKA-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5385: Status: Patch Available (was: In Progress) > Transactional Producer allows batches to expire and co

[jira] [Commented] (KAFKA-5385) Transactional Producer allows batches to expire and commits transactions regardless

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

[GitHub] kafka pull request #3252: KAFKA-5385: ProducerBatch expiry should go through...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3252 KAFKA-5385: ProducerBatch expiry should go through Sender.failBatch Before this patch, we would call `producerBatch.done` directly from the accumulator when expiring batches. This meant that we woul

[jira] [Commented] (KAFKA-1044) change log4j to slf4j

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040126#comment-16040126 ] Ewen Cheslack-Postava commented on KAFKA-1044: -- [~viktorsomogyi] I've added y

[jira] [Assigned] (KAFKA-1044) change log4j to slf4j

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-1044: Assignee: Ewen Cheslack-Postava > change log4j to slf4j >

[jira] [Assigned] (KAFKA-1044) change log4j to slf4j

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-1044: Assignee: Viktor Somogyi (was: Ewen Cheslack-Postava) > change log4j to sl

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

See

Build failed in Jenkins: kafka-0.11.0-jdk7 #110

See Changes: [wangguoz] MINOR: remove ignore annotations in Streams EOS integration test -- [...truncated 953.78 KB...] kafka.controller.ControllerIntegrationTest > testP

Re: Changing JIRA notifications to remove Single Email Address (dev@kafka.apache.org)

What about also adding "Issue Resolved" to the events that hit dev? While I don't generally care about updates on issue progress, I do want to know when issues are resolved in case undocumented behavior that I may have accidentally been relying on may have changed. With or without this suggested

Re: [DISCUSS] KIP-113: Support replicas movement between log directories

Hey Sriram, Thanks for taking time to review the KIP. Please see below my answers to your questions: >1. Could you pick a hardware/Kafka configuration and go over what is the >average disk/partition repair/restore time that we are targeting for a >typical JBOD setup? We currently don't have this

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

See Changes: [jason] KAFKA-5366; Add concurrent reads to transactions system test -- [...truncated 2.54 MB...] org.apache.kafka.connect.runtime.distributed.DistributedHer

Re: KIP-160 - Augment KStream.print() to allow users pass in extra parameters in the printed string

I see. LGTM. On Tue, Jun 6, 2017 at 6:07 AM, Bill Bejeck wrote: > +1 on adding node name to the `RecordContext` > > -Bill > > On Mon, Jun 5, 2017 at 6:24 PM, Jeyhun Karimov > wrote: > > > I agree with Matthias's comment. Constructing RecordContext with more > > metadata seems more feasible for

[GitHub] kafka pull request #3251: MINOR: remove ignore annotations in Streams EOS in...

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

Re: Changing JIRA notifications to remove Single Email Address (dev@kafka.apache.org)

Agree on proposal. On Tue, Jun 6, 2017 at 3:55 PM Guozhang Wang wrote: > Just clarifying: currently all events are notified to the following > recipients: > > All Watchers > Current Assignee > Reporter > Single Email Address (dev@kafka.apache.org) > > > So by removing the last one, other related

[jira] [Assigned] (KAFKA-5021) Update Message Delivery Semantics section to take into account KIP-98

[ https://issues.apache.org/jira/browse/KAFKA-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-5021: -- Assignee: Jason Gustafson > Update Message Delivery Semantics section to take into acco

[jira] [Commented] (KAFKA-1044) change log4j to slf4j

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039920#comment-16039920 ] Viktor Somogyi commented on KAFKA-1044: --- Hi, I'm new to Kafka and was searching for

[jira] [Commented] (KAFKA-5366) Add cases for concurrent transactional reads and writes in system tests

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

[GitHub] kafka pull request #3217: KAFKA-5366: Add concurrent reads to transactions s...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3217 --- 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] [Updated] (KAFKA-5366) Add cases for concurrent transactional reads and writes in system tests

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

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

Thanks for the comprehensive summary! Personally I'd prefer the option of passing RecordContext as an additional parameter into he overloaded function. But I'm also open to other arguments if there are sth. that I have overlooked. Guozhang On Mon, Jun 5, 2017 at 3:19 PM, Jeyhun Karimov wrote:

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Jeyhun, Matthias: Thanks for the explanation, I overlooked the repartition argument previously. 1) Based on that argument I'm convinced of having ValueMapperWithKey / ValueJoinerWithKey / ValueTransformerWithKey; though I'm still not convinced with ReducerWithKey and InitializerWithKey since for

[jira] [Commented] (KAFKA-5329) Replica list in the metadata cache on the broker may have different order from zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039836#comment-16039836 ] Ismael Juma commented on KAFKA-5329: [~becket_qin], I had not understood how it impact

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

Kyle, Thanks a lot for the updated KIP. It looks good to me. Guozhang On Fri, Jun 2, 2017 at 5:37 AM, Jim Jagielski wrote: > This makes much more sense to me. +1 > > > On Jun 1, 2017, at 10:33 AM, Kyle Winkelman > wrote: > > > > I have updated the KIP and my PR. Let me know what you think.

Re: Changing JIRA notifications to remove Single Email Address (dev@kafka.apache.org)

Just clarifying: currently all events are notified to the following recipients: All Watchers Current Assignee Reporter Single Email Address (dev@kafka.apache.org) So by removing the last one, other related people (watcher, assignee, reporter) will still be notified. Guozhang On Tue, Jun 6,

Changing JIRA notifications to remove Single Email Address (dev@kafka.apache.org)

(Changing the subject title to reflect on the proposal) Hey guys, In order to not drop the ball on the floor I'd like to kick off some proposals according to people's feedbacks on this issue. Feel free to brainstorm on different ideas: We change JIRA notifications to remove `Single Email Address

Re: [DISCUSS] KIP-167: Add a restoreAll method to StateRestoreCallback

Thanks for the updated KIP Bill, I have a couple of comments: 1) I'm assuming beginRestore / endRestore is called only once per store throughout the whole restoration process, and restoreAll is called per batch. In that case I feel we can set the StateRestoreContext as a second parameter in restor

[jira] [Updated] (KAFKA-5381) ERROR Uncaught exception in scheduled task 'delete-expired-consumer-offsets' (kafka.utils.KafkaScheduler)

[ https://issues.apache.org/jira/browse/KAFKA-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman updated KAFKA-5381: --- Description: We have a 6 node cluster of 0.10.0.1 brokers. Broker 4 had a hardware problem, so we re-

[jira] [Resolved] (KAFKA-5339) Transactions system test with hard broker bounces fails sporadically

[ https://issues.apache.org/jira/browse/KAFKA-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta resolved KAFKA-5339. - Resolution: Fixed This occurred only once, and the producer has had a lot of bugfixes since then.

[jira] [Updated] (KAFKA-5378) Last Stable Offset not returned in Fetch request

[ https://issues.apache.org/jira/browse/KAFKA-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5378: --- Status: Patch Available (was: In Progress) > Last Stable Offset not returned in Fetch request

Re: [VOTE] KIP-134: Delay initial consumer group rebalance

Hi Jun, The console consumer issue also came up in a conversation I was having recently. Seems like the config/server.properties change is a reasonable compromise given that we have other defaults that are for development. Ismael On Tue, Jun 6, 2017 at 10:59 PM, Jun Rao wrote: > Hi, Everyone,

Re: [VOTE] KIP-134: Delay initial consumer group rebalance

Hi, Everyone, Sorry for being late on this thread. I just came across this thread. I have a couple of concerns on this. (1) It seems the amount of delay will be application specific. So, it seems that it's better for the delay to be a client side config instead of a server side one? (2) When runni

[GitHub] kafka pull request #3251: MINOR: remove ignore annotations in Streams EOS in...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/3251 MINOR: remove ignore annotations in Streams EOS integration test You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka KMinor

[jira] [Commented] (KAFKA-4942) Kafka Connect: Offset committing times out before expected

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

[GitHub] kafka pull request #2730: KAFKA-4942 fixed the commitTimeoutMs being set bef...

Github user simplesteph closed the pull request at: https://github.com/apache/kafka/pull/2730 --- 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-5394) KafkaAdminClient#timeoutCallsInFlight does not work as expected

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

[GitHub] kafka pull request #3250: KAFKA-5394. KafkaAdminClient#timeoutCallsInFlight ...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/3250 KAFKA-5394. KafkaAdminClient#timeoutCallsInFlight does not work as ex… …pected * Rename KafkaClient#close to KafkaClient#forget to emphasize that it forgets the requests on a given conn

[GitHub] kafka pull request #2912: KAFKA-4942 Fix commitTimeoutMs being set before th...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2912 --- 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-4942) Kafka Connect: Offset committing times out before expected

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

[jira] [Resolved] (KAFKA-4942) Kafka Connect: Offset committing times out before expected

[ https://issues.apache.org/jira/browse/KAFKA-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4942. -- Resolution: Fixed Fix Version/s: 0.11.1.0 0.11.0.0 Iss

[jira] [Work started] (KAFKA-5385) Transactional Producer allows batches to expire and commits transactions regardless

[ https://issues.apache.org/jira/browse/KAFKA-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5385 started by Apurva Mehta. --- > Transactional Producer allows batches to expire and commits transactions > regar

[jira] [Resolved] (KAFKA-5375) Transactions: Concurrent transactional consumer loses messages when there are broker bounces

[ https://issues.apache.org/jira/browse/KAFKA-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta resolved KAFKA-5375. - Resolution: Fixed Assignee: Apurva Mehta (was: Jason Gustafson) This turned out to be due t

[jira] [Updated] (KAFKA-5364) Producer attempts to send transactional messages before adding partitions to transaction

[ https://issues.apache.org/jira/browse/KAFKA-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5364: Resolution: Fixed Status: Resolved (was: Patch Available) I am going to close this ticket.

[jira] [Updated] (KAFKA-5385) Transactional Producer allows batches to expire and commits transactions regardless

[ https://issues.apache.org/jira/browse/KAFKA-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5385: Labels: exactly-once (was: ) > Transactional Producer allows batches to expire and commits transact

[GitHub] kafka pull request #3249: MINOR: Fix docs; client no longer uses yammer metr...

GitHub user jklukas opened a pull request: https://github.com/apache/kafka/pull/3249 MINOR: Fix docs; client no longer uses yammer metrics Yammer metrics is no longer a dependency of the client, but the Monitoring section of the docs contradicts this. For quite some time, clients ha

[GitHub] kafka pull request #3244: MINOR: expose commit interval config for SimpleBen...

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

[GitHub] kafka pull request #3248: KAFKA-5378: Return LSO in FetchResponse plus some ...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3248 KAFKA-5378: Return LSO in FetchResponse plus some metrics You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-5378 Alternat

[jira] [Commented] (KAFKA-5378) Last Stable Offset not returned in Fetch request

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

Re: [VOTE] KIP-113 - Support replicas movement between log directories

Thanks to everyone who voted and provided feedback! This KIP is now adopted with 3 binding +1s (Jun, Joel, Becket) On Tue, Jun 6, 2017 at 10:36 AM, Becket Qin wrote: > +1 > > Thanks for the KIP, Dong. > > On Tue, Jun 6, 2017 at 10:20 AM, Jun Rao wrote: > > > Hi, Dong, > > > > Thanks for the KI

Re: [VOTE] KIP-113 - Support replicas movement between log directories

+1 Thanks for the KIP, Dong. On Tue, Jun 6, 2017 at 10:20 AM, Jun Rao wrote: > Hi, Dong, > > Thanks for the KIP. +1 from me. > > Jun > > On Mon, Apr 3, 2017 at 9:49 AM, Dong Lin wrote: > > > Hi all, > > > > It seems that there is no further concern with the KIP-113. We would like > > to start

Re: [VOTE] KIP-113 - Support replicas movement between log directories

Hi, Dong, Thanks for the KIP. +1 from me. Jun On Mon, Apr 3, 2017 at 9:49 AM, Dong Lin wrote: > Hi all, > > It seems that there is no further concern with the KIP-113. We would like > to start the voting process. The KIP can be found at > *https://cwiki.apache.org/confluence/display/KAFKA/KIP-

Re: [VOTE] KIP-162: Enable topic deletion by default

+1 (non-binding) Thanks, Bharat On Tue, Jun 6, 2017 at 9:21 AM, Ashwin Sinha wrote: > +1 > > On Tue, Jun 6, 2017 at 11:20 PM, Mickael Maison > wrote: > > > +1 (non binding), thanks > > > > On Tue, Jun 6, 2017 at 2:16 PM, Bill Bejeck wrote: > > > +1 > > > > > > -Bill > > > > > > On Tue, Jun 6,

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

See

[jira] [Created] (KAFKA-5394) KafkaAdminClient#timeoutCallsInFlight does not work as expected

Colin P. McCabe created KAFKA-5394: -- Summary: KafkaAdminClient#timeoutCallsInFlight does not work as expected Key: KAFKA-5394 URL: https://issues.apache.org/jira/browse/KAFKA-5394 Project: Kafka

[jira] [Commented] (KAFKA-1561) Data Loss for Incremented Replica Factor and Leader Election

[ https://issues.apache.org/jira/browse/KAFKA-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039226#comment-16039226 ] Vinayak Sharma commented on KAFKA-1561: --- Hi, [~junrao] I have Cluster consisting of

[GitHub] kafka pull request #3179: MINOR: update stream docs for kip-134

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

[GitHub] kafka pull request #3247: MINOR: log4j template should accept log_level

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/3247 MINOR: log4j template should accept log_level The log_level parameter is used in system tests in kafka.py. However the log4j template accepted that parameter in only one place. This led to a lar

Re: [VOTE] KIP-162: Enable topic deletion by default

+1 On Tue, Jun 6, 2017 at 11:20 PM, Mickael Maison wrote: > +1 (non binding), thanks > > On Tue, Jun 6, 2017 at 2:16 PM, Bill Bejeck wrote: > > +1 > > > > -Bill > > > > On Tue, Jun 6, 2017 at 9:08 AM, Ismael Juma wrote: > > > >> Thanks for the KIP, Gwen. +1 (binding). > >> > >> Ismael > >> > >

Re: [VOTE] KIP-162: Enable topic deletion by default

+1 (non binding), thanks On Tue, Jun 6, 2017 at 2:16 PM, Bill Bejeck wrote: > +1 > > -Bill > > On Tue, Jun 6, 2017 at 9:08 AM, Ismael Juma wrote: > >> Thanks for the KIP, Gwen. +1 (binding). >> >> Ismael >> >> On Tue, Jun 6, 2017 at 5:37 AM, Gwen Shapira wrote: >> >> > Hi, >> > >> > The discuss

[jira] [Resolved] (KAFKA-4948) Failure in kafka.admin.DescribeConsumerGroupTest.testDescribeExistingGroupWithNoMembersWithNewConsumer

[ https://issues.apache.org/jira/browse/KAFKA-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-4948. --- Resolution: Fixed Fix Version/s: 0.11.1.0 0.11.0.0 Issue resolved by

[jira] [Commented] (KAFKA-4948) Failure in kafka.admin.DescribeConsumerGroupTest.testDescribeExistingGroupWithNoMembersWithNewConsumer

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

[GitHub] kafka pull request #3246: KAFKA-4948: Wait for offset commit in test to fix ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3246 --- 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] [Created] (KAFKA-5393) in-memory state store memory issue

Kevin Chen created KAFKA-5393: - Summary: in-memory state store memory issue Key: KAFKA-5393 URL: https://issues.apache.org/jira/browse/KAFKA-5393 Project: Kafka Issue Type: Bug Compone

[jira] [Commented] (KAFKA-5390) First records in batch rejected but others accepted when rolling log

[ https://issues.apache.org/jira/browse/KAFKA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038969#comment-16038969 ] Ismael Juma commented on KAFKA-5390: If you want to do manual batching, you can simply

[jira] [Commented] (KAFKA-5390) First records in batch rejected but others accepted when rolling log

[ https://issues.apache.org/jira/browse/KAFKA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038950#comment-16038950 ] Magnus Reftel commented on KAFKA-5390: -- Yes and no =) It's good to know that batches

[jira] [Updated] (KAFKA-5391) Replace zkClient.delete* method with an equivalent zkUtils method

[ https://issues.apache.org/jira/browse/KAFKA-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balint Molnar updated KAFKA-5391: - Status: Patch Available (was: Open) > Replace zkClient.delete* method with an equivalent zkUtils

[GitHub] kafka pull request #3246: KAFKA-4948: Wait for offset commit in test to fix ...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3246 KAFKA-4948: Wait for offset commit in test to fix transient failure `DescribeConsumerGroupTest#testDescribeExistingGroupWithNoMembersWithNewConsumer` shuts down the consumer executor thread a

[jira] [Commented] (KAFKA-4948) Failure in kafka.admin.DescribeConsumerGroupTest.testDescribeExistingGroupWithNoMembersWithNewConsumer

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

[jira] [Commented] (KAFKA-5391) Replace zkClient.delete* method with an equivalent zkUtils method

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

[GitHub] kafka pull request #3245: KAFKA-5391 Replace zkClient.delete* method with an...

GitHub user baluchicken opened a pull request: https://github.com/apache/kafka/pull/3245 KAFKA-5391 Replace zkClient.delete* method with an equivalent zkUtills @ijuma can you please review. You can merge this pull request into a Git repository by running: $ git pull https://git

[jira] [Commented] (KAFKA-5390) First records in batch rejected but others accepted when rolling log

[ https://issues.apache.org/jira/browse/KAFKA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038927#comment-16038927 ] Ismael Juma commented on KAFKA-5390: `Log` has the following code: {code} // check me

[GitHub] kafka pull request #1052: Changes to KafkaApis and MetadataCache based on KA...

Github user fpj closed the pull request at: https://github.com/apache/kafka/pull/1052 --- 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 enabled

[jira] [Commented] (KAFKA-2073) Replace TopicMetadata request/response with o.a.k.requests.metadata

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

[jira] [Commented] (KAFKA-5070) org.apache.kafka.streams.errors.LockException: task [0_18] Failed to lock the state directory: /opt/rocksdb/pulse10/0_18

[ https://issues.apache.org/jira/browse/KAFKA-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038911#comment-16038911 ] Kevin Chen commented on KAFKA-5070: --- to fix the failure to start issue, I think you need

[jira] [Comment Edited] (KAFKA-5390) First records in batch rejected but others accepted when rolling log

[ https://issues.apache.org/jira/browse/KAFKA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038879#comment-16038879 ] Magnus Reftel edited comment on KAFKA-5390 at 6/6/17 1:28 PM: --

[jira] [Commented] (KAFKA-5390) First records in batch rejected but others accepted when rolling log

[ https://issues.apache.org/jira/browse/KAFKA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038879#comment-16038879 ] Magnus Reftel commented on KAFKA-5390: -- No, the server does not reject the batch - it

[GitHub] kafka pull request #3244: MINOR: expose commit interval config for testing

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/3244 MINOR: expose commit interval config for testing Expose the streams commit interval config for different testing scenarios. You can merge this pull request into a Git repository by running: $ g

Re: [VOTE] KIP-162: Enable topic deletion by default

+1 -Bill On Tue, Jun 6, 2017 at 9:08 AM, Ismael Juma wrote: > Thanks for the KIP, Gwen. +1 (binding). > > Ismael > > On Tue, Jun 6, 2017 at 5:37 AM, Gwen Shapira wrote: > > > Hi, > > > > The discussion has been quite positive, so I posted a JIRA, a PR and > > updated the KIP with the latest de

Re: [VOTE] KIP-162: Enable topic deletion by default

Thanks for the KIP, Gwen. +1 (binding). Ismael On Tue, Jun 6, 2017 at 5:37 AM, Gwen Shapira wrote: > Hi, > > The discussion has been quite positive, so I posted a JIRA, a PR and > updated the KIP with the latest decisions. > > Lets officially vote on the KIP: > https://cwiki.apache.org/confluen

Re: KIP-160 - Augment KStream.print() to allow users pass in extra parameters in the printed string

+1 on adding node name to the `RecordContext` -Bill On Mon, Jun 5, 2017 at 6:24 PM, Jeyhun Karimov wrote: > I agree with Matthias's comment. Constructing RecordContext with more > metadata seems more feasible for me. > > Cheers, > Jeyun > > On Mon, Jun 5, 2017 at 7:47 AM Matthias J. Sax > wrot

[jira] [Commented] (KAFKA-5390) First records in batch rejected but others accepted when rolling log

[ https://issues.apache.org/jira/browse/KAFKA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038844#comment-16038844 ] Ismael Juma commented on KAFKA-5390: The errors show what the issue is. The segment si

[jira] [Updated] (KAFKA-5390) First records in batch rejected but others accepted when rolling log

[ https://issues.apache.org/jira/browse/KAFKA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Reftel updated KAFKA-5390: - Attachment: kafka-sequence-2.tar.gz Updated to print results from the send callback. > First reco

[jira] [Commented] (KAFKA-5390) First records in batch rejected but others accepted when rolling log

[ https://issues.apache.org/jira/browse/KAFKA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038832#comment-16038832 ] Magnus Reftel commented on KAFKA-5390: -- Thanks for the quick reply! I tried switching

[jira] [Commented] (KAFKA-5364) Producer attempts to send transactional messages before adding partitions to transaction

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

[GitHub] kafka pull request #3231: KAFKA-5364: ensurePartitionAdded does not handle p...

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

Jenkins build is back to normal : kafka-0.11.0-jdk7 #103

See

[jira] [Updated] (KAFKA-5389) Replace zkClient.exists method with zkUtils.pathExists

[ https://issues.apache.org/jira/browse/KAFKA-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balint Molnar updated KAFKA-5389: - Status: Patch Available (was: In Progress) > Replace zkClient.exists method with zkUtils.pathExis

[GitHub] kafka pull request #3243: KAFKA-5389 Replace zkClient.exists method with zkU...

GitHub user baluchicken opened a pull request: https://github.com/apache/kafka/pull/3243 KAFKA-5389 Replace zkClient.exists method with zkUtils.pathExists @ijuma can you please review You can merge this pull request into a Git repository by running: $ git pull https://github.co

[jira] [Commented] (KAFKA-5389) Replace zkClient.exists method with zkUtils.pathExists

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

[jira] [Updated] (KAFKA-5387) [Kafka Producer] - expose cluster metadata

[ https://issues.apache.org/jira/browse/KAFKA-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart Vercammen updated KAFKA-5387: -- Description: Kafka producer has a method to expose the number of partitions for a specific topi

[jira] [Created] (KAFKA-5392) AdminClient leaking resources

Ismael Juma created KAFKA-5392: -- Summary: AdminClient leaking resources Key: KAFKA-5392 URL: https://issues.apache.org/jira/browse/KAFKA-5392 Project: Kafka Issue Type: Bug Reporter:

  1   2   >