date:20180220

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

2018-02-20 Thread Apache Jenkins Server

See 


Changes:

[rajinisivaram] KAFKA-6554; Missing lastOffsetDelta validation before log 
append (#4585)

--
[...truncated 413.72 KB...]

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldNotClearAnythingIfOffsetToFirstOffset STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldNotClearAnythingIfOffsetToFirstOffset PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldNotLetOffsetsGoBackwardsEvenIfEpochsProgress STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldNotLetOffsetsGoBackwardsEvenIfEpochsProgress PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldGetFirstOffsetOfSubsequentEpochWhenOffsetRequestedForPreviousEpoch STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldGetFirstOffsetOfSubsequentEpochWhenOffsetRequestedForPreviousEpoch PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldUpdateOffsetBetweenEpochBoundariesOnClearEarliest2 STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldUpdateOffsetBetweenEpochBoundariesOnClearEarliest2 PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldClearEarliestOnEmptyCache 
STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldClearEarliestOnEmptyCache 
PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldPreserveResetOffsetOnClearEarliestIfOneExists STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldPreserveResetOffsetOnClearEarliestIfOneExists PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldUpdateOffsetBetweenEpochBoundariesOnClearEarliest STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldUpdateOffsetBetweenEpochBoundariesOnClearEarliest PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldReturnInvalidOffsetIfEpochIsRequestedWhichIsNotCurrentlyTracked STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldReturnInvalidOffsetIfEpochIsRequestedWhichIsNotCurrentlyTracked PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldFetchEndOffsetOfEmptyCache 
STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldFetchEndOffsetOfEmptyCache 
PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldRetainLatestEpochOnClearAllEarliestAndUpdateItsOffset STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldRetainLatestEpochOnClearAllEarliestAndUpdateItsOffset PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldClearAllEntries STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldClearAllEntries PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldClearLatestOnEmptyCache 
STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldClearLatestOnEmptyCache 
PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldNotResetEpochHistoryHeadIfUndefinedPassed STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldNotResetEpochHistoryHeadIfUndefinedPassed PASSED

kafka.server.epoch.LeaderEpochIntegrationTest > 
shouldIncreaseLeaderEpochBetweenLeaderRestarts STARTED

kafka.server.epoch.LeaderEpochIntegrationTest > 
shouldIncreaseLeaderEpochBetweenLeaderRestarts PASSED

kafka.server.epoch.LeaderEpochIntegrationTest > 
shouldAddCurrentLeaderEpochToMessagesAsTheyAreWrittenToLeader STARTED

kafka.server.epoch.LeaderEpochIntegrationTest > 
shouldAddCurrentLeaderEpochToMessagesAsTheyAreWrittenToLeader PASSED

kafka.server.epoch.LeaderEpochIntegrationTest > 
shouldSendLeaderEpochRequestAndGetAResponse STARTED

kafka.server.epoch.LeaderEpochIntegrationTest > 
shouldSendLeaderEpochRequestAndGetAResponse PASSED

kafka.server.epoch.OffsetsForLeaderEpochTest > shouldGetEpochsFromReplica 
STARTED

kafka.server.epoch.OffsetsForLeaderEpochTest > shouldGetEpochsFromReplica PASSED

kafka.server.epoch.OffsetsForLeaderEpochTest > 
shouldReturnUnknownTopicOrPartitionIfThrown STARTED

kafka.server.epoch.OffsetsForLeaderEpochTest > 
shouldReturnUnknownTopicOrPartitionIfThrown PASSED

kafka.server.epoch.OffsetsForLeaderEpochTest > 
shouldReturnNoLeaderForPartitionIfThrown STARTED

kafka.server.epoch.OffsetsForLeaderEpochTest > 
shouldReturnNoLeaderForPartitionIfThrown PASSED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
shouldSurviveFastLeaderChange STARTED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
shouldSurviveFastLeaderChange PASSED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
offsetsShouldNotGoBackwards STARTED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
offsetsShouldNotGoBackwards PASSED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
shouldFollowLeaderEpochBasicWorkflow STARTED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
shouldFollowLeaderEpochBasicWorkflow PASSED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
shouldNotAllowDivergentLogs STARTED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
shouldNotAll

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

2018-02-20 Thread Apache Jenkins Server

See

Kafka with EBS on AWS : Raid-0 striping or multiple dirs in log.dirs

2018-02-20 Thread Somasundaram Sekar

AWS confluent quickstart
 configures
Kafka log.dirs with 4 - 512GB EBS block devices with RAID-0 striping for
higher throughput and also helps bypass the 1TB limit of block devices
without provisioned IOPS. I have just come across a statement that “*losing
a block device in the RAID will causing all the data of all of the other
block devices”*, can someone help clarify this!!



Now that Kafka allows multiple directories under log.dirs, *can we mount
each block device under a different mount point and configure them as a
list of directories under log.dirs?*



If that is possible(which it is, I guess), what are the trade-offs?

Thanks,

Somasundaram S

-- 
*Disclaimer*: This e-mail is intended to be delivered only to the named 
addressee(s). If this information is received by anyone other than the 
named addressee(s), the recipient(s) should immediately notify 
i...@tigeranalytics.com and promptly delete the transmitted material from 
your computer and server.   In no event shall this material be read, used, 
stored, or retained by anyone other than the named addressee(s) without the 
express written consent of the sender or the named addressee(s). Computer 
viruses can be transmitted viaemail. The recipient should check this email and 
any attachments for viruses. The company accepts no liability for any 
damage caused by any virus transmitted by this email.

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

2018-02-20 Thread Apache Jenkins Server

See

Save the date: ApacheCon North America, September 24-27 in Montréal

2018-02-20 Thread Rich Bowen


Dear Apache Enthusiast,

(You’re receiving this message because you’re subscribed to a user@ or 
dev@ list of one or more Apache Software Foundation projects.)


We’re pleased to announce the upcoming ApacheCon [1] in Montréal, 
September 24-27. This event is all about you — the Apache project community.


We’ll have four tracks of technical content this time, as well as lots 
of opportunities to connect with your project community, hack on the 
code, and learn about other related (and unrelated!) projects across the 
foundation.


The Call For Papers (CFP) [2] and registration are now open. Register 
early to take advantage of the early bird prices and secure your place 
at the event hotel.


Important dates
March 30: CFP closes
April 20: CFP notifications sent
	August 24: Hotel room block closes (please do not wait until the last 
minute)


Follow @ApacheCon on Twitter to be the first to hear announcements about 
keynotes, the schedule, evening events, and everything you can expect to 
see at the event.


See you in Montréal!

Sincerely, Rich Bowen, V.P. Events,
on behalf of the entire ApacheCon team

[1] http://www.apachecon.com/acna18
[2] https://cfp.apachecon.com/conference.html?apachecon-north-america-2018

Issues with Kafka

2018-02-20 Thread Shatadeep Banerjee

I am running Kafka in a multi-node, multi-broker setup. I have 3 machines (with 
Windows OS) connected in a cluster. When I close node 3, it can still send and 
receive messages, while node 2 cannot receive messages but can send messages. 
Why is this happening?
Shatadeep Banerjee

Sent from Mail for Windows 10

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

2018-02-20 Thread Apache Jenkins Server

See 


Changes:

[rajinisivaram] KAFKA-6554; Missing lastOffsetDelta validation before log 
append (#4585)

--
[...truncated 244.02 KB...]
kafka.api.SaslGssapiSslEndToEndAuthorizationTest > 
testProduceConsumeViaSubscribe STARTED

kafka.api.SaslGssapiSslEndToEndAuthorizationTest > 
testProduceConsumeViaSubscribe PASSED

kafka.api.SaslGssapiSslEndToEndAuthorizationTest > 
testNoProduceWithoutDescribeAcl STARTED

kafka.api.SaslGssapiSslEndToEndAuthorizationTest > 
testNoProduceWithoutDescribeAcl PASSED

kafka.zookeeper.ZooKeeperClientTest > testZNodeChangeHandlerForDataChange 
STARTED

kafka.zookeeper.ZooKeeperClientTest > testZNodeChangeHandlerForDataChange PASSED

kafka.zookeeper.ZooKeeperClientTest > testZooKeeperSessionStateMetric STARTED

kafka.zookeeper.ZooKeeperClientTest > testZooKeeperSessionStateMetric PASSED

kafka.zookeeper.ZooKeeperClientTest > testGetChildrenExistingZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testGetChildrenExistingZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testConnection STARTED

kafka.zookeeper.ZooKeeperClientTest > testConnection PASSED

kafka.zookeeper.ZooKeeperClientTest > testZNodeChangeHandlerForCreation STARTED

kafka.zookeeper.ZooKeeperClientTest > testZNodeChangeHandlerForCreation PASSED

kafka.zookeeper.ZooKeeperClientTest > testGetAclExistingZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testGetAclExistingZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testSetAclNonExistentZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testSetAclNonExistentZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testConnectionLossRequestTermination 
STARTED

kafka.zookeeper.ZooKeeperClientTest > testConnectionLossRequestTermination 
PASSED

kafka.zookeeper.ZooKeeperClientTest > testExistsNonExistentZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testExistsNonExistentZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testGetDataNonExistentZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testGetDataNonExistentZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testConnectionTimeout STARTED

kafka.zookeeper.ZooKeeperClientTest > testConnectionTimeout PASSED

kafka.zookeeper.ZooKeeperClientTest > testUnresolvableConnectString STARTED

kafka.zookeeper.ZooKeeperClientTest > testUnresolvableConnectString PASSED

kafka.zookeeper.ZooKeeperClientTest > testGetChildrenNonExistentZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testGetChildrenNonExistentZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testPipelinedGetData STARTED

kafka.zookeeper.ZooKeeperClientTest > testPipelinedGetData PASSED

kafka.zookeeper.ZooKeeperClientTest > testZNodeChildChangeHandlerForChildChange 
STARTED

kafka.zookeeper.ZooKeeperClientTest > testZNodeChildChangeHandlerForChildChange 
PASSED

kafka.zookeeper.ZooKeeperClientTest > testGetChildrenExistingZNodeWithChildren 
STARTED

kafka.zookeeper.ZooKeeperClientTest > testGetChildrenExistingZNodeWithChildren 
PASSED

kafka.zookeeper.ZooKeeperClientTest > testSetDataExistingZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testSetDataExistingZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testMixedPipeline STARTED

kafka.zookeeper.ZooKeeperClientTest > testMixedPipeline PASSED

kafka.zookeeper.ZooKeeperClientTest > testGetDataExistingZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testGetDataExistingZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testDeleteExistingZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testDeleteExistingZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testSessionExpiry STARTED

kafka.zookeeper.ZooKeeperClientTest > testSessionExpiry PASSED

kafka.zookeeper.ZooKeeperClientTest > testSetDataNonExistentZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testSetDataNonExistentZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testDeleteNonExistentZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testDeleteNonExistentZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testExistsExistingZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testExistsExistingZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testZooKeeperStateChangeRateMetrics 
STARTED
ERROR: No tool found matching GRADLE_3_4_RC_2_HOME
ERROR: Could not install GRADLE_4_4_HOME
java.lang.NullPointerException
at 
hudson.plugins.toolenv.ToolEnvBuildWrapper$1.buildEnvVars(ToolEnvBuildWrapper.java:46)
at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:895)
at hudson.plugins.git.GitSCM.getParamExpandedRepos(GitSCM.java:458)
at 
hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:666)
at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:631)
at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:391)
at hudson.scm.SCM.poll(SCM.java:408)
at hudson.model.AbstractProject._poll(AbstractProject.ja

Re: Issues with Kafka

2018-02-20 Thread Affan Syed

Could you elaborate a bit more.

a) what version of Kafka?
b) What do you mean by "it can still send/receive"? It cant be node 3 as it
is down.



- Affan

On Tue, Feb 20, 2018 at 3:47 PM, Shatadeep Banerjee <
shata_d...@yahoo.co.in.invalid> wrote:

> I am running Kafka in a multi-node, multi-broker setup. I have 3 machines
> (with Windows OS) connected in a cluster. When I close node 3, it can still
> send and receive messages, while node 2 cannot receive messages but can
> send messages. Why is this happening?
> Shatadeep Banerjee
>
> Sent from Mail for Windows 10
>
>

[jira] [Resolved] (KAFKA-5624) Unsafe use of expired sensors

2018-02-20 Thread Jason Gustafson (JIRA)


 [ 
https://issues.apache.org/jira/browse/KAFKA-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Gustafson resolved KAFKA-5624.

   Resolution: Fixed
Fix Version/s: 2.0.0

> Unsafe use of expired sensors
> -
>
> Key: KAFKA-5624
> URL: https://issues.apache.org/jira/browse/KAFKA-5624
> Project: Kafka
>  Issue Type: Bug
>Reporter: Jason Gustafson
>Assignee: Manikumar
>Priority: Major
> Fix For: 2.0.0
>
>
> Seems a couple unhandled cases following sensor expiration:
> 1. Static sensors (such as {{ClientQuotaManager.delayQueueSensor}}) can be 
> expired due to inactivity, but the references will remain valid and usable. 
> Probably a good idea to either ensure we use a "get or create" pattern when 
> accessing the sensor or add a new static registration option which makes the 
> sensor ineligible for expiration.
> 2. It is possible to register metrics through the sensor even after it is 
> expired. We should probably raise an exception instead.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-02-20 Thread Jason Gustafson (JIRA)


 [ 
https://issues.apache.org/jira/browse/KAFKA-6554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Gustafson resolved KAFKA-6554.

   Resolution: Fixed
Fix Version/s: 1.1.0

> Broker doesn't reject Produce request with inconsistent state
> -
>
> Key: KAFKA-6554
> URL: https://issues.apache.org/jira/browse/KAFKA-6554
> Project: Kafka
>  Issue Type: Bug
>  Components: producer 
>Affects Versions: 1.0.0
>Reporter: Simon Fell
>Assignee: Jason Gustafson
>Priority: Minor
> Fix For: 1.1.0
>
> Attachments: produce_v3.txt
>
>
> Produce messages of type v3 have offset deltas in each record along with a 
> LastOffsetDelta for the topic/partition set. In investigating an issue with 
> missing offsets, I found a bug in a producer library where it would send 
> multiple records, but leave LastOffsetDelta at 0. This causes various 
> problems including holes in the offsets fetched by the consumer. 
> As lastOffsetDelta can be computed by looking at the records, it seems like 
> the broker should at least validate the LastOffsetDelta field against the 
> contained records to stop this bad data getting in.
> I've attached a decode v3 produce message that was causing the problems, and 
> was accepted by the broker.
> Here's a link to the issue in the kafka library we were using which has more 
> context if you need it.
> https://github.com/Shopify/sarama/issues/1032
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-02-20 Thread Apache Jenkins Server

See

[jira] [Created] (KAFKA-6573) KafkaController.brokerInfo not updated on dynamic update

2018-02-20 Thread Rajini Sivaram (JIRA)

Rajini Sivaram created KAFKA-6573:
-

 Summary: KafkaController.brokerInfo not updated on dynamic update
 Key: KAFKA-6573
 URL: https://issues.apache.org/jira/browse/KAFKA-6573
 Project: Kafka
  Issue Type: Bug
  Components: controller
Affects Versions: 1.1.0
Reporter: Rajini Sivaram
Assignee: Rajini Sivaram
 Fix For: 1.1.0


KafkaController.brokerInfo is cached in-memory and used to re-register the 
broker in ZooKeeper if ZK session expires. It should be kept up-to-date if 
listeners are dynamically updated.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-02-20 Thread Apache Jenkins Server

See 


Changes:

[ismael] KAFKA-6568: Minor clean-ups follow-up (#4592)

--
[...truncated 241.18 KB...]

kafka.tools.ConsoleConsumerTest > 
shouldParseValidNewConsumerConfigWithAutoOffsetResetLatest PASSED

kafka.tools.ConsoleConsumerTest > shouldParseValidOldConsumerValidConfig STARTED

kafka.tools.ConsoleConsumerTest > shouldParseValidOldConsumerValidConfig PASSED

kafka.tools.ReplicaVerificationToolTest > testReplicaBufferVerifyChecksum 
STARTED

kafka.tools.ReplicaVerificationToolTest > testReplicaBufferVerifyChecksum PASSED

kafka.tools.ConsoleProducerTest > testParseKeyProp STARTED

kafka.tools.ConsoleProducerTest > testParseKeyProp PASSED

kafka.tools.ConsoleProducerTest > testValidConfigsOldProducer STARTED

kafka.tools.ConsoleProducerTest > testValidConfigsOldProducer PASSED

kafka.tools.ConsoleProducerTest > testInvalidConfigs STARTED

kafka.tools.ConsoleProducerTest > testInvalidConfigs PASSED

kafka.tools.ConsoleProducerTest > testValidConfigsNewProducer STARTED

kafka.tools.ConsoleProducerTest > testValidConfigsNewProducer PASSED

kafka.tools.MirrorMakerIntegrationTest > testCommaSeparatedRegex STARTED

kafka.tools.MirrorMakerIntegrationTest > testCommaSeparatedRegex PASSED

kafka.zookeeper.ZooKeeperClientTest > testZNodeChangeHandlerForDataChange 
STARTED

kafka.zookeeper.ZooKeeperClientTest > testZNodeChangeHandlerForDataChange PASSED

kafka.zookeeper.ZooKeeperClientTest > testZooKeeperSessionStateMetric STARTED

kafka.zookeeper.ZooKeeperClientTest > testZooKeeperSessionStateMetric PASSED

kafka.zookeeper.ZooKeeperClientTest > testGetChildrenExistingZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testGetChildrenExistingZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testConnection STARTED

kafka.zookeeper.ZooKeeperClientTest > testConnection PASSED

kafka.zookeeper.ZooKeeperClientTest > testZNodeChangeHandlerForCreation STARTED

kafka.zookeeper.ZooKeeperClientTest > testZNodeChangeHandlerForCreation PASSED

kafka.zookeeper.ZooKeeperClientTest > testGetAclExistingZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testGetAclExistingZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testSetAclNonExistentZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testSetAclNonExistentZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testConnectionLossRequestTermination 
STARTED

kafka.zookeeper.ZooKeeperClientTest > testConnectionLossRequestTermination 
PASSED

kafka.zookeeper.ZooKeeperClientTest > testExistsNonExistentZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testExistsNonExistentZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testGetDataNonExistentZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testGetDataNonExistentZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testConnectionTimeout STARTED

kafka.zookeeper.ZooKeeperClientTest > testConnectionTimeout PASSED

kafka.zookeeper.ZooKeeperClientTest > testUnresolvableConnectString STARTED

kafka.zookeeper.ZooKeeperClientTest > testUnresolvableConnectString PASSED

kafka.zookeeper.ZooKeeperClientTest > testGetChildrenNonExistentZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testGetChildrenNonExistentZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testPipelinedGetData STARTED

kafka.zookeeper.ZooKeeperClientTest > testPipelinedGetData PASSED

kafka.zookeeper.ZooKeeperClientTest > testZNodeChildChangeHandlerForChildChange 
STARTED

kafka.zookeeper.ZooKeeperClientTest > testZNodeChildChangeHandlerForChildChange 
PASSED

kafka.zookeeper.ZooKeeperClientTest > testGetChildrenExistingZNodeWithChildren 
STARTED

kafka.zookeeper.ZooKeeperClientTest > testGetChildrenExistingZNodeWithChildren 
PASSED

kafka.zookeeper.ZooKeeperClientTest > testSetDataExistingZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testSetDataExistingZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testMixedPipeline STARTED

kafka.zookeeper.ZooKeeperClientTest > testMixedPipeline PASSED

kafka.zookeeper.ZooKeeperClientTest > testGetDataExistingZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testGetDataExistingZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testDeleteExistingZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testDeleteExistingZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testSessionExpiry STARTED

kafka.zookeeper.ZooKeeperClientTest > testSessionExpiry PASSED

kafka.zookeeper.ZooKeeperClientTest > testSetDataNonExistentZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testSetDataNonExistentZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testDeleteNonExistentZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testDeleteNonExistentZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testExistsExistingZNode STARTED

kafka.zookeeper.ZooKeeperClientTest > testExistsExistingZNode PASSED

kafka.zookeeper.ZooKeeperClientTest > testZooKeeperStateChangeRateMetrics 
STARTED
ERROR: No tool

[jira] [Created] (KAFKA-6574) Support Headers in console-consumer and console-producer

2018-02-20 Thread Vik Gamov (JIRA)

Vik Gamov created KAFKA-6574:


 Summary: Support Headers in console-consumer and console-producer
 Key: KAFKA-6574
 URL: https://issues.apache.org/jira/browse/KAFKA-6574
 Project: Kafka
  Issue Type: Bug
  Components: consumer
Affects Versions: 1.0.0
Reporter: Vik Gamov


Message headers were introduced in 1.0.0 but console producer and consumer 
don't support them,



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-02-20 Thread Apache Jenkins Server

See 


Changes:

[damian.guy] MINOR: Fix streams broker compatibility test.

--
[...truncated 1.48 MB...]
kafka.zk.KafkaZkClientTest > testBrokerSequenceIdMethods PASSED

kafka.zk.KafkaZkClientTest > testCreateSequentialPersistentPath STARTED

kafka.zk.KafkaZkClientTest > testCreateSequentialPersistentPath PASSED

kafka.zk.KafkaZkClientTest > testConditionalUpdatePath STARTED

kafka.zk.KafkaZkClientTest > testConditionalUpdatePath PASSED

kafka.zk.KafkaZkClientTest > testTopicAssignmentMethods STARTED

kafka.zk.KafkaZkClientTest > testTopicAssignmentMethods PASSED

kafka.zk.KafkaZkClientTest > testPropagateIsrChanges STARTED

kafka.zk.KafkaZkClientTest > testPropagateIsrChanges PASSED

kafka.zk.KafkaZkClientTest > testDeleteRecursive STARTED

kafka.zk.KafkaZkClientTest > testDeleteRecursive PASSED

kafka.zk.KafkaZkClientTest > testDelegationTokenMethods STARTED

kafka.zk.KafkaZkClientTest > testDelegationTokenMethods PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > testSizeInBytesWithCompression 
STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > testSizeInBytesWithCompression 
PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > 
testIteratorIsConsistentWithCompression STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > 
testIteratorIsConsistentWithCompression PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > testIteratorIsConsistent 
STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > testIteratorIsConsistent PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > testEqualsWithCompression 
STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > testEqualsWithCompression 
PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > testWrittenEqualsRead STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > testWrittenEqualsRead PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > testEquals STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > testEquals PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > testSizeInBytes STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > testSizeInBytes PASSED

kafka.javaapi.consumer.ZookeeperConsumerConnectorTest > testBasic STARTED

kafka.javaapi.consumer.ZookeeperConsumerConnectorTest > testBasic PASSED

kafka.metrics.MetricsTest > testMetricsReporterAfterDeletingTopic STARTED

kafka.metrics.MetricsTest > testMetricsReporterAfterDeletingTopic PASSED

kafka.metrics.MetricsTest > testSessionExpireListenerMetrics STARTED

kafka.metrics.MetricsTest > testSessionExpireListenerMetrics PASSED

kafka.metrics.MetricsTest > 
testBrokerTopicMetricsUnregisteredAfterDeletingTopic STARTED

kafka.metrics.MetricsTest > 
testBrokerTopicMetricsUnregisteredAfterDeletingTopic PASSED

kafka.metrics.MetricsTest > testClusterIdMetric STARTED

kafka.metrics.MetricsTest > testClusterIdMetric PASSED

kafka.metrics.MetricsTest > testControllerMetrics STARTED

kafka.metrics.MetricsTest > testControllerMetrics PASSED

kafka.metrics.MetricsTest > testWindowsStyleTagNames STARTED

kafka.metrics.MetricsTest > testWindowsStyleTagNames PASSED

kafka.metrics.MetricsTest > testMetricsLeak STARTED

kafka.metrics.MetricsTest > testMetricsLeak PASSED

kafka.metrics.MetricsTest > testBrokerTopicMetricsBytesInOut STARTED

kafka.metrics.MetricsTest > testBrokerTopicMetricsBytesInOut PASSED

kafka.metrics.KafkaTimerTest > testKafkaTimer STARTED

kafka.metrics.KafkaTimerTest > testKafkaTimer PASSED

kafka.security.auth.ResourceTypeTest > testJavaConversions STARTED

kafka.security.auth.ResourceTypeTest > testJavaConversions PASSED

kafka.security.auth.ResourceTypeTest > testFromString STARTED

kafka.security.auth.ResourceTypeTest > testFromString PASSED

kafka.security.auth.OperationTest > testJavaConversions STARTED

kafka.security.auth.OperationTest > testJavaConversions PASSED

kafka.security.auth.ZkAuthorizationTest > testIsZkSecurityEnabled STARTED

kafka.security.auth.ZkAuthorizationTest > testIsZkSecurityEnabled PASSED

kafka.security.auth.ZkAuthorizationTest > testZkUtils STARTED

kafka.security.auth.ZkAuthorizationTest > testZkUtils PASSED

kafka.security.auth.ZkAuthorizationTest > testZkAntiMigration STARTED

kafka.security.auth.ZkAuthorizationTest > testZkAntiMigration PASSED

kafka.security.auth.ZkAuthorizationTest > testZkMigration STARTED

kafka.security.auth.ZkAuthorizationTest > testZkMigration PASSED

kafka.security.auth.ZkAuthorizationTest > testChroot STARTED

kafka.security.auth.ZkAuthorizationTest > testChroot PASSED

kafka.security.auth.ZkAuthorizationTest > testDelete STARTED

kafka.security.auth.ZkAuthorizationTest > testDelete PASSED

kafka.security.auth.ZkAuthorizationTest > testDeleteRecursive STARTED

kafka.security.auth.ZkAuthorizationTest > testDeleteRecursive PASSED

kafka.security.auth.AclTest > testAclJsonConversion STARTED

kafka.security.auth.AclTest > testAclJsonConversion PASSED

kafka.security.

[jira] [Resolved] (KAFKA-4651) Improve test coverage of Stores

2018-02-20 Thread Guozhang Wang (JIRA)


 [ 
https://issues.apache.org/jira/browse/KAFKA-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guozhang Wang resolved KAFKA-4651.
--
   Resolution: Fixed
 Assignee: Bill Bejeck
Fix Version/s: 1.2.0

> Improve test coverage of Stores
> ---
>
> Key: KAFKA-4651
> URL: https://issues.apache.org/jira/browse/KAFKA-4651
> Project: Kafka
>  Issue Type: Sub-task
>  Components: streams
>Reporter: Damian Guy
>Assignee: Bill Bejeck
>Priority: Minor
>  Labels: newbie
> Fix For: 1.2.0
>
>
> Some factory methods aren't tested



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] 1.0.1 RC1

2018-02-20 Thread Ewen Cheslack-Postava

Just a heads up that an issue with upgrades was found
https://issues.apache.org/jira/browse/KAFKA-6238 There's a PR in progress
to address the underlying issue. There was a workaround, but it looked like
this would cause more pain than doing one more RC, so we'll have an RC2 up
soon after the PR is merged.

-Ewen

On Fri, Feb 16, 2018 at 3:53 AM, Mickael Maison 
wrote:

> Ran tests from source and quickstart with binaries
>
> +1 (non-binding)
>
> On Fri, Feb 16, 2018 at 6:05 AM, Jason Gustafson 
> wrote:
> > +1. Verified artifacts and ran quickstart. Thanks Ewen!
> >
> > -Jason
> >
> > On Thu, Feb 15, 2018 at 1:42 AM, Rajini Sivaram  >
> > wrote:
> >
> >> +1
> >>
> >> Ran quickstart with binaries, built source and ran tests,
> >>
> >> Thank you for running the release, Ewen.
> >>
> >> Regards,
> >>
> >> Rajini
> >>
> >> On Thu, Feb 15, 2018 at 2:31 AM, Guozhang Wang 
> wrote:
> >>
> >> > +1
> >> >
> >> > Ran tests, verified web docs.
> >> >
> >> > On Wed, Feb 14, 2018 at 6:00 PM, Satish Duggana <
> >> satish.dugg...@gmail.com>
> >> > wrote:
> >> >
> >> > > +1 (non-binding)
> >> > >
> >> > > - Ran testAll/releaseTarGzAll on 1.0.1-rc1
> >> > >  tag
> >> > > - Ran through quickstart of core/streams
> >> > >
> >> > > Thanks,
> >> > > Satish.
> >> > >
> >> > >
> >> > > On Tue, Feb 13, 2018 at 11:30 PM, Damian Guy 
> >> > wrote:
> >> > >
> >> > > > +1
> >> > > >
> >> > > > Ran tests, verified streams quickstart works
> >> > > >
> >> > > > On Tue, 13 Feb 2018 at 17:52 Damian Guy 
> >> wrote:
> >> > > >
> >> > > > > Thanks Ewen - i had the staging repo set up as profile that i
> >> forgot
> >> > to
> >> > > > > add to my maven command. All good.
> >> > > > >
> >> > > > > On Tue, 13 Feb 2018 at 17:41 Ewen Cheslack-Postava <
> >> > e...@confluent.io>
> >> > > > > wrote:
> >> > > > >
> >> > > > >> Damian,
> >> > > > >>
> >> > > > >> Which quickstart are you referring to? The streams quickstart
> only
> >> > > > >> executes
> >> > > > >> pre-built stuff afaict.
> >> > > > >>
> >> > > > >> In any case, if you're building a maven streams project, did
> you
> >> > > modify
> >> > > > it
> >> > > > >> to point to the staging repository at
> >> > > > >> https://repository.apache.org/content/groups/staging/ in
> addition
> >> > to
> >> > > > the
> >> > > > >> default repos? During rc it wouldn't fetch from maven central
> >> since
> >> > it
> >> > > > >> hasn't been published there yet.
> >> > > > >>
> >> > > > >> If that is configured, more compete maven output would be
> helpful
> >> to
> >> > > > track
> >> > > > >> down where it is failing to resolve the necessary archetype.
> >> > > > >>
> >> > > > >> -Ewen
> >> > > > >>
> >> > > > >> On Tue, Feb 13, 2018 at 3:03 AM, Damian Guy <
> damian@gmail.com
> >> >
> >> > > > wrote:
> >> > > > >>
> >> > > > >> > Hi Ewen,
> >> > > > >> >
> >> > > > >> > I'm trying to run the streams quickstart and I'm getting:
> >> > > > >> > [ERROR] Failed to execute goal
> >> > > > >> > org.apache.maven.plugins:maven-archetype-plugin:3.0.1:
> generate
> >> > > > >> > (default-cli) on project standalone-pom: The desired
> archetype
> >> > does
> >> > > > not
> >> > > > >> > exist (org.apache.kafka:streams-quickstart-java:1.0.1)
> >> > > > >> >
> >> > > > >> > Something i'm missing?
> >> > > > >> >
> >> > > > >> > Thanks,
> >> > > > >> > Damian
> >> > > > >> >
> >> > > > >> > On Tue, 13 Feb 2018 at 10:16 Manikumar <
> >> manikumar.re...@gmail.com
> >> > >
> >> > > > >> wrote:
> >> > > > >> >
> >> > > > >> > > +1 (non-binding)
> >> > > > >> > >
> >> > > > >> > > ran quick-start, unit tests on the src.
> >> > > > >> > >
> >> > > > >> > >
> >> > > > >> > >
> >> > > > >> > > On Tue, Feb 13, 2018 at 5:31 AM, Ewen Cheslack-Postava <
> >> > > > >> > e...@confluent.io>
> >> > > > >> > > wrote:
> >> > > > >> > >
> >> > > > >> > > > Thanks for the heads up, I forgot to drop the old ones,
> I've
> >> > > done
> >> > > > >> that
> >> > > > >> > > and
> >> > > > >> > > > rc1 artifacts should be showing up now.
> >> > > > >> > > >
> >> > > > >> > > > -Ewen
> >> > > > >> > > >
> >> > > > >> > > >
> >> > > > >> > > > On Mon, Feb 12, 2018 at 12:57 PM, Ted Yu <
> >> yuzhih...@gmail.com
> >> > >
> >> > > > >> wrote:
> >> > > > >> > > >
> >> > > > >> > > > > +1
> >> > > > >> > > > >
> >> > > > >> > > > > Ran test suite which passed.
> >> > > > >> > > > >
> >> > > > >> > > > > BTW it seems the staging repo hasn't been updated yet:
> >> > > > >> > > > >
> >> > > > >> > > > > https://repository.apache.org/
> content/groups/staging/org/
> >> > > > >> > > > > apache/kafka/kafka-clients/
> >> > > > >> > > > >
> >> > > > >> > > > > On Mon, Feb 12, 2018 at 10:16 AM, Ewen
> Cheslack-Postava <
> >> > > > >> > > > e...@confluent.io
> >> > > > >> > > > > >
> >> > > > >> > > > > wrote:
> >> > > > >> > > > >
> >> > > > >> > > > > > And of course I'm +1 since I've already done normal
> >> > release
> >> > > > >> > > validation
> >> > > > >> > > > > > before posting this.
> >> > >

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

2018-02-20 Thread Apache Jenkins Server

See

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

2018-02-20 Thread Apache Jenkins Server

See 


Changes:

[rajinisivaram] MINOR: Fix logger name override (#4600)

--
[...truncated 410.88 KB...]

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldNotClearAnythingIfOffsetToFirstOffset STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldNotClearAnythingIfOffsetToFirstOffset PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldNotLetOffsetsGoBackwardsEvenIfEpochsProgress STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldNotLetOffsetsGoBackwardsEvenIfEpochsProgress PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldGetFirstOffsetOfSubsequentEpochWhenOffsetRequestedForPreviousEpoch STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldGetFirstOffsetOfSubsequentEpochWhenOffsetRequestedForPreviousEpoch PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldUpdateOffsetBetweenEpochBoundariesOnClearEarliest2 STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldUpdateOffsetBetweenEpochBoundariesOnClearEarliest2 PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldClearEarliestOnEmptyCache 
STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldClearEarliestOnEmptyCache 
PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldPreserveResetOffsetOnClearEarliestIfOneExists STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldPreserveResetOffsetOnClearEarliestIfOneExists PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldUpdateOffsetBetweenEpochBoundariesOnClearEarliest STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldUpdateOffsetBetweenEpochBoundariesOnClearEarliest PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldReturnInvalidOffsetIfEpochIsRequestedWhichIsNotCurrentlyTracked STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldReturnInvalidOffsetIfEpochIsRequestedWhichIsNotCurrentlyTracked PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldFetchEndOffsetOfEmptyCache 
STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldFetchEndOffsetOfEmptyCache 
PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldRetainLatestEpochOnClearAllEarliestAndUpdateItsOffset STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldRetainLatestEpochOnClearAllEarliestAndUpdateItsOffset PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldClearAllEntries STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldClearAllEntries PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldClearLatestOnEmptyCache 
STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > shouldClearLatestOnEmptyCache 
PASSED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldNotResetEpochHistoryHeadIfUndefinedPassed STARTED

kafka.server.epoch.LeaderEpochFileCacheTest > 
shouldNotResetEpochHistoryHeadIfUndefinedPassed PASSED

kafka.server.epoch.LeaderEpochIntegrationTest > 
shouldIncreaseLeaderEpochBetweenLeaderRestarts STARTED

kafka.server.epoch.LeaderEpochIntegrationTest > 
shouldIncreaseLeaderEpochBetweenLeaderRestarts PASSED

kafka.server.epoch.LeaderEpochIntegrationTest > 
shouldAddCurrentLeaderEpochToMessagesAsTheyAreWrittenToLeader STARTED

kafka.server.epoch.LeaderEpochIntegrationTest > 
shouldAddCurrentLeaderEpochToMessagesAsTheyAreWrittenToLeader PASSED

kafka.server.epoch.LeaderEpochIntegrationTest > 
shouldSendLeaderEpochRequestAndGetAResponse STARTED

kafka.server.epoch.LeaderEpochIntegrationTest > 
shouldSendLeaderEpochRequestAndGetAResponse PASSED

kafka.server.epoch.OffsetsForLeaderEpochTest > shouldGetEpochsFromReplica 
STARTED

kafka.server.epoch.OffsetsForLeaderEpochTest > shouldGetEpochsFromReplica PASSED

kafka.server.epoch.OffsetsForLeaderEpochTest > 
shouldReturnUnknownTopicOrPartitionIfThrown STARTED

kafka.server.epoch.OffsetsForLeaderEpochTest > 
shouldReturnUnknownTopicOrPartitionIfThrown PASSED

kafka.server.epoch.OffsetsForLeaderEpochTest > 
shouldReturnNoLeaderForPartitionIfThrown STARTED

kafka.server.epoch.OffsetsForLeaderEpochTest > 
shouldReturnNoLeaderForPartitionIfThrown PASSED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
shouldSurviveFastLeaderChange STARTED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
shouldSurviveFastLeaderChange PASSED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
offsetsShouldNotGoBackwards STARTED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
offsetsShouldNotGoBackwards PASSED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
shouldFollowLeaderEpochBasicWorkflow STARTED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
shouldFollowLeaderEpochBasicWorkflow PASSED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
shouldNotAllowDivergentLogs STARTED

kafka.server.epoch.EpochDrivenReplicationProtocolAcceptanceTest > 
shouldNotAllowDivergentLogs PASSED

kafka.server.M

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

2018-02-20 Thread Apache Jenkins Server

See 


Changes:

[rajinisivaram] MINOR: Fix logger name override (#4600)

--
[...truncated 1.48 MB...]

kafka.zk.KafkaZkClientTest > testCreateSequentialPersistentPath STARTED

kafka.zk.KafkaZkClientTest > testCreateSequentialPersistentPath PASSED

kafka.zk.KafkaZkClientTest > testConditionalUpdatePath STARTED

kafka.zk.KafkaZkClientTest > testConditionalUpdatePath PASSED

kafka.zk.KafkaZkClientTest > testTopicAssignmentMethods STARTED

kafka.zk.KafkaZkClientTest > testTopicAssignmentMethods PASSED

kafka.zk.KafkaZkClientTest > testPropagateIsrChanges STARTED

kafka.zk.KafkaZkClientTest > testPropagateIsrChanges PASSED

kafka.zk.KafkaZkClientTest > testDeleteRecursive STARTED

kafka.zk.KafkaZkClientTest > testDeleteRecursive PASSED

kafka.zk.KafkaZkClientTest > testDelegationTokenMethods STARTED

kafka.zk.KafkaZkClientTest > testDelegationTokenMethods PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > testSizeInBytesWithCompression 
STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > testSizeInBytesWithCompression 
PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > 
testIteratorIsConsistentWithCompression STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > 
testIteratorIsConsistentWithCompression PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > testIteratorIsConsistent 
STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > testIteratorIsConsistent PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > testEqualsWithCompression 
STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > testEqualsWithCompression 
PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > testWrittenEqualsRead STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > testWrittenEqualsRead PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > testEquals STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > testEquals PASSED

kafka.javaapi.message.ByteBufferMessageSetTest > testSizeInBytes STARTED

kafka.javaapi.message.ByteBufferMessageSetTest > testSizeInBytes PASSED

kafka.javaapi.consumer.ZookeeperConsumerConnectorTest > testBasic STARTED

kafka.javaapi.consumer.ZookeeperConsumerConnectorTest > testBasic PASSED

kafka.metrics.MetricsTest > testMetricsReporterAfterDeletingTopic STARTED

kafka.metrics.MetricsTest > testMetricsReporterAfterDeletingTopic PASSED

kafka.metrics.MetricsTest > testSessionExpireListenerMetrics STARTED

kafka.metrics.MetricsTest > testSessionExpireListenerMetrics PASSED

kafka.metrics.MetricsTest > 
testBrokerTopicMetricsUnregisteredAfterDeletingTopic STARTED

kafka.metrics.MetricsTest > 
testBrokerTopicMetricsUnregisteredAfterDeletingTopic PASSED

kafka.metrics.MetricsTest > testClusterIdMetric STARTED

kafka.metrics.MetricsTest > testClusterIdMetric PASSED

kafka.metrics.MetricsTest > testControllerMetrics STARTED

kafka.metrics.MetricsTest > testControllerMetrics PASSED

kafka.metrics.MetricsTest > testWindowsStyleTagNames STARTED

kafka.metrics.MetricsTest > testWindowsStyleTagNames PASSED

kafka.metrics.MetricsTest > testMetricsLeak STARTED

kafka.metrics.MetricsTest > testMetricsLeak PASSED

kafka.metrics.MetricsTest > testBrokerTopicMetricsBytesInOut STARTED

kafka.metrics.MetricsTest > testBrokerTopicMetricsBytesInOut PASSED

kafka.metrics.KafkaTimerTest > testKafkaTimer STARTED

kafka.metrics.KafkaTimerTest > testKafkaTimer PASSED

kafka.security.auth.ResourceTypeTest > testJavaConversions STARTED

kafka.security.auth.ResourceTypeTest > testJavaConversions PASSED

kafka.security.auth.ResourceTypeTest > testFromString STARTED

kafka.security.auth.ResourceTypeTest > testFromString PASSED

kafka.security.auth.OperationTest > testJavaConversions STARTED

kafka.security.auth.OperationTest > testJavaConversions PASSED

kafka.security.auth.ZkAuthorizationTest > testIsZkSecurityEnabled STARTED

kafka.security.auth.ZkAuthorizationTest > testIsZkSecurityEnabled PASSED

kafka.security.auth.ZkAuthorizationTest > testZkUtils STARTED

kafka.security.auth.ZkAuthorizationTest > testZkUtils PASSED

kafka.security.auth.ZkAuthorizationTest > testZkAntiMigration STARTED

kafka.security.auth.ZkAuthorizationTest > testZkAntiMigration PASSED

kafka.security.auth.ZkAuthorizationTest > testZkMigration STARTED

kafka.security.auth.ZkAuthorizationTest > testZkMigration PASSED

kafka.security.auth.ZkAuthorizationTest > testChroot STARTED

kafka.security.auth.ZkAuthorizationTest > testChroot PASSED

kafka.security.auth.ZkAuthorizationTest > testDelete STARTED

kafka.security.auth.ZkAuthorizationTest > testDelete PASSED

kafka.security.auth.ZkAuthorizationTest > testDeleteRecursive STARTED

kafka.security.auth.ZkAuthorizationTest > testDeleteRecursive PASSED

kafka.security.auth.AclTest > testAclJsonConversion STARTED

kafka.security.auth.AclTest > testAclJsonConversion PASSED

kafka.security.auth.PermissionTypeTest > testJavaConversions STARTED

kafka.securi

[jira] [Resolved] (KAFKA-1457) Nginx Kafka Integration

2018-02-20 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/KAFKA-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sönke Liebau resolved KAFKA-1457.
-
Resolution: Not A Problem

I think this issue can safely be closed, there are numerous solutions out there 
for pushing log files into Kafka:
* Kafka Connect Filesource
* Filebeat
* Logstash
* Heka
* Collectd

We could actually consider closing this as "fixed" since with Kafka Connect one 
might argue that Kafka now offers a component for what [~darion] wants to do :)

> Nginx Kafka Integration
> ---
>
> Key: KAFKA-1457
> URL: https://issues.apache.org/jira/browse/KAFKA-1457
> Project: Kafka
>  Issue Type: Wish
>  Components: tools
>Reporter: darion yaphet
>Priority: Minor
>  Labels: DataSource
>
> Some use Kafka as log data collector and nginx is the web server . we need to 
> push nginx log into kafka but I don't know how to write the plugin
> Would Apacha Kafka provide  a nginx module to push nginx log into kafka ? 
> Thanks a lot   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Jenkins build is back to normal : kafka-1.1-jdk7 #54

2018-02-20 Thread Apache Jenkins Server

See

[jira] [Resolved] (KAFKA-1689) automatic migration of log dirs to new locations

2018-02-20 Thread JIRA


 [ 
https://issues.apache.org/jira/browse/KAFKA-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sönke Liebau resolved KAFKA-1689.
-
   Resolution: Fixed
Fix Version/s: 1.1.0

The requested functionality is available as part of KAFKA-5163

> automatic migration of log dirs to new locations
> 
>
> Key: KAFKA-1689
> URL: https://issues.apache.org/jira/browse/KAFKA-1689
> Project: Kafka
>  Issue Type: New Feature
>  Components: config, core
>Affects Versions: 0.8.1.1
>Reporter: Javier Alba
>Priority: Minor
>  Labels: newbie++
> Fix For: 1.1.0
>
>
> There is no automated way in Kafka 0.8.1.1 to make a migration of log data if 
> we want to reconfigure our cluster nodes to use several data directories 
> where we have mounted new disks instead our original data directory.
> For example, say we have our brokers configured with:
>   log.dirs = /tmp/kafka-logs
> And we added 3 new disks and now we want our brokers to use them as log.dirs:
>   logs.dirs = /srv/data/1,/srv/data/2,/srv/data/3
> It would be great to have an automated way of doing such a migration, of 
> course without losing current data in the cluster.
> It would be ideal to be able to do this migration without losing service.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2018-02-20 Thread Apache Jenkins Server

See

Do the Jackson security vulnerabilities affect Kafka at all?

2018-02-20 Thread Jeff Widman

The Jackson JSON parser library had a couple of CVE's announced:
1. CVE-2017-7525
2. CVE 2017-15095

Here's a skimmable summary:
https://adamcaudill.com/2017/10/04/exploiting-jackson-rce-cve-2017-7525/

Looking at the source, it appears Kafka uses an older version of Jackson
which has the vulnerabilities.

However, these vulnerabilities only happen when Jackson is used in specific
ways. I'm not familiar enough with all the places that Kafka uses Jackson
to understand whether Kafka is susceptible, and I come from a non-Java
background so it's difficult for me to parse the Java source with 100%
confidence that I understand what's happening.

I know primarily Kafka uses JSON for inter-cluster communication through
Zookeeper, so if an attacker could access Zookeeper could they update the
znode payloads to exploit this? Additionally, I think there are some util
scripts that (de)serialize JSON files, for example the
partition-reassignment scripts...

So do these CVE's apply to Kafka?

If so, it seem the patch is fairly trivial of just upgrading to a newer
version of Jackson...
should this also be backported to the 1.0.1 release?



-- 

*Jeff Widman*
jeffwidman.com  | 740-WIDMAN-J (943-6265)
<><

Re: Do the Jackson security vulnerabilities affect Kafka at all?

2018-02-20 Thread Ismael Juma

Hi Jeff,

Have you checked trunk and 1.1? They should be using the latest version.

Ismael

On Tue, Feb 20, 2018 at 10:38 PM, Jeff Widman  wrote:

> The Jackson JSON parser library had a couple of CVE's announced:
> 1. CVE-2017-7525
> 2. CVE 2017-15095
>
> Here's a skimmable summary:
> https://adamcaudill.com/2017/10/04/exploiting-jackson-rce-cve-2017-7525/
>
> Looking at the source, it appears Kafka uses an older version of Jackson
> which has the vulnerabilities.
>
> However, these vulnerabilities only happen when Jackson is used in specific
> ways. I'm not familiar enough with all the places that Kafka uses Jackson
> to understand whether Kafka is susceptible, and I come from a non-Java
> background so it's difficult for me to parse the Java source with 100%
> confidence that I understand what's happening.
>
> I know primarily Kafka uses JSON for inter-cluster communication through
> Zookeeper, so if an attacker could access Zookeeper could they update the
> znode payloads to exploit this? Additionally, I think there are some util
> scripts that (de)serialize JSON files, for example the
> partition-reassignment scripts...
>
> So do these CVE's apply to Kafka?
>
> If so, it seem the patch is fairly trivial of just upgrading to a newer
> version of Jackson...
> should this also be backported to the 1.0.1 release?
>
>
>
> --
>
> *Jeff Widman*
> jeffwidman.com  | 740-WIDMAN-J (943-6265)
> <><
>

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

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

Kafka with EBS on AWS : Raid-0 striping or multiple dirs in log.dirs

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

Save the date: ApacheCon North America, September 24-27 in Montréal

Issues with Kafka

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

Re: Issues with Kafka

[jira] [Resolved] (KAFKA-5624) Unsafe use of expired sensors

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

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

[jira] [Created] (KAFKA-6573) KafkaController.brokerInfo not updated on dynamic update

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

[jira] [Created] (KAFKA-6574) Support Headers in console-consumer and console-producer

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

[jira] [Resolved] (KAFKA-4651) Improve test coverage of Stores

Re: [VOTE] 1.0.1 RC1

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

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

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

[jira] [Resolved] (KAFKA-1457) Nginx Kafka Integration

Jenkins build is back to normal : kafka-1.1-jdk7 #54

[jira] [Resolved] (KAFKA-1689) automatic migration of log dirs to new locations

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

Do the Jackson security vulnerabilities affect Kafka at all?

Re: Do the Jackson security vulnerabilities affect Kafka at all?

26 matches

Site Navigation

Mail list logo

Footer information