[jira] [Updated] (KAFKA-4071) Corruptted replication-offset-checkpoint leads to kafka server disfunctional

[ https://issues.apache.org/jira/browse/KAFKA-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zane Zhang updated KAFKA-4071: -- Description: For an unknown reason, [kafka data root]/replication-offset-checkpoint was corrupted.

[jira] [Updated] (KAFKA-4065) Property missing in ProcuderConfig.java - KafkaProducer API 0.9.0.0

[ https://issues.apache.org/jira/browse/KAFKA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] manzar updated KAFKA-4065: -- Description: 1 ) "compressed.topics" property is missing in ProducerConfig.java in KafkaProducer API 0.9.0.0.

[jira] [Commented] (KAFKA-4071) Corruptted replication-offset-checkpoint leads to kafka server disfunctional

[ https://issues.apache.org/jira/browse/KAFKA-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431056#comment-15431056 ] Alexey Ozeritskiy commented on KAFKA-4071: -- Thanks [~zanezhang]. Could you attach

[jira] [Commented] (KAFKA-4051) Strange behavior during rebalance when turning the OS clock back

[ https://issues.apache.org/jira/browse/KAFKA-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15430981#comment-15430981 ] Gabriel Ibarra commented on KAFKA-4051: --- Hi, I'm sorry for the delay. I agree with you guys, it is

Prevent broker from leading topic partitions

I have a use case that requires a 2 node deployment with a Kafka-backed service with the following constraints: - All data must be persisted to node 1. If node 1 fails (regardless of the status of node 2), then the system must stop. - If node 2 is up, then it must stay in synch with node 1. - If

Re: Prevent broker from leading topic partitions

Hi, I don't think I understand *why* you need this. Kafka is by default a distributed HA system that balances data and leadership over nodes. Why do you need to change this? You could accomplish something like this with mirror maker, that may make more sense. Thanks Tom Crayford Heroku Kafka

[jira] [Commented] (KAFKA-3163) KIP-33 - Add a time based log index to Kafka

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

[GitHub] kafka pull request #1769: Minor follow up for KAFKA-3163 (KIP-33)

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1769 Minor follow up for KAFKA-3163 (KIP-33) @junrao Could you take a look when get a chance? Thanks. You can merge this pull request into a Git repository by running: $ git pull

Re: [VOTE] KIP-74: Add FetchResponse size limit in bytes

Thanks. Request parameter renamed: response_max_bytes -> max_bytes. Andrey. > On 19 Aug 2016, at 16:52, Ismael Juma wrote: > > Thanks for the KIP. +1 (binding) with the following suggestion: > > Fetch Request (Version: 3) => replica_id max_wait_time min_bytes >

[GitHub] kafka pull request #1768: KAFKA-4051: Use nanosecond clock for timers in bro...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/1768 KAFKA-4051: Use nanosecond clock for timers in broker Use System.nanoseconds instead of System.currentTimeMillis in broker timer tasks to cope with changes to wall-clock time. You can merge

[jira] [Updated] (KAFKA-4019) LogCleaner should grow read/write buffer to max message size for the topic

[ https://issues.apache.org/jira/browse/KAFKA-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4019: -- Status: Patch Available (was: Open) > LogCleaner should grow read/write buffer to max message

[jira] [Updated] (KAFKA-4066) NullPointerException in Kafka consumer due to unsafe access to findCoordinatorFuture

[ https://issues.apache.org/jira/browse/KAFKA-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4066: -- Status: Patch Available (was: Open) > NullPointerException in Kafka consumer due to unsafe

[jira] [Updated] (KAFKA-4051) Strange behavior during rebalance when turning the OS clock back

[ https://issues.apache.org/jira/browse/KAFKA-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4051: -- Status: Patch Available (was: Open) Agree with [~onurkaraman] that this is an unusual

[jira] [Created] (KAFKA-4073) MirrorMaker should handle mirroring messages w/o timestamp better

Jun Rao created KAFKA-4073: -- Summary: MirrorMaker should handle mirroring messages w/o timestamp better Key: KAFKA-4073 URL: https://issues.apache.org/jira/browse/KAFKA-4073 Project: Kafka Issue

[jira] [Commented] (KAFKA-4073) MirrorMaker should handle mirroring messages w/o timestamp better

[ https://issues.apache.org/jira/browse/KAFKA-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431460#comment-15431460 ] Jun Rao commented on KAFKA-4073: One way to fix that is to check if the timestamp is present in the source

[jira] [Commented] (KAFKA-3937) Kafka Clients Leak Native Memory For Longer Than Needed With Compressed Messages

[ https://issues.apache.org/jira/browse/KAFKA-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431505#comment-15431505 ] William Yu commented on KAFKA-3937: --- [~ijuma] I've created a new PR based on your comments. Let me know

[jira] [Updated] (KAFKA-4073) MirrorMaker should handle mirroring messages w/o timestamp better

[ https://issues.apache.org/jira/browse/KAFKA-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4073: --- Fix Version/s: 0.10.0.2 0.10.1.0 > MirrorMaker should handle mirroring messages

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

See Changes: [junrao] KAFKA-3163; Minor follow up for (KIP-33) -- [...truncated 4991 lines...] kafka.api.PlaintextConsumerTest > testCoordinatorFailover STARTED kafka.api.PlaintextConsumerTest

[GitHub] kafka pull request #1651: MINOR: Fix typos in security section

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1651 --- 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 #1764: MINOR: improve Streams application reset tool to m...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1764 --- 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: [VOTE] KIP-73 - Replication Quotas

Ben, Thanks for the proposal. +1. Just a few minor comments below. 1. We have a LeaderOverThrottledRate metric to indicate the amount of throttling happening in the leader broker. It seems that we should have the equivalent of that for the follower to indicate the amount of throttling in the

[jira] [Commented] (KAFKA-2629) Enable getting SSL password from an executable rather than passing plaintext password

[ https://issues.apache.org/jira/browse/KAFKA-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431725#comment-15431725 ] Ashish K Singh commented on KAFKA-2629: --- [~bharatviswa] just posted a WIP patch. This adds a config

[jira] [Commented] (KAFKA-2894) WorkerSinkTask doesn't handle rewinding offsets on rebalance

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

Re: [DISCUSS] KIP-4 ACL Admin Schema

Grant, For your second comment, when propagating the ZK changes to acl cache, we will also update the latest ZK version. So, if ACL requests are not issued too quickly, the conditional updates to ZK should always be successful in one try. One potential benefit of serving the ACL request from any

[jira] [Resolved] (KAFKA-4049) Transient failure in RegexSourceIntegrationTest.testRegexMatchesTopicsAWhenDeleted

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

[jira] [Commented] (KAFKA-4049) Transient failure in RegexSourceIntegrationTest.testRegexMatchesTopicsAWhenDeleted

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

[GitHub] kafka pull request #1746: KAFKA-4049: Fix transient failure in RegexSourceIn...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1746 --- 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-4066) NullPointerException in Kafka consumer due to unsafe access to findCoordinatorFuture

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

[GitHub] kafka pull request #1770: WIP: KAFKA-2629: Enable getting passwords from an ...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/1770 WIP: KAFKA-2629: Enable getting passwords from an executable rathe… …r than passing plaintext password You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-2629) Enable getting SSL password from an executable rather than passing plaintext password

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

[jira] [Resolved] (KAFKA-4075) Failure in SaslSslTopicMetadataTest.testIsrAfterBrokerShutDownAndJoinsBack

[ https://issues.apache.org/jira/browse/KAFKA-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4075. Resolution: Duplicate Duplicate of KAFKA-3103 > Failure in

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

See

[GitHub] kafka pull request #1739: KAFKA-4032: Uncaught exceptions when autocreating ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1739 --- 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] [Commented] (KAFKA-4032) Uncaught exceptions when autocreating topics

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

[GitHub] kafka pull request #1772: MINOR: Update Kafka configuration documentation to...

GitHub user SinghAsDev opened a pull request: https://github.com/apache/kafka/pull/1772 MINOR: Update Kafka configuration documentation to use kafka-configs.… …sh, instead of deprecated kafka-topics.sh --alter You can merge this pull request into a Git repository by running:

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

See Changes: [junrao] KAFKA-3894; log cleaner can partially clean a segment -- [...truncated 5036 lines...] kafka.api.SslProducerSendTest > testSendWithInvalidCreateTime STARTED

[GitHub] kafka pull request #1731: MINOR: add slf4jlog4j to streams example

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1731 --- 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-4075) Failure in SaslSslTopicMetadataTest.testIsrAfterBrokerShutDownAndJoinsBack

Guozhang Wang created KAFKA-4075: Summary: Failure in SaslSslTopicMetadataTest.testIsrAfterBrokerShutDownAndJoinsBack Key: KAFKA-4075 URL: https://issues.apache.org/jira/browse/KAFKA-4075 Project:

[jira] [Updated] (KAFKA-4032) Uncaught exceptions when autocreating topics

[ https://issues.apache.org/jira/browse/KAFKA-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4032: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Uncaught exceptions when

[jira] [Updated] (KAFKA-4032) Uncaught exceptions when autocreating topics

[ https://issues.apache.org/jira/browse/KAFKA-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4032: --- Fix Version/s: 0.10.1.0 > Uncaught exceptions when autocreating topics >

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

See Changes: [ismael] KAFKA-4066; Fix NPE in consumer due to multi-threaded updates [ismael] MINOR: Fix typos in security section [wangguoz] MINOR: improve Streams application reset tool to make sure application [ismael] MINOR:

[jira] [Commented] (KAFKA-4051) Strange behavior during rebalance when turning the OS clock back

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

[GitHub] kafka pull request #1768: KAFKA-4051: Use nanosecond clock for timers in bro...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1768 --- 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-4051) Strange behavior during rebalance when turning the OS clock back

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

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

See Changes: [ismael] MINOR: Fix typos in security section [wangguoz] MINOR: improve Streams application reset tool to make sure application [ismael] MINOR: add slf4jlog4j to streams example [cshapi] KAFKA-4051: Use nanosecond

[GitHub] kafka pull request #1771: KAFKA-2894: WorkerSinkTask should rewind offsets o...

GitHub user kkonstantine opened a pull request: https://github.com/apache/kafka/pull/1771 KAFKA-2894: WorkerSinkTask should rewind offsets on rebalance You can merge this pull request into a Git repository by running: $ git pull https://github.com/kkonstantine/kafka

[jira] [Commented] (KAFKA-4073) MirrorMaker should handle mirroring messages w/o timestamp better

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

[jira] [Resolved] (KAFKA-4073) MirrorMaker should handle mirroring messages w/o timestamp better

[ https://issues.apache.org/jira/browse/KAFKA-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-4073. Resolution: Fixed Issue resolved by pull request 1773 [https://github.com/apache/kafka/pull/1773] >

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

See Changes: [ismael] KAFKA-3916; Check for disconnects properly before sending from the -- [...truncated 12105 lines...] org.apache.kafka.streams.state.internals.RocksDBKeyValueStoreTest >

[jira] [Assigned] (KAFKA-4073) MirrorMaker should handle mirroring messages w/o timestamp better

[ https://issues.apache.org/jira/browse/KAFKA-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4073: -- Assignee: Ismael Juma > MirrorMaker should handle mirroring messages w/o timestamp better >

[jira] [Resolved] (KAFKA-3916) Connection from controller to broker disconnects

[ https://issues.apache.org/jira/browse/KAFKA-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3916. Resolution: Fixed Fix Version/s: 0.10.1.0 Issue resolved by pull request 1734

[jira] [Commented] (KAFKA-3916) Connection from controller to broker disconnects

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

[jira] [Updated] (KAFKA-3916) Connection from controller to broker disconnects

[ https://issues.apache.org/jira/browse/KAFKA-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3916: --- Assignee: Jason Gustafson > Connection from controller to broker disconnects >

[GitHub] kafka pull request #1773: KAFKA-4073: MirrorMaker should handle messages wit...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1773 KAFKA-4073: MirrorMaker should handle messages without timestamp correctly You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka

[jira] [Commented] (KAFKA-4073) MirrorMaker should handle mirroring messages w/o timestamp better

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

Build failed in Jenkins: kafka-0.10.0-jdk7 #193

See Changes: [ismael] MINOR: add slf4jlog4j to streams example -- [...truncated 5750 lines...] org.apache.kafka.streams.kstream.internals.KTableImplTest > testKTable PASSED

[GitHub] kafka pull request #1736: MINOR: Refactor TopologyBuilder with ApplicationID...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1736 --- 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 #1773: KAFKA-4073: MirrorMaker should handle messages wit...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1773 --- 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] [Commented] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the offset map

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

[jira] [Commented] (KAFKA-3522) Consider adding version information into rocksDB storage format

[ https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431288#comment-15431288 ] Ishita Mandhan commented on KAFKA-3522: --- Just wanted to check in to see if now is a good time to

[jira] [Commented] (KAFKA-3163) KIP-33 - Add a time based log index to Kafka

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

[GitHub] kafka pull request #1769: Minor follow up for KAFKA-3163 (KIP-33)

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1769 --- 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 #1725: KAFKA-3894: log cleaner can partially clean a segm...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1725 --- 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] [Resolved] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the offset map

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-3894. Resolution: Fixed Issue resolved by pull request 1725 [https://github.com/apache/kafka/pull/1725] >

[jira] [Created] (KAFKA-4072) improving memory usage in LogCleaner

Jun Rao created KAFKA-4072: -- Summary: improving memory usage in LogCleaner Key: KAFKA-4072 URL: https://issues.apache.org/jira/browse/KAFKA-4072 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-3894) LogCleaner thread crashes if not even one segment can fit in the offset map

[ https://issues.apache.org/jira/browse/KAFKA-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3894: --- Assignee: Tom Crayford [~tcrayford-heroku], thanks for the patch. Filed a followup jira KAFKA-4072 to

Re: Prevent broker from leading topic partitions

Hi 22.08.2016, 19:16, "Tom Crayford" : > Hi, > > I don't think I understand *why* you need this. Kafka is by default a > distributed HA system that balances data and leadership over nodes. Why do > you need to change this? In fact, kafka does not balance anything. It uses

Re: [DISCUSS] KIP-71 Enable log compaction and deletion to co-exist

The update looks good to me. Thanks Damian. Guozhang On Fri, Aug 19, 2016 at 11:05 AM, Damian Guy wrote: > Thanks Jun. > > Everyone - i've updated the KIP to use a comma-separated list of > cleanup.policies as suggested. I know we have already voted on this > proposal, so

[GitHub] kafka pull request #1734: KAFKA-3916: Check for disconnects properly before ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1734 --- 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-4074) Deleting a topic can make it unavailable even if delete.topic.enable is false

Joel Koshy created KAFKA-4074: - Summary: Deleting a topic can make it unavailable even if delete.topic.enable is false Key: KAFKA-4074 URL: https://issues.apache.org/jira/browse/KAFKA-4074 Project: Kafka

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

See Changes: [junrao] KAFKA-3163; Minor follow up for (KIP-33) [junrao] KAFKA-3894; log cleaner can partially clean a segment -- [...truncated 1853 lines...]

[jira] [Commented] (KAFKA-4066) NullPointerException in Kafka consumer due to unsafe access to findCoordinatorFuture

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

[GitHub] kafka pull request #1763: KAFKA-4066: Fix NPE in consumer due to multi-threa...

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