[jira] [Created] (KAFKA-6151) kafka broker not starting ; WARN kafka.log.Log: Found a corrupted index file

Prince Paulson created KAFKA-6151: - Summary: kafka broker not starting ; WARN kafka.log.Log: Found a corrupted index file Key: KAFKA-6151 URL: https://issues.apache.org/jira/browse/KAFKA-6151

Re: Question about fromLogical method in connect/api/src/main/java/org/apache/kafka/connect/data/Date.java

CharSyam, As I understood, it seems like Date#fromLogical assumes that the given Data object is created under UTC timezone - its unit test, DateTest, creates all related GregorianCalendar objects with TimeZone.getTimeZone("UTC"). So if all the Date objects given as the parameter are UTC-oriented,

Mutation/upgrade of kafka message logs

Hi, I understand in most of cases, we should keep log immutable. However, when it goes to event sourcing (Ben Stopford and Neha Narkhede have a series of posts: Messaging as the Single Source of

MetricsReporter does not get auto-generated client.id

I have already created a Jira for this, but have not received any comments so bringing this to email. https://issues.apache.org/jira/browse/KAFKA-6123 Interceptors and MetricsReporters configured for a client will receive the user-specified configurations via the configure() method. When a

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

See Changes: [wangguoz] MINOR: Code cleanup and JavaDoc improvements for clients and Streams -- [...truncated 3.79 MB...]

Re: [DISCUSS] KIP-217: Expose a timeout to allow an expired ZK session to be re-created

Hi, Stephane, Thanks for the reply. 1) Fixing the issue in ZK will be ideal. Not sure when it will happen though. Once it's fixed, we can probably deprecate this config. 2) That could be useful. Is there a java api to do that at runtime? Also, invalidating DNS cache doesn't always fix the issue

Re: [DISCUSS] KIP-215: Add topic regex support for Connect sinks

I took a quick pass at the PR, looks good so far. ConfigException would still be fine in the case you're highlighting as it's inside the framework anyway and we'd expect a ConfigException from configure() if connectors try to use their ConfigDef to parse an invalid config. But here I don't feel

[jira] [Created] (KAFKA-6150) Make Repartition Topics Transient

Guozhang Wang created KAFKA-6150: Summary: Make Repartition Topics Transient Key: KAFKA-6150 URL: https://issues.apache.org/jira/browse/KAFKA-6150 Project: Kafka Issue Type: Improvement

Re: [VOTE] 1.0.0 RC4

+1. Hope this is the last one. On Fri, Oct 27, 2017 at 10:28 AM, Guozhang Wang wrote: > Hello Kafka users, developers and client-developers, > > This is the fifth candidate for release of Apache Kafka 1.0.0. The main PRs > that gets merged in after RC3 are the following: > >

[GitHub] kafka pull request #4072: MINOR: Add HttpMetricsReporter for system tests

Github user ewencp closed the pull request at: https://github.com/apache/kafka/pull/4072 ---

[GitHub] kafka pull request #4072: MINOR: Add HttpMetricsReporter for system tests

GitHub user ewencp reopened a pull request: https://github.com/apache/kafka/pull/4072 MINOR: Add HttpMetricsReporter for system tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka http-metrics Alternatively you

Re: Permission to create a KIP

Not sure if someone added you and just forgot to reply, but it looks like you already have permissions on the wiki. Just follow the process described here: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals -Ewen On Thu, Oct 26, 2017 at 8:40 AM, Elizabeth Bennett <

Question about fromLogical method in connect/api/src/main/java/org/apache/kafka/connect/data/Date.java

Hi here. I have a question about fromLogical method in connect/api/src/main/java/org/apache/kafka/connect/data/Date.java below code does these step. 1. calendar with UTC timezone 2. set value 3. check hour, minute, second, millisecond are 0. if not throw DataException. ``` public static int

Re: [DISCUSS] KIP-211: Revise Expiration Semantics of Consumer Group Offsets

I support this as the proposed change seems both more intuitive and safer. Right now we've essentially hacked this at my day job by bumping the offset retention period really high, but this is a much cleaner solution. I don't have any use-cases that require custom retention periods on a

[jira] [Created] (KAFKA-6149) LogCleanerManager should include topic partition name when warning of invalid cleaner offset

Ryan P created KAFKA-6149: - Summary: LogCleanerManager should include topic partition name when warning of invalid cleaner offset Key: KAFKA-6149 URL: https://issues.apache.org/jira/browse/KAFKA-6149

Re: [VOTE] KIP-214: Add zookeeper.max.in.flight.requests config to the broker

+1 (non-binding) Thanks for putting the work in to benchmark various defaults. On Mon, Oct 30, 2017 at 3:05 PM, Ismael Juma wrote: > Thanks for the KIP, +1 (binding). > > On 27 Oct 2017 6:15 pm, "Onur Karaman" > wrote: > > > I'd like to start

[GitHub] kafka pull request #4162: [KAFKA-4499] Add "getAllKeys" for querying windowe...

GitHub user ConcurrencyPractitioner opened a pull request: https://github.com/apache/kafka/pull/4162 [KAFKA-4499] Add "getAllKeys" for querying windowed KTable stores You can merge this pull request into a Git repository by running: $ git pull

Re: [VOTE] KIP-214: Add zookeeper.max.in.flight.requests config to the broker

Thanks for the KIP, +1 (binding). On 27 Oct 2017 6:15 pm, "Onur Karaman" wrote: > I'd like to start the vote for KIP-214: Add > zookeeper.max.in.flight.requests config to the broker > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- >

Re: [VOTE] KIP-214: Add zookeeper.max.in.flight.requests config to the broker

Hi, Onur, Thanks for the KIP. +1 from me. Jun On Sat, Oct 28, 2017 at 11:48 PM, Manikumar wrote: > +1 (non-binding) > > On Fri, Oct 27, 2017 at 10:46 PM, Ted Yu wrote: > > > +1 > > > > On Fri, Oct 27, 2017 at 10:15 AM, Onur Karaman < > >

[jira] [Created] (KAFKA-6148) ERROR Commit of WorkerSinkTask{id=bigquery-connector-log-0} offsets threw an unexpected exception: (org.apache.kafka.connect.runtime.WorkerSinkTask:205) java.lang.ClassC

Eugene Burd created KAFKA-6148: -- Summary: ERROR Commit of WorkerSinkTask{id=bigquery-connector-log-0} offsets threw an unexpected exception: (org.apache.kafka.connect.runtime.WorkerSinkTask:205) java.lang.ClassCastException:

Re: [VOTE] KIP-207:The Offsets which ListOffsetsResponse returns should monotonically increase even during a partition leader change

Hi all, With binding +1 votes from Jason Gustafson, Jun Rao, and Ismael Juma, non-binding +1 votes from Manikumar, and no +0 or -1 votes, the vote passes. best, Colin On Fri, Oct 27, 2017, at 11:09, Colin McCabe wrote: > Thanks, everyone. I'm going to close the vote tomorrow if there are no >

[jira] [Resolved] (KAFKA-6139) error when loading plugins

[ https://issues.apache.org/jira/browse/KAFKA-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Burd resolved KAFKA-6139. Resolution: Information Provided Error was due to having the plugin directory set a level too low

[jira] [Resolved] (KAFKA-4084) automated leader rebalance causes replication downtime for clusters with too many partitions

[ https://issues.apache.org/jira/browse/KAFKA-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-4084. Resolution: Fixed Fix Version/s: 1.1.0 The auto leader balancing logic now uses the async ZK api and

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

See Changes: [jason] KAFKA-6130; Ensure VerifiableConsumer halts when --max-messages is [jason] KAFKA-2903; FileRecords.read doesn't handle size > sizeInBytes when [jason] KAFKA-5212; Consumer ListOffsets

Re: [VOTE] KIP-205: Add all() and range() API to ReadOnlyWindowStore

+1 for the KIP and Rename On Sat, Oct 28, 2017 at 5:51 AM Bill Bejeck wrote: > +1 for the KIP and +1 on renaming "range" to "fetchAll" > > Thanks, > Bill > > On Thu, Oct 26, 2017 at 4:39 PM, Guozhang Wang wrote: > > > BTW, Xavier has an argument to rename

[GitHub] kafka pull request #4161: Adding lighthouse logos and nav bar

GitHub user manjuapu opened a pull request: https://github.com/apache/kafka/pull/4161 Adding lighthouse logos and nav bar @guozhangwang Please review You can merge this pull request into a Git repository by running: $ git pull https://github.com/confluentinc/kafka

[VOTE] KIP-208: Add SSL support to Kafka Connect REST interface

Hi, It seems there are no more comments for this KIP, so I would like to start the voting . For more details about the KIP-208 go to *https://cwiki.apache.org/confluence/display/KAFKA/KIP-208%3A+Add+SSL+support+to+Kafka+Connect+REST+interface

[GitHub] kafka pull request #4160: Customer logo stream

Github user manjuapu closed the pull request at: https://github.com/apache/kafka/pull/4160 ---

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

See Changes: [wangguoz] MINOR: Code cleanup and JavaDoc improvements for clients and Streams -- Started by an SCM change [EnvInject] - Loading node environment variables.

[GitHub] kafka pull request #4128: MINOR: random cleanup and JavaDoc improvements for...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4128 ---

[GitHub] kafka pull request #4160: Customer logo stream

GitHub user manjuapu opened a pull request: https://github.com/apache/kafka/pull/4160 Customer logo stream @guozhangwang Please review You can merge this pull request into a Git repository by running: $ git pull https://github.com/confluentinc/kafka customer-logo-stream

[jira] [Created] (KAFKA-6147) Error reading field 'api_versions': Error reading field 'max_version': java.nio.BufferUnderflowException

Sandro Simas created KAFKA-6147: --- Summary: Error reading field 'api_versions': Error reading field 'max_version': java.nio.BufferUnderflowException Key: KAFKA-6147 URL:

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

See

[GitHub] kafka-site issue #105: Adding Trivago logo to streams page

Github user guozhangwang commented on the issue: https://github.com/apache/kafka-site/pull/105 LGTM. Merged to asf-site. ---

[GitHub] kafka-site pull request #105: Adding Trivago logo to streams page

Github user asfgit closed the pull request at: https://github.com/apache/kafka-site/pull/105 ---

[GitHub] kafka-site issue #105: Adding Trivago logo to streams page

Github user manjuapu commented on the issue: https://github.com/apache/kafka-site/pull/105 @guozhangwang Good catch removed it "s" ---

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

See

[GitHub] kafka-site pull request #105: Adding Trivago logo to streams page

Github user miguno commented on a diff in the pull request: https://github.com/apache/kafka-site/pull/105#discussion_r147804493 --- Diff: 0110/streams/index.html --- @@ -17,20 +17,20 @@

[GitHub] kafka-site pull request #105: Adding Trivago logo to streams page

Github user guozhangwang commented on a diff in the pull request: https://github.com/apache/kafka-site/pull/105#discussion_r147801292 --- Diff: 0110/streams/index.html --- @@ -17,20 +17,20 @@

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

See Changes: [jason] KAFKA-2903; FileRecords.read doesn't handle size > sizeInBytes when [jason] KAFKA-5212; Consumer ListOffsets request can starve group heartbeats --

[GitHub] kafka pull request #4110: [KAFKA-5212] Consumer ListOffsets request can star...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4110 ---

[jira] [Resolved] (KAFKA-5212) Consumer ListOffsets request can starve group heartbeats

[ https://issues.apache.org/jira/browse/KAFKA-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5212. Resolution: Fixed Fix Version/s: (was: 1.0.1) Issue resolved by pull request

[GitHub] kafka-site pull request #105: Adding Trivago logo to streams page

GitHub user manjuapu opened a pull request: https://github.com/apache/kafka-site/pull/105 Adding Trivago logo to streams page @guozhangwang Please review You can merge this pull request into a Git repository by running: $ git pull https://github.com/manjuapu/kafka-site

[GitHub] kafka pull request #4158: KAFKA-2903: FileRecords.read doesn't handle size >...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4158 ---

[jira] [Created] (KAFKA-6146) re-register the exist watch on PreferredReplicaElectionZNode after the preferred leader election completes

Jun Rao created KAFKA-6146: -- Summary: re-register the exist watch on PreferredReplicaElectionZNode after the preferred leader election completes Key: KAFKA-6146 URL: https://issues.apache.org/jira/browse/KAFKA-6146

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

See Changes: [junrao] KAFKA-6073; Use ZookeeperClient in KafkaApis -- [...truncated 383.29 KB...] kafka.log.ProducerStateManagerTest > testRecoverFromSnapshot PASSED

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

See Changes: [junrao] KAFKA-6073; Use ZookeeperClient in KafkaApis [jason] KAFKA-6130; Ensure VerifiableConsumer halts when --max-messages is -- Started by an SCM change

[jira] [Created] (KAFKA-6145) Warm up new KS instances before migrating tasks - potentially a two phase rebalance

Antony Stubbs created KAFKA-6145: Summary: Warm up new KS instances before migrating tasks - potentially a two phase rebalance Key: KAFKA-6145 URL: https://issues.apache.org/jira/browse/KAFKA-6145

[jira] [Created] (KAFKA-6144) Allow state stores to serve stale reads during rebalance

Antony Stubbs created KAFKA-6144: Summary: Allow state stores to serve stale reads during rebalance Key: KAFKA-6144 URL: https://issues.apache.org/jira/browse/KAFKA-6144 Project: Kafka Issue

Re: [VOTE] KIP-175: Additional '--describe' views for ConsumerGroupCommand

Bumping this again! From: "Vahid S Hashemian" To: dev@kafka.apache.org Date: 09/28/2017 12:13 PM Subject:Re: [VOTE] KIP-175: Additional '--describe' views for ConsumerGroupCommand I'm bumping this up as it's awaiting one more binding +1, but I'd

Re: [DISCUSS] KIP-211: Revise Expiration Semantics of Consumer Group Offsets

Bump! From: Vahid S Hashemian/Silicon Valley/IBM To: dev Date: 10/18/2017 04:45 PM Subject:[DISCUSS] KIP-211: Revise Expiration Semantics of Consumer Group Offsets Hi all, I created a KIP to address the group offset expiration issue reported in

[jira] [Resolved] (KAFKA-6130) VerifiableConsumer with --max-messages doesn't exit

[ https://issues.apache.org/jira/browse/KAFKA-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6130. Resolution: Fixed Fix Version/s: 1.1.0 > VerifiableConsumer with --max-messages

[GitHub] kafka pull request #4157: KAFKA-6130: VerifiableConsumer with --max-messages

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4157 ---

[GitHub] kafka pull request #4111: KAFKA-6073: Use ZookeeperClient in KafkaApis

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/4111 ---

[jira] [Created] (KAFKA-6143) VerifiableProducer & VerifiableConsumer need tests

Tom Bentley created KAFKA-6143: -- Summary: VerifiableProducer & VerifiableConsumer need tests Key: KAFKA-6143 URL: https://issues.apache.org/jira/browse/KAFKA-6143 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-6142) Connect worker configurations and connector configurations should accept environment variables

Randall Hauch created KAFKA-6142: Summary: Connect worker configurations and connector configurations should accept environment variables Key: KAFKA-6142 URL: https://issues.apache.org/jira/browse/KAFKA-6142

[GitHub] kafka pull request #3831: KAFKA-5520: KIP-171 - Extend Consumer Group Reset ...

Github user jeqo closed the pull request at: https://github.com/apache/kafka/pull/3831 ---

[GitHub] kafka pull request #4159: KAFKA-5520: KIP-171 - Extend Consumer Group Reset ...

GitHub user jeqo opened a pull request: https://github.com/apache/kafka/pull/4159 KAFKA-5520: KIP-171 - Extend Consumer Group Reset Offset for Stream Application - Merge with KIP-198 KIP:

[jira] [Resolved] (KAFKA-2995) in 0.9.0.0 Old Consumer's commitOffsets with specify partition can submit not exists topic and partition to zk

[ https://issues.apache.org/jira/browse/KAFKA-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2995. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-2062) Sync Producer, Variable Message Length, Multiple Threads = Direct memory overuse

[ https://issues.apache.org/jira/browse/KAFKA-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2062. -- Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-1958) ZookeeperConsumerConnector doesn't remove consumer node on shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1958. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-1415) Async producer.send can block forever if async.ProducerSendThread dies

[ https://issues.apache.org/jira/browse/KAFKA-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1415. -- Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-1066) Reduce logging on producer connection failures

[ https://issues.apache.org/jira/browse/KAFKA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1066. -- Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported > Reduce

[jira] [Resolved] (KAFKA-1006) Consumer loses messages of a new topic with auto.offset.reset = largest

[ https://issues.apache.org/jira/browse/KAFKA-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1006. -- Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported, please upgrade

[jira] [Resolved] (KAFKA-610) connect.timeout.ms seems to do the wrong thing in the producer

[ https://issues.apache.org/jira/browse/KAFKA-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-610. - Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported. >

[jira] [Resolved] (KAFKA-599) SimpleConsumerShell ONLY connects to the first host in the broker-list string to fetch topic metadata

[ https://issues.apache.org/jira/browse/KAFKA-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-599. - Resolution: Auto Closed The Scala consumers are no longer supported. > SimpleConsumerShell ONLY

[jira] [Resolved] (KAFKA-435) Keep track of the transient test failure for Kafka-343 on Apache Jenkins

[ https://issues.apache.org/jira/browse/KAFKA-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-435. - Resolution: Cannot Reproduce Closing inactive issue. > Keep track of the transient test failure for

[jira] [Resolved] (KAFKA-354) Refactor getter and setter API to conform to the new convention

[ https://issues.apache.org/jira/browse/KAFKA-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-354. - Resolution: Won't Fix Closing inactive issue. > Refactor getter and setter API to conform to the new

[jira] [Resolved] (KAFKA-407) Uncaught InputStream.close() exception in CompressionUtils.compress()

[ https://issues.apache.org/jira/browse/KAFKA-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-407. - Resolution: Won't Fix This part of the code is removed. So closing the issue. > Uncaught

[jira] [Reopened] (KAFKA-3917) Some __consumer_offsets replicas grow way too big

[ https://issues.apache.org/jira/browse/KAFKA-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-3917: If you're running 0.10.2.0, then potentially KAFKA-5413, but I'll reopen until we can verify. > Some

[jira] [Resolved] (KAFKA-2616) Improve Kakfa client exceptions

[ https://issues.apache.org/jira/browse/KAFKA-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2616. Resolution: Auto Closed BlockingChannel is only used by the Scala clients. which are no longer

[jira] [Resolved] (KAFKA-2636) Producer connectivity obscured connection failure logging

[ https://issues.apache.org/jira/browse/KAFKA-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2636. Resolution: Not A Problem The producer should throw a TimeoutException to the callback or if

[jira] [Resolved] (KAFKA-2662) Make ConsumerIterator thread-safe for multiple threads in different Kafka groups

[ https://issues.apache.org/jira/browse/KAFKA-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2662. Resolution: Auto Closed The Scala consumers are no longer supported. Please upgrade to the Java

[jira] [Resolved] (KAFKA-2725) high level consumer rebalances with auto-commit disabled should throw an exception

[ https://issues.apache.org/jira/browse/KAFKA-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2725. Resolution: Auto Closed The Scala consumers are no longer supported. If this still applies to the

Re: Experimenting with Kafka and OpenSSL

I haven't yet had a chance to try out Java 9, but that's definitely on my TODO list, maybe sometime this weekend. Thanks for pointing me to KAFKA-2561. I had missed that. -Jaikiran On 30/10/17 4:17 PM, Mickael Maison wrote: Thanks for sharing, very interesting read. Did you get a chance to

[GitHub] kafka pull request #4158: KAFKA-2903: FileRecords.read doesn't handle size >...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/4158 KAFKA-2903: FileRecords.read doesn't handle size > sizeInBytes when start is not zero You can merge this pull request into a Git repository by running: $ git pull

[jira] [Resolved] (KAFKA-3071) Kafka Server 0.8.2 ERROR OOME with siz

[ https://issues.apache.org/jira/browse/KAFKA-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3071. Resolution: Auto Closed The SimpleConsumer is no longer supported and will be removed in a future

[GitHub] kafka pull request #4157: KAFKA-6130: VerifiableConsumer with --max-messages

GitHub user tombentley opened a pull request: https://github.com/apache/kafka/pull/4157 KAFKA-6130: VerifiableConsumer with --max-messages @hachikuji can you review this? Do you know the best place to write a test, since there doesn't seem to be a unit test for the

Re: Experimenting with Kafka and OpenSSL

Thanks for sharing, very interesting read. Did you get a chance to try JDK 9 ? We also considered using OpenSSL instead of JSSE especially since Netty made an easy to re-use package (netty-tcnative). There was KAFKA-2561 (https://issues.apache.org/jira/browse/KAFKA-2561) where people shared a

[jira] [Resolved] (KAFKA-788) Periodic refresh of topic metadata on the producer doesn't include all topics

[ https://issues.apache.org/jira/browse/KAFKA-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-788. - Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported. > Periodic

[GitHub] kafka pull request #4156: Merge pull request #2 from apache/trunk

GitHub user hejiefang opened a pull request: https://github.com/apache/kafka/pull/4156 Merge pull request #2 from apache/trunk pull You can merge this pull request into a Git repository by running: $ git pull https://github.com/hejiefang/kafka trunk Alternatively you can

Experimenting with Kafka and OpenSSL

We have been using Kafka in some of our projects for the past couple of years. Our experience with Kafka and SSL had shown some performance issues when we had seriously tested it (which admittedly was around a year back). Our basic tests did show that things had improved over time with newer

Re: Use self contained tokens instead of ACL

Hi, In the first phase, we are trying implement the components/design discussed in the KIP. Yes, we can definitely improve some of the components to be more extensible. We are planning to implement in future KIPs/PRs. Thanks On Fri, Oct 27, 2017 at 8:22 PM, Sönke Liebau <