Re: Apache Kafka Docker official image

For official Apache Kafka Docker image I'd expect that it's published by Apache Kafka project from Dockerfile and related resources all living in Kafka's sources, and as any official Kafka source/resource those would be subject to Apache Kafka project community processes and practices. On Thu,

Request to add to contributor list

Hi dev team, I want to be added as a contributor in Kafka JIRA. My JIRA ID is takebayashi Thanks, Shun

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

Hi Jun, yes, we can just customize rules to send full principal name. I was just thinking to use PrinciplaBuilder interface for implementing SASL rules also. So that the interface will be consistent across protocols. Thanks On Fri, Feb 17, 2017 at 1:07 AM, Jun Rao wrote: >

[GitHub] kafka pull request #2562: MINOR: Update docstring for "offsets.retention.min...

GitHub user omkreddy opened a pull request: https://github.com/apache/kafka/pull/2562 MINOR: Update docstring for "offsets.retention.minutes" config You can merge this pull request into a Git repository by running: $ git pull https://github.com/omkreddy/kafka MINOR-DOC

Re: [DISCUSS] KIP-82 - Add Record Headers

Sorry, should have noted that the performance testing was done using the producer performance tool shipped with Kafka. -Jason On Thu, Feb 16, 2017 at 6:44 PM, Jason Gustafson wrote: > Hey Nacho, > > I've compared performance of our KIP-98 implementation with and without >

Re: [DISCUSS] KIP-82 - Add Record Headers

Hey Nacho, I've compared performance of our KIP-98 implementation with and without varints. For messages around 128 bytes, we see an increase in throughput of about 30% using the default configuration settings. At 256 bytes, the increase is around 16%. Obviously the performance converge as

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

See Changes: [jason] MINOR: Move compression stream construction into CompressionType [wangguoz] KAFKA-4484: Set more conservative default values on RocksDB for memory -- [...truncated 4110

[GitHub] kafka pull request #2561: MINOR: Fix possible NPE in NodeApiVersions.toStrin...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/2561 MINOR: Fix possible NPE in NodeApiVersions.toString You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

Re: [DISCUSS] KIP-82 - Add Record Headers

-VarInts I'm one of the people (if not the most) opposed to VarInts. VarInts have a place, but this is not it. (We had a large discussion about them at the beginning of KIP-82 time) If anybody has real life performance numbers of VarInts improving things or significantly reducing resources I

Re: Should InvalidTopicException be called IllegalTopicException

Wow, I managed to send two incomplete messages thanks to the new mac touchbar :) I was suggesting either renaming to IllegalTopicException or have a one that clearly mentions the name InvalidTopicNameException. However I guess the first option would be the easiest. Thanks, Cosmin

Should InvalidTopicException be called IllegalTopicException

It's a bit confusing when trying to understand what's the difference between UnknownTopicOrPartitionException (retriable) and InvalidTopicException (non-retriable). Looking through the code to figure out what's an invalid topic I see most tests that throw it describe it as "illegal". This is

Re: [VOTE] KIP-98: Exactly Once Delivery and Transactional Messaging

Hi Jun, Thanks for the reply. Comments inline. On Thu, Feb 16, 2017 at 2:29 PM, Jun Rao wrote: > Hi, Apurva, > > Thanks for the reply. A couple of comment below. > > On Wed, Feb 15, 2017 at 9:45 PM, Apurva Mehta wrote: > > > Hi Jun, > > > > Answers

[jira] [Commented] (KAFKA-4494) Significant startup delays in KStreams app

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

[GitHub] kafka pull request #2560: KAFKA-4494: Reduce startup and rebalance time

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2560 KAFKA-4494: Reduce startup and rebalance time Replace one-by-one initialization of state stores with bulk initialization. You can merge this pull request into a Git repository by running: $ git

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

See Changes: [wangguoz] KAFKA-4709：Error message from Struct.validate() should include the name -- [...truncated 8412 lines...] kafka.utils.timer.TimerTest > testTaskExpiration STARTED

[jira] [Commented] (KAFKA-4484) Set more conservative default values on RocksDB for memory usage

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

[jira] [Updated] (KAFKA-4484) Set more conservative default values on RocksDB for memory usage

[ https://issues.apache.org/jira/browse/KAFKA-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4484: - Resolution: Fixed Fix Version/s: 0.10.3.0 Status: Resolved (was: Patch

[GitHub] kafka pull request #2525: KAFKA-4484: Set more conservative default values o...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2525 --- 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

[GitHub] kafka pull request #2536: MINOR: Move compression stream construction into C...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2536 --- 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

Re: [DISCUSS] KIP-123: Allow per stream/table timestamp extractor

Hi Matthias, Done. On Thu, Feb 16, 2017 at 7:24 PM Matthias J. Sax wrote: > Jeyhun, > > can you please add the KIP to this table: > > https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals#KafkaImprovementProposals-KIPsunderdiscussion > > and to

[jira] [Created] (KAFKA-4776) Implement graceful handling for improperly formed compressed message sets

Jason Gustafson created KAFKA-4776: -- Summary: Implement graceful handling for improperly formed compressed message sets Key: KAFKA-4776 URL: https://issues.apache.org/jira/browse/KAFKA-4776 Project:

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

On Thu, Feb 16, 2017, at 14:11, Dong Lin wrote: > Hey Colin, > > Thanks for the update. I have two comments: > > - I actually think it is simpler and good enough to have per-topic API > instead of batch-of-topic API. This is different from the argument for > batch-of-partition API because,

[jira] [Commented] (KAFKA-4686) Null Message payload is shutting down broker

[ https://issues.apache.org/jira/browse/KAFKA-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870806#comment-15870806 ] Jason Gustafson commented on KAFKA-4686: I'm at a loss how this can happen. I tried to create a

Re: [VOTE] KIP-98: Exactly Once Delivery and Transactional Messaging

Hi, Apurva, Thanks for the reply. A couple of comment below. On Wed, Feb 15, 2017 at 9:45 PM, Apurva Mehta wrote: > Hi Jun, > > Answers inline: > > 210. Pid snapshots: Is the number of pid snapshot configurable or hardcoded > > with 2? When do we decide to roll a new

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

Hey Colin, Thanks for the update. I have two comments: - I actually think it is simpler and good enough to have per-topic API instead of batch-of-topic API. This is different from the argument for batch-of-partition API because, unlike operation on topic, people usually operate on multiple

[jira] [Commented] (KAFKA-4775) Fix findbugs warnings in kafka-tools

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

[GitHub] kafka pull request #2559: KAFKA-4775. Fix findbugs warnings in kafka-tools

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2559 KAFKA-4775. Fix findbugs warnings in kafka-tools You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-4775 Alternatively you

[jira] [Commented] (KAFKA-4709) Error message from Struct.validate() should include the name of the offending field.

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

[GitHub] kafka pull request #2521: KAFKA-4709：Error message from Struct.validate() ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2521 --- 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] [Created] (KAFKA-4775) Fix findbugs warnings in kafka-tools

Colin P. McCabe created KAFKA-4775: -- Summary: Fix findbugs warnings in kafka-tools Key: KAFKA-4775 URL: https://issues.apache.org/jira/browse/KAFKA-4775 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-4709) Error message from Struct.validate() should include the name of the offending field.

[ https://issues.apache.org/jira/browse/KAFKA-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4709. -- Resolution: Fixed Fix Version/s: 0.10.3.0 Issue resolved by pull request 2521

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

See Changes: [ismael] KAFKA-4765; Fixed Intentionally Broken Hosts Resolving to 127.0.53.53 in -- [...truncated 17523 lines...] org.apache.kafka.streams.KafkaStreamsTest >

[jira] [Commented] (KAFKA-4774) Inner classes which don't need a reference to the outer class should be static

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

[GitHub] kafka pull request #2558: KAFKA-4774. Inner classes which don't need a refer...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2558 KAFKA-4774. Inner classes which don't need a reference to the outer c… …lass should be static You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (KAFKA-4774) Inner classes which don't need a reference to the outer class should be static

Colin P. McCabe created KAFKA-4774: -- Summary: Inner classes which don't need a reference to the outer class should be static Key: KAFKA-4774 URL: https://issues.apache.org/jira/browse/KAFKA-4774

Re: Apache Kafka Docker official image

I'm not sure what "official image" means here... An image that gets tested by the Apache Kafka system tests? An image that the PMC votes on as part of the release process? Wouldn't the Apache official image need to be hosted on the Apache repository? I'd love to know more on how other Apache

[jira] [Work started] (KAFKA-4773) The Kafka build should run findbugs

[ https://issues.apache.org/jira/browse/KAFKA-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4773 started by Colin P. McCabe. -- > The Kafka build should run findbugs > ---

[jira] [Commented] (KAFKA-4773) The Kafka build should run findbugs

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

[GitHub] kafka pull request #2557: KAFKA-4773: The Kafka build should run findbugs

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2557 KAFKA-4773: The Kafka build should run findbugs You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-4773 Alternatively you can

[jira] [Created] (KAFKA-4773) The Kafka build should run findbugs

Colin P. McCabe created KAFKA-4773: -- Summary: The Kafka build should run findbugs Key: KAFKA-4773 URL: https://issues.apache.org/jira/browse/KAFKA-4773 Project: Kafka Issue Type:

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

Hi, Radai, Mayuresh, Thanks for the explanation. Good point on a pluggable authorizer can customize how acls are added. However, earlier, Mayuresh was saying that in LinkedIn's customized authorizer, it's not possible to create a principal from string. If that's the case, will adding the

[jira] [Commented] (KAFKA-4686) Null Message payload is shutting down broker

[ https://issues.apache.org/jira/browse/KAFKA-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870485#comment-15870485 ] Hannu Valtonen commented on KAFKA-4686: --- Log compaction was not used in our case. Our solution was

[jira] [Comment Edited] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870121#comment-15870121 ] Buğra Gedik edited comment on KAFKA-4767 at 2/16/17 6:31 PM: - I understand

Re: [DISCUSS] KIP-82 - Add Record Headers

+1 for varints here-- it would save quite a bit of space. They are pretty quick to implement as well. I think it makes sense for values to be byte arrays. Users might want to attach arbitrary payloads; they shouldn't be forced to serialize everything to Java strings. best, Colin On Thu, Feb

[jira] [Commented] (KAFKA-4686) Null Message payload is shutting down broker

[ https://issues.apache.org/jira/browse/KAFKA-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870458#comment-15870458 ] Jason Gustafson commented on KAFKA-4686: [~Ormod] Thanks. Do you recall if the topic experiencing

Re: [VOTE] 0.10.2.0 RC2

+1 (non-binding) Built from the source and ran the quickstart successfully on Ubuntu, Mac, Windows (64 bit). Thank you Ewen for running the release. --Vahid From: Ewen Cheslack-Postava To: dev@kafka.apache.org, "us...@kafka.apache.org" ,

Re: [DISCUSS] KIP-123: Allow per stream/table timestamp extractor

Jeyhun, can you please add the KIP to this table: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals#KafkaImprovementProposals-KIPsunderdiscussion and to this list: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Streams Thanks! -Matthias On 2/14/17 5:36

[jira] [Commented] (KAFKA-4686) Null Message payload is shutting down broker

[ https://issues.apache.org/jira/browse/KAFKA-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870447#comment-15870447 ] Hannu Valtonen commented on KAFKA-4686: --- We've periodically seen the same on Kafka 0.10.1.1 with the

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

Hi all, So I think people have made some very good points so far. There seems to be agreement that we need to have explicit batch APIs for the sake of efficiency, so I added that back. Contexts seem a little more complex than we thought, so I removed that from the proposal. I removed the Impl

Re: [VOTE] 0.10.2.0 RC2

+1 Verified signatures, tests and docs On Thu, Feb 16, 2017 at 9:44 AM, Neha Narkhede wrote: > +1 (binding) > > Verified signatures, quickstart, docs. > > Thanks for running the release, Ewen! > > On Thu, Feb 16, 2017 at 9:42 AM Gwen Shapira wrote: > > >

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

On Mon, Feb 13, 2017, at 23:04, radai wrote: > 1. making the client Closeable/AutoCloseable would allow try (Client = > ...) > {} without the need to finally close. Good idea... let's make the interface extend AutoCloseable. > > 2. a "stream processing unit" (producer + consumer) currently

Re: [DISCUSS] KIP-82 - Add Record Headers

Hey Michael, Hmm, I guess the point of representing it as bytes is to allow the broker to pass it through opaquely? Is the cost of parsing them a concern, or are we simply trying to ensure that the broker stays agnostic to the format? On varints, I think adding support for them makes less sense

Re: [VOTE] 0.10.2.0 RC2

+1 (binding) Verified signatures, quickstart, docs. Thanks for running the release, Ewen! On Thu, Feb 16, 2017 at 9:42 AM Gwen Shapira wrote: > +1 (binding). > > Verified signatures, ran unit tests, ran quickstart. > > Nice release :) > > On Tue, Feb 14, 2017 at 10:39 AM,

Re: [VOTE] 0.10.2.0 RC2

+1 (binding). Verified signatures, ran unit tests, ran quickstart. Nice release :) On Tue, Feb 14, 2017 at 10:39 AM, Ewen Cheslack-Postava wrote: > Hello Kafka users, developers and client-developers, > > This is the third candidate for release of Apache Kafka 0.10.2.0. > >

[jira] [Created] (KAFKA-4772) Exploit #peek to implement #print() and other methods

Matthias J. Sax created KAFKA-4772: -- Summary: Exploit #peek to implement #print() and other methods Key: KAFKA-4772 URL: https://issues.apache.org/jira/browse/KAFKA-4772 Project: Kafka

[jira] [Assigned] (KAFKA-4159) Allow overriding producer & consumer properties at the connector level

[ https://issues.apache.org/jira/browse/KAFKA-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Durfey reassigned KAFKA-4159: - Assignee: Stephen Durfey > Allow overriding producer & consumer properties at the

[jira] [Updated] (KAFKA-4159) Allow overriding producer & consumer properties at the connector level

[ https://issues.apache.org/jira/browse/KAFKA-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Durfey updated KAFKA-4159: -- Status: Patch Available (was: Open) > Allow overriding producer & consumer properties at the

[jira] [Commented] (KAFKA-4771) NPEs in KerberosLogin due to autoboxing

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

[GitHub] kafka pull request #2556: KAFKA-4771 - NPEs in KerberosLogin due to autoboxi...

GitHub user coheigea opened a pull request: https://github.com/apache/kafka/pull/2556 KAFKA-4771 - NPEs in KerberosLogin due to autoboxing You can merge this pull request into a Git repository by running: $ git pull https://github.com/coheigea/kafka kafka-4771 Alternatively

Apache Kafka Docker official image

Hi, I’m currently proposing an official image for Apache Kafka in the Docker library ( https://github.com/docker-library/official-images/pull/2627 ). I wanted to know if someone from Kafka upstream is interested in taking over or

[jira] [Created] (KAFKA-4771) NPEs in KerberosLogin due to autoboxing

Colm O hEigeartaigh created KAFKA-4771: -- Summary: NPEs in KerberosLogin due to autoboxing Key: KAFKA-4771 URL: https://issues.apache.org/jira/browse/KAFKA-4771 Project: Kafka Issue

[jira] [Comment Edited] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870121#comment-15870121 ] Buğra Gedik edited comment on KAFKA-4767 at 2/16/17 3:16 PM: - I understand

[jira] [Comment Edited] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870121#comment-15870121 ] Buğra Gedik edited comment on KAFKA-4767 at 2/16/17 3:15 PM: - I understand

[jira] [Commented] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870121#comment-15870121 ] Buğra Gedik commented on KAFKA-4767: I understand that it will eventually gets shutdown. But that does

[jira] [Commented] (KAFKA-4765) org.apache.kafka.clients.producer.KafkaProducerTest#testConstructorFailureCloseResource and Similar Tests are Failing on some Systems (127.0.53.53 Collision Warning)

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

Re: [DISCUSS] KIP-82 - Add Record Headers

Hi Jason, On point 1) in the message protocol the headers are simply a byte array, as like the key or value, this is to clearly demarcate the header in the core message. Then the header byte array in the core message is an array of key, value pairs. This is what it is denoting. Then this

[jira] [Commented] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870055#comment-15870055 ] huxi commented on KAFKA-4767: - What do you mean by "leaking the IO thread"? Do you mean it could not be shut

[GitHub] kafka pull request #2552: KAFKA-4765: Fixed Intentionally Broken Hosts Resol...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2552 --- 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-4765) org.apache.kafka.clients.producer.KafkaProducerTest#testConstructorFailureCloseResource and Similar Tests are Failing on some Systems (127.0.53.53 Collision Warning)

[ https://issues.apache.org/jira/browse/KAFKA-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4765: --- Resolution: Fixed Fix Version/s: 0.10.3.0 Status: Resolved (was: Patch Available)

Re: [kafka-clients] [VOTE] 0.10.2.0 RC2

+1 (non-binding) I didn't explicitly state my voting status in my previous comment, sorry. On Thu, Feb 16, 2017 at 1:59 PM, Rajini Sivaram wrote: > +1 (non-binding) > > Ran quick start and some security tests on binary, checked source build and > tests. > > Thank you,

Re: [kafka-clients] [VOTE] 0.10.2.0 RC2

+1 (non-binding) Ran quick start and some security tests on binary, checked source build and tests. Thank you, Rajini On Thu, Feb 16, 2017 at 2:04 AM, Jun Rao wrote: > Hi, Ewen, > > Thanks for running the release. +1. Verified quickstart on 2.10 binary. > > Jun > > On Tue,

[jira] [Comment Edited] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869912#comment-15869912 ] Buğra Gedik edited comment on KAFKA-4767 at 2/16/17 1:25 PM: - I think we are

[jira] [Comment Edited] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869912#comment-15869912 ] Buğra Gedik edited comment on KAFKA-4767 at 2/16/17 1:25 PM: - I think we are

[jira] [Commented] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869912#comment-15869912 ] Buğra Gedik commented on KAFKA-4767: I think we are getting close to understanding each other. Here is

[GitHub] kafka pull request #2555: Javadoc typo

GitHub user astubbs opened a pull request: https://github.com/apache/kafka/pull/2555 Javadoc typo You can merge this pull request into a Git repository by running: $ git pull https://github.com/astubbs/kafka patch-1 Alternatively you can review and apply these changes as the

[jira] [Created] (KAFKA-4770) KStreamAggregationDedupIntegrationTest fails occasionally

Eno Thereska created KAFKA-4770: --- Summary: KStreamAggregationDedupIntegrationTest fails occasionally Key: KAFKA-4770 URL: https://issues.apache.org/jira/browse/KAFKA-4770 Project: Kafka Issue

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869703#comment-15869703 ] Vladimír Kleštinec commented on KAFKA-2729: --- [~elevy] Agree, we are experiencing same issue,

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

See