Re: How can I get the first valid record's offset in a partition?

2018-02-12 Thread Kamal
When you get the exception and want to read from the first valid record offset. Use, consumer#seekToBeginning(partitions) https://kafka.apache.org/0100/javadoc/org/apache/kafka/clients/consumer/KafkaConsumer.html#seekToBeginning(java.util.Collection) On Mon, Feb 12, 2018 at 12:09 PM, York Zhang

[jira] [Created] (KAFKA-6554) Broker doesn't reject Produce request with inconsistent state

2018-02-12 Thread Simon Fell (JIRA)
Simon Fell created KAFKA-6554: - Summary: Broker doesn't reject Produce request with inconsistent state Key: KAFKA-6554 URL: https://issues.apache.org/jira/browse/KAFKA-6554 Project: Kafka Issue

[jira] [Created] (KAFKA-6553) Consumer consumed committed messages

2018-02-12 Thread Orel Shai (JIRA)
Orel Shai created KAFKA-6553: Summary: Consumer consumed committed messages Key: KAFKA-6553 URL: https://issues.apache.org/jira/browse/KAFKA-6553 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-6552) “entity_type” not exactly in description of kafka-configs.sh

2018-02-12 Thread Guozhang Wang (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-6552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6552. -- Resolution: Fixed Assignee: Xin Fix Version/s: 1.2.0 > “entity_type” not

[VOTE] 1.0.1 RC1

2018-02-12 Thread Ewen Cheslack-Postava
Hello Kafka users, developers and client-developers, This is the second candidate for release of Apache Kafka 1.0.1. This is a bugfix release for the 1.0 branch that was first released with 1.0.0 about 3 months ago. We've fixed 49 significant issues since that release. Most of these are

Re: [VOTE] 1.0.1 RC1

2018-02-12 Thread Ewen Cheslack-Postava
And of course I'm +1 since I've already done normal release validation before posting this. -Ewen On Mon, Feb 12, 2018 at 10:15 AM, Ewen Cheslack-Postava wrote: > Hello Kafka users, developers and client-developers, > > This is the second candidate for release of Apache

Re: [DISCUSS] KIP-250 Add Support for Quorum-based Producer Acknowledgment

2018-02-12 Thread Guozhang Wang
Hello Tao, No I was not proposing to change the mechanism of acks=all, and only mentioning that today even with acks=all the tolerance of failures is theoretically still bounded by min.isr settings though we do require all replicas in ISR (which may be larger than min.isr) to replicate before

Build failed in Jenkins: kafka-trunk-jdk9 #388

2018-02-12 Thread Apache Jenkins Server
See Changes: [jason] KAFKA-5550; Connect Struct.put() should include the field name if [wangguoz] KAFKA-6552: Use “entity_type” in description of kafka-configs.sh (#4556)

Re: [DISCUSS] KIP-250 Add Support for Quorum-based Producer Acknowledgment

2018-02-12 Thread Litao Deng
Folks. Thanks for all of the good discussions. Here are a few of my thoughts: 1. we won't change any existing semantics. That means, besides acks '-1 (all)', '0', '1', we will introduce a separate 'quorum' and document the semantic. 'quorum' is a totally different view of our

[jira] [Created] (KAFKA-6555) Making state store queryable during restoration

2018-02-12 Thread Ashish Surana (JIRA)
Ashish Surana created KAFKA-6555: Summary: Making state store queryable during restoration Key: KAFKA-6555 URL: https://issues.apache.org/jira/browse/KAFKA-6555 Project: Kafka Issue Type:

Build failed in Jenkins: kafka-trunk-jdk7 #3177

2018-02-12 Thread Apache Jenkins Server
See Changes: [wangguoz] MINOR: Fixed typos in KGroupedTable Javadoc (#4552) [wangguoz] KAFKA-6472 - Fix WordCount example code error (#4538) [github] MINOR: Add a new system test for resilience (#4560)

Re: [DISCUSS] KIP-250 Add Support for Quorum-based Producer Acknowledgment

2018-02-12 Thread Litao Deng
Hey Guozhang. Not fully understand your following comments. The goal of my approach is to maintain the behavior of ack="all", which > happen to do better than what Kafka is actually guaranteed: when both A and > B are partitioned off, produced records will not be acked since "all" > requires all

Build failed in Jenkins: kafka-trunk-jdk7 #3176

2018-02-12 Thread Apache Jenkins Server
See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H22 (ubuntu xenial) in workspace

Build failed in Jenkins: kafka-trunk-jdk9 #390

2018-02-12 Thread Apache Jenkins Server
See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H22 (ubuntu xenial) in workspace

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

2018-02-12 Thread Apache Jenkins Server
See Changes: [wangguoz] KAFKA-6472 - Fix WordCount example code error (#4538) -- [...truncated 411.32 KB...] kafka.server.epoch.LeaderEpochFileCacheTest >

Build failed in Jenkins: kafka-trunk-jdk9 #391

2018-02-12 Thread Apache Jenkins Server
See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H22 (ubuntu xenial) in workspace

Jenkins build is back to normal : kafka-trunk-jdk9 #389

2018-02-12 Thread Apache Jenkins Server
See

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

2018-02-12 Thread Apache Jenkins Server
See

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

2018-02-12 Thread Apache Jenkins Server
See Changes: [jason] KAFKA-5944: Unit tests for handling SASL authentication failures in -- [...truncated 3.21 MB...] kafka.api.DelegationTokenEndToEndAuthorizationTest

Jenkins build is back to normal : kafka-trunk-jdk9 #392

2018-02-12 Thread Apache Jenkins Server
See