Build failed in Jenkins: kafka-2.1-jdk8 #44

See Changes: [matthias] KAFKA-7534: Error in flush calling close may prevent underlying store -- [...truncated 896.93 KB...] kafka.coordinator.transaction.TransactionCoordin

Build failed in Jenkins: kafka-1.0-jdk7 #250

See Changes: [matthias] KAFKA-7534: Error in flush calling close may prevent underlying store [mjsax] MINOR: Increase timeout and add more context to error message (#5840) ---

[jira] [Created] (KAFKA-7558) Ability for consumer to indicate no intention to commit

Alex Rykov created KAFKA-7558: - Summary: Ability for consumer to indicate no intention to commit Key: KAFKA-7558 URL: https://issues.apache.org/jira/browse/KAFKA-7558 Project: Kafka Issue Type: I

Jenkins build is back to normal : kafka-trunk-jdk11 #60

See

Build failed in Jenkins: kafka-1.1-jdk7 #224

See Changes: [matthias] KAFKA-7534: Error in flush calling close may prevent underlying store -- [...truncated 1.51 MB...] K extends Object declared in interface KGroup

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

See

[jira] [Created] (KAFKA-7557) optimize LogManager.truncateFullyAndStartAt()

Jun Rao created KAFKA-7557: -- Summary: optimize LogManager.truncateFullyAndStartAt() Key: KAFKA-7557 URL: https://issues.apache.org/jira/browse/KAFKA-7557 Project: Kafka Issue Type: Bug Affects V

[jira] [Resolved] (KAFKA-7352) KIP-368: Allow SASL Connections to Periodically Re-Authenticate

[ https://issues.apache.org/jira/browse/KAFKA-7352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-7352. --- Resolution: Fixed Reviewer: Rajini Sivaram > KIP-368: Allow SASL Connections to Periodi

Build failed in Jenkins: kafka-trunk-jdk11 #59

See Changes: [github] MINOR: Remove unused commitSync in ConsoleConsumer (#5845) -- [...truncated 2.34 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldFai

Re: [DISCUSS] KIP-385: Provide configuration allowing consumer to no throw away prefetched data

Thanks for participating the discussion. Indeed, I learned quite a lot. Will take a look at the patch as well and spend some time hunting for some other interesting issue to work on :) Cheers, Zahari On Fri, Oct 26, 2018 at 8:49 PM Colin McCabe wrote: > Hi Zahari, > > I think we can retire the

Re: Kafka-node: Kafka client keeps sending request to broker which went down

Hi Shashank, kafka-node is not developed by Apache or the Apache Kafka project. I don't think anyone here has looked at that code. I have heard reports from the field that kafka-node has some very serious bugs, such as not retrying failed requests at all in some circumstances. I do not recom

Re: [VOTE] KIP-349 Priorities for Source Topics

On Thu, Oct 25, 2018, at 18:16, n...@afshartous.com wrote: > > The reporter of KAFKA-6690 (Bala) replied in the JIra ticket to my > question to elaborate about his use-case. I don’t think he’s on the dev > list. Here’s his response: > > Bala: Sorry about the delay in reply. We use Kafka

Re: [DISCUSS] KIP-385: Provide configuration allowing consumer to no throw away prefetched data

Hi Zahari, I think we can retire the KIP, since the KAFKA-7548 patch should solve the issue without any changes that require a KIP. This is actually the best thing we could do for our users, since things will "just work" more efficiently without a lot of configuration knobs. I think you did a

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

See Changes: [ismael] KAFKA-7532: Clean-up controller log when shutting down brokers (#5831) -- [...truncated 2.83 MB...] org.apache.kafka.streams.test.OutputVerifierTest

RE: Contribution request for KAFKA-2607

Thanks, I'll do it! -Original Message- From: Harsha Chintalapani Sent: 26 October, 2018 6:08 PM To: dev@kafka.apache.org Subject: Re: Contribution request for KAFKA-2607 I added you to Contributors in JIRA. You should be able to assign it yourself. -Harsha On Oct 26, 2018, 11:05 AM -04

Re: Contribution request for KAFKA-2607

I added you to Contributors in JIRA. You should be able to assign it yourself. -Harsha On Oct 26, 2018, 11:05 AM -0400, dev@kafka.apache.org, wrote: > > Al11

Contribution request for KAFKA-2607

Hello! I would like to help with task https://issues.apache.org/jira/browse/KAFKA-2607, as existing pull request is completely outdated. Please assign it to me, my jira account is Al11

Re: Frequent under-replicated partitions

Thanks Mani. I will monitor them. On Fri, Oct 26, 2018 at 3:34 PM Manikumar wrote: > We can monitor below replica related metrics. Try tuning " > replica.lag.time.max.ms" , "replica.fetch.max.bytes" . > look for logs starting with "Shrinking ISR for partition ...". > > kafka.server:type=Replica

[jira] [Created] (KAFKA-7556) KafkaConsumer.beginningOffsets does not return actual first offsets

Robert V created KAFKA-7556: --- Summary: KafkaConsumer.beginningOffsets does not return actual first offsets Key: KAFKA-7556 URL: https://issues.apache.org/jira/browse/KAFKA-7556 Project: Kafka Issu

Re: [VOTE] 2.1.0 RC0

minor observation: config sections are empty in the documentation page. http://kafka.apache.org/21/documentation.html#producerconfigs On Wed, Oct 24, 2018 at 10:49 PM Ted Yu wrote: > +1 > > InternalTopicIntegrationTest failed during test suite run but passed with > rerun. > > On Wed, Oct 24, 201

[jira] [Resolved] (KAFKA-7532) Missing stringification in error message "Removed ArrayBuffer() from list of shutting down brokers. (kafka.controller.KafkaController)"

[ https://issues.apache.org/jira/browse/KAFKA-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7532. Resolution: Fixed Fix Version/s: 2.0.2 2.1.1 > Missing stringification in

[jira] [Resolved] (KAFKA-7533) Kafka consumer does not poll after commit

[ https://issues.apache.org/jira/browse/KAFKA-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Nemenko resolved KAFKA-7533. Resolution: Fixed > Kafka consumer does not poll after commit > ---

Re: Frequent under-replicated partitions

We can monitor below replica related metrics. Try tuning " replica.lag.time.max.ms" , "replica.fetch.max.bytes" . look for logs starting with "Shrinking ISR for partition ...". kafka.server:type=ReplicaManager,name=IsrShrinksPerSec kafka.server:type=ReplicaManager,name=IsrExpandsPerSec kafka.serv