[jira] [Updated] (KAFKA-5260) Producer should not send AbortTxn unless transaction has actually begun

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

[jira] [Commented] (KAFKA-5260) Producer should not send AbortTxn unless transaction has actually begun

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

[GitHub] kafka pull request #3126: KAFKA-5260: Producer should not send AbortTxn unle...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3126 --- 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-5316) Log cleaning can increase message size and cause cleaner to crash with buffer overflow

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

[GitHub] kafka pull request #3165: KAFKA-5316: LogCleaner should account for larger r...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3165 KAFKA-5316: LogCleaner should account for larger record sets after cleaning You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

RE?? [DISCUSS] KIP-148: Add a connect timeout for client

>I think that is exactly what David cares (please correct me if I'm wrong): >for some request I would like to wait long enough for it to be completed, >like join-group request; while at the same time if it has encountered some >issues while trying to connect to the broker to send the join group

[DISCUSS] KIP-165: Extend Interactive Queries for return latest update timestamp per key

Dear community, I want to share KIP-165 [1] based on issue KAFKA-4304 [2]. I would like to get your comments. [1] https://cwiki.apache.org/confluence/display/KAFKA/KIP-165%3A+Extend+Interactive+Queries+for+return+latest+update+timestamp+per+key [2]

[jira] [Commented] (KAFKA-5338) There is a Misspell in ResetIntegrationTest

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

[GitHub] kafka pull request #3159: [KAFKA-5338]There is a Misspell in ResetIntegratio...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3159 --- 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-5338) There is a Misspell in ResetIntegrationTest

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

[jira] [Assigned] (KAFKA-5338) There is a Misspell in ResetIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-5338: Assignee: hejiefang > There is a Misspell in ResetIntegrationTest >

Re: [DISCUSS] KIP-148: Add a connect timeout for client

On Wed, May 24, 2017 at 9:59 AM, Colin McCabe wrote: > On Tue, May 23, 2017, at 19:07, Guozhang Wang wrote: > > I think using a single config to cover end-to-end latency with connecting > > and request round-trip may not be best appropriate since 1) some request > > may need

Re: Jira-Spam on Dev-Mailinglist

I agree. Guozhang, do you know how to implement the suggestion? JIRA to Apache Infra? Or is this something we can do ourselves somehow? On Mon, May 29, 2017 at 9:33 PM Guozhang Wang wrote: > I share your pains. Right now I use filters on my email accounts and it has > been

[jira] [Commented] (KAFKA-5150) LZ4 decompression is 4-5x slower than Snappy on small batches / messages

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

[GitHub] kafka pull request #3164: KAFKA-5150: Reduce lz4 decompression overhead (wit...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3164 KAFKA-5150: Reduce lz4 decompression overhead (without thread local buffers) Temporary PR that has additional changes over https://github.com/apache/kafka/pull/2967 for comparison. You can merge

Re: Jira-Spam on Dev-Mailinglist

I share your pains. Right now I use filters on my email accounts and it has been down to about 25 per day. I think setup a separate mailing list for jirabot and jenkins auto generated emails is a good idea. Guozhang On Mon, May 29, 2017 at 12:58 AM, wrote: > Hello

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

Hey Eno, I think this makes sense. I do think people who spend time running production stream processing systems will, over time, end up strongly preferring the current behavior of failing and fixing the root problem rather than skipping, but we don't need to force this on people as long as the

Re: Kafka Loss of messages

+Vinayak On 26 May 2017 at 21:44, Jun Rao wrote: > Hi, Vinayak, > > I am not sure that KAFKA-1561 as reported is an issue. Could you describe > the scenario in your test in that jira in a bit more detail? > > Thanks, > > Jun > > On Fri, May 26, 2017 at 5:58 AM, Vinayak Sharma

[jira] [Created] (KAFKA-5345) Some socket connections not closed after restart of Kafka Streams

Jeroen van Wilgenburg created KAFKA-5345: Summary: Some socket connections not closed after restart of Kafka Streams Key: KAFKA-5345 URL: https://issues.apache.org/jira/browse/KAFKA-5345

[jira] [Updated] (KAFKA-5008) Kafka-Clients not OSGi ready

[ https://issues.apache.org/jira/browse/KAFKA-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc updated KAFKA-5008: Reviewer: Neha Narkhede Issue Type: Improvement (was: Bug) > Kafka-Clients not OSGi ready >

Re: Kafka Loss of messages

Hi Jun, Please ignore the earlier mail. I have a Kafka Cluster running on AWS machines i.e. 3 Zookeeper and 2 Brokers. I am trying to scale the brokers while producing and consuming messages. I am sending 1000 messages by batch producer every second for 200 seconds for the following topics:

Re: Kafka Loss of messages

Hi Jun, 0.10.0.0 I have a Kafka Cluster running on AWS instances. I am trying to scale broker up and down while simultaneously using the cluster to produce and consume messages. On 29 May 2017 at 13:03, Sanket Dhopeshwarkar wrote: > +Vinayak > > On 26 May 2017 at 21:44, Jun

Re: [DISCUSS] KIP-164 Add unavailablePartitionCount and per-partition Unavailable metrics

Hi, Sounds good. I was sure this existed already for some reason :) On Sun, May 28, 2017 at 11:06 AM Dong Lin wrote: > Hi, > > We created KIP-164 to propose adding per-partition metric *Unavailable* and > per-broker metric *UnavailablePartitionCount* > > The KIP wik can be

Re?? Re: Re: [DISCUSS] KIP-148: Add a connect timeout for client

Hi Rajini Thanks for the comment and kindly to add another config for the flexibility. The limitation in the consumer with request.timeout.ms is need to fix, but as Guozhang's comment, this is orthogonal to this KIP, we can fix it by another KIP or issue. Thanks, David

Jira-Spam on Dev-Mailinglist

Hello everyone I find it hard to follow this mailinglist due to all the mails generated by Jira. Just over this weekend there are 240 new mails. Would it be possible to setup something like j...@kafka.apache.org where everyone can subscribe interested in those Jira mails? Right now I am going

[jira] [Updated] (KAFKA-5343) MockProducer should not handle send/ProducerRecord after close

[ https://issues.apache.org/jira/browse/KAFKA-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Grotzke updated KAFKA-5343: -- Description: Currently {{MockProducer}} implements {{close}} with void, i.e. it just does

[jira] [Updated] (KAFKA-5344) Change message.timestamp.difference.max.ms back to Long.MaxValue

[ https://issues.apache.org/jira/browse/KAFKA-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-5344: Status: Patch Available (was: Open) > Change message.timestamp.difference.max.ms back to