Re: [DISCUSS] 0.10.2.2 bug fix release

+1 Thanks, Matthias! On Fri, Jun 8, 2018 at 1:58 AM, Ismael Juma wrote: > One more thing, I suggest we go with what we have for all 3 releases you > are doing. We should aim to make the big fix release process as smooth as > possible and we should strive to avoid last minute additions to olde

Re: [DISCUSS] 0.11.0.3 bug fix release

+1 Thanks, Matthias! On Fri, Jun 8, 2018 at 1:54 AM, Ismael Juma wrote: > +1, thanks! > > On Thu, 7 Jun 2018, 11:16 Matthias J. Sax, wrote: > > > Dear all, > > > > I want to propose a 0.11.0.3 bug fix release. 0.11.0.2 is 6 months old > > and a couple of critical fixes are available for 0.11.0

Re: [DISCUSS] 1.0.2 bug fix release

+1 Thank you, Matthias! On Fri, Jun 8, 2018 at 1:53 AM, Ismael Juma wrote: > +1, thanks! > > On Thu, 7 Jun 2018, 11:16 Matthias J. Sax, wrote: > > > Dear all, > > > > I want to propose a 1.0.2 bug fix release. 1.0.1 is 3 months old and a > > couple of critical fixes are available for 1.0.2. >

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

See

Re: kafka ack=all and min-isr

The key point is: if (leaderReplica.highWatermark.messageOffset >= requiredOffset) { The high watermark only moves when all the replicas in ISR have that particular offset. Does that clarify it? Ismael On Thu, Jun 7, 2018 at 10:31 PM Carl Samuelson wrote: > Hi > > Hopefully this is the correc

kafka ack=all and min-isr

Hi Hopefully this is the correct email address and forum for this. I asked this question on stack overflow, but did not get an answer: https://stackoverflow.com/questions/50689177/kafka-ack-all-and-min-isr *Summary* The docs and code comments for Kafka suggest that when the producer setting acks

[jira] [Resolved] (KAFKA-2445) Failed test: kafka.producer.ProducerTest > testSendWithDeadBroker FAILED

[ https://issues.apache.org/jira/browse/KAFKA-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2445. -- Resolution: Auto Closed > Failed test: kafka.producer.ProducerTest > testSendWithDeadBroker FAILED > --

Jenkins build is back to normal : kafka-trunk-jdk10 #185

See

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

See Changes: [me] KAFKA-7001: Rename errors.allowed.max property in Connect to [me] KAFKA-7002: Add a config property for DLQ topic's replication factor [junrao] KAFKA-7011 - Remove ResourceNameType field from

Jenkins build is back to normal : kafka-2.0-jdk8 #5

See

[jira] [Created] (KAFKA-7023) Kafka Streams RocksDB bulk loading config may not be honored with customized RocksDBConfigSetter

Liquan Pei created KAFKA-7023: - Summary: Kafka Streams RocksDB bulk loading config may not be honored with customized RocksDBConfigSetter Key: KAFKA-7023 URL: https://issues.apache.org/jira/browse/KAFKA-7023

[jira] [Created] (KAFKA-7022) Setting segment.bytes for a topic too small can cause ReplicaFetcher thread crash and in turn an unhealthy cluster due to under-replicated partitions

Koelli Mungee created KAFKA-7022: Summary: Setting segment.bytes for a topic too small can cause ReplicaFetcher thread crash and in turn an unhealthy cluster due to under-replicated partitions Key: KAFKA-7022 URL

Build failed in Jenkins: kafka-trunk-jdk10 #184

See Changes: [me] KAFKA-7001: Rename errors.allowed.max property in Connect to [me] KAFKA-7002: Add a config property for DLQ topic's replication factor [junrao] KAFKA-7011 - Remove ResourceNameType field from

Re: [DISCUSS] 0.10.2.2 bug fix release

One more thing, I suggest we go with what we have for all 3 releases you are doing. We should aim to make the big fix release process as smooth as possible and we should strive to avoid last minute additions to older release branches. We can be a bit more flexible for 1.0.2 since it's more recent.

Re: [DISCUSS] 0.11.0.3 bug fix release

+1, thanks! On Thu, 7 Jun 2018, 11:16 Matthias J. Sax, wrote: > Dear all, > > I want to propose a 0.11.0.3 bug fix release. 0.11.0.2 is 6 months old > and a couple of critical fixes are available for 0.11.0.3. > > Please find a list of all 16 resolved tickets here: > > > https://issues.apache.or

Re: [DISCUSS] 1.0.2 bug fix release

+1, thanks! On Thu, 7 Jun 2018, 11:16 Matthias J. Sax, wrote: > Dear all, > > I want to propose a 1.0.2 bug fix release. 1.0.1 is 3 months old and a > couple of critical fixes are available for 1.0.2. > > Please find a list of all 14 resolved tickets here: > > > https://issues.apache.org/jira/br

Re: [DISCUSS] 1.0.2 bug fix release

+1. On Thu, Jun 7, 2018 at 11:16 AM, Matthias J. Sax wrote: > Dear all, > > I want to propose a 1.0.2 bug fix release. 1.0.1 is 3 months old and a > couple of critical fixes are available for 1.0.2. > > Please find a list of all 14 resolved tickets here: > > https://issues.apache.org/jira/browse

Re: [DISCUSS] 0.10.2.2 bug fix release

+1 from me. Thanks Matthias. On Thu, Jun 7, 2018 at 4:34 PM, Ismael Juma wrote: > Thanks for doing this Matthias, +1. > > Ismael > > On Thu, Jun 7, 2018 at 1:50 PM Matthias J. Sax > wrote: > > > Dear all, > > > > I want to propose a 0.10.2.2 bug fix release. 0.10.2.1 is over a year > > old and

Re: [DISCUSS] 0.11.0.3 bug fix release

+1. On Thu, Jun 7, 2018 at 11:16 AM, Matthias J. Sax wrote: > Dear all, > > I want to propose a 0.11.0.3 bug fix release. 0.11.0.2 is 6 months old > and a couple of critical fixes are available for 0.11.0.3. > > Please find a list of all 16 resolved tickets here: > > https://issues.apache.org/ji

[jira] [Created] (KAFKA-7021) Source KTable checkpoint is not correct

Matthias J. Sax created KAFKA-7021: -- Summary: Source KTable checkpoint is not correct Key: KAFKA-7021 URL: https://issues.apache.org/jira/browse/KAFKA-7021 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-7011) Investigate if its possible to drop the ResourceNameType field from Java Resource class.

[ https://issues.apache.org/jira/browse/KAFKA-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-7011. Resolution: Fixed Merged the PR to trunk and 2.0 branch. > Investigate if its possible to drop the Resourc

Re: [DISCUSS] 0.10.2.2 bug fix release

Thanks for doing this Matthias, +1. Ismael On Thu, Jun 7, 2018 at 1:50 PM Matthias J. Sax wrote: > Dear all, > > I want to propose a 0.10.2.2 bug fix release. 0.10.2.1 is over a year > old and a couple of critical fixes are available for 0.10.2.2. > > Please find a list of all 24 resolved ticke

[jira] [Created] (KAFKA-7020) Error while renaming dir for topic_XXX in log dir YYY

wade wu created KAFKA-7020: -- Summary: Error while renaming dir for topic_XXX in log dir YYY Key: KAFKA-7020 URL: https://issues.apache.org/jira/browse/KAFKA-7020 Project: Kafka Issue Type: Bug

[DISCUSS] 0.10.2.2 bug fix release

Dear all, I want to propose a 0.10.2.2 bug fix release. 0.10.2.1 is over a year old and a couple of critical fixes are available for 0.10.2.2. Please find a list of all 24 resolved tickets here: https://issues.apache.org/jira/browse/KAFKA-6566?jql=project%20%3D%20KAFKA%20AND%20fixVersion%20%3D%2

[jira] [Resolved] (KAFKA-7008) Consider replacing the Resource field in AclBinding with a ResourceFilter or ResourceMatcher

[ https://issues.apache.org/jira/browse/KAFKA-7008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates resolved KAFKA-7008. Resolution: Won't Fix > Consider replacing the Resource field in AclBinding with a ResourceFilter o

[jira] [Created] (KAFKA-7019) Reduction the contention between metadata update and metadata read operation

Dong Lin created KAFKA-7019: --- Summary: Reduction the contention between metadata update and metadata read operation Key: KAFKA-7019 URL: https://issues.apache.org/jira/browse/KAFKA-7019 Project: Kafka

Build failed in Jenkins: kafka-2.0-jdk8 #4

See Changes: [wangguoz] KAFKA-6935: Add config for allowing optional optimization (#5071) -- [...truncated 972.41 KB...] kafka.server.epoch.LeaderEpochFileCacheTest > shouldRe

[jira] [Created] (KAFKA-7018) persist memberId for consumer restart

Boyang Chen created KAFKA-7018: -- Summary: persist memberId for consumer restart Key: KAFKA-7018 URL: https://issues.apache.org/jira/browse/KAFKA-7018 Project: Kafka Issue Type: Improvement

[DISCUSS] 1.0.2 bug fix release

Dear all, I want to propose a 1.0.2 bug fix release. 1.0.1 is 3 months old and a couple of critical fixes are available for 1.0.2. Please find a list of all 14 resolved tickets here: https://issues.apache.org/jira/browse/KAFKA-6937?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Resolved%2C%20C

[DISCUSS] 0.11.0.3 bug fix release

Dear all, I want to propose a 0.11.0.3 bug fix release. 0.11.0.2 is 6 months old and a couple of critical fixes are available for 0.11.0.3. Please find a list of all 16 resolved tickets here: https://issues.apache.org/jira/browse/KAFKA-6925?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Resolv

[jira] [Resolved] (KAFKA-6984) Question

[ https://issues.apache.org/jira/browse/KAFKA-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6984. -- Resolution: Information Provided Post these kind of queries to  [us...@kafka.apache.org|mailto:us...@ka

Jenkins build is back to normal : kafka-trunk-jdk10 #183

See

[jira] [Created] (KAFKA-7017) GroupCoordinator response error: Broker: Group coordinator not available

Sampath Kumar created KAFKA-7017: Summary: GroupCoordinator response error: Broker: Group coordinator not available Key: KAFKA-7017 URL: https://issues.apache.org/jira/browse/KAFKA-7017 Project: Kafka

Build failed in Jenkins: kafka-2.0-jdk8 #3

See Changes: [matthias] KAFKA-6538: Changes to enhance ByteStore exceptions thrown from [me] KAFKA-6991: Fix ServiceLoader issue with PluginClassLoader (KIP-285) -- [...trunc