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

See Changes: [harsha] KAFKA-2551; Update Unclean leader election docs -- [...truncated 2974 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanShutdownFile PASSED

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

See Changes: [harsha] KAFKA-2551; Update Unclean leader election docs -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-us1 (Ubuntu ubuntu

[jira] [Commented] (KAFKA-2551) Unclean leader election docs outdated

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

[GitHub] kafka pull request: KAFKA-2551: Update Unclean leader election doc...

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

[GitHub] kafka pull request: Update design.html

GitHub user stevejs opened a pull request: https://github.com/apache/kafka/pull/1057 Update design.html Fix typo. You can merge this pull request into a Git repository by running: $ git pull https://github.com/stevejs/kafka patch-1 Alternatively you can review and apply these

[jira] [Commented] (KAFKA-3334) First message on new topic not actually being sent, no exception thrown

[ https://issues.apache.org/jira/browse/KAFKA-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192592#comment-15192592 ] Ismael Juma commented on KAFKA-3334: It doesn't seem to me that documenting this is en

[jira] [Comment Edited] (KAFKA-2464) Client-side assignment and group generalization

[ https://issues.apache.org/jira/browse/KAFKA-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192580#comment-15192580 ] Jiangjie Qin edited comment on KAFKA-2464 at 3/14/16 12:09 AM: -

[jira] [Commented] (KAFKA-2464) Client-side assignment and group generalization

[ https://issues.apache.org/jira/browse/KAFKA-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192580#comment-15192580 ] Jiangjie Qin commented on KAFKA-2464: - [~hachikuji] I just noticed that in KafkaConfig

[jira] [Updated] (KAFKA-3388) Producer should only timeout a batch in the accumulator when metadata is missing.

[ https://issues.apache.org/jira/browse/KAFKA-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3388: Reviewer: Jun Rao > Producer should only timeout a batch in the accumulator when metadata is > miss

[GitHub] kafka pull request: KAFKA-3388: Fix expiration of batches sitting ...

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1056 KAFKA-3388: Fix expiration of batches sitting in the accumulator You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA-3388 A

[jira] [Commented] (KAFKA-3388) Producer should only timeout a batch in the accumulator when metadata is missing.

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

[jira] [Updated] (KAFKA-3388) Producer should only timeout a batch in the accumulator when metadata is missing.

[ https://issues.apache.org/jira/browse/KAFKA-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3388: Status: Patch Available (was: Open) > Producer should only timeout a batch in the accumulator when

Re: KStreams Proposal

Hi Guozhang, Possibly, but the use case I'm working with is having a of collector object , for aggregate statistics for example, that would output results intermittently (via punctuate). The issue for me is that 'transform(..)' returns a key-value pair for each message, possibly of a different

[jira] [Commented] (KAFKA-3388) Producer should only timeout a batch in the accumulator when metadata is missing.

[ https://issues.apache.org/jira/browse/KAFKA-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192539#comment-15192539 ] Jiangjie Qin commented on KAFKA-3388: - [~mgharat] Can you take a look and see if I mis

[jira] [Commented] (KAFKA-3388) Producer should only timeout a batch in the accumulator when metadata is missing.

[ https://issues.apache.org/jira/browse/KAFKA-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192536#comment-15192536 ] Ismael Juma commented on KAFKA-3388: Perfect, thanks. > Producer should only timeout

[jira] [Commented] (KAFKA-3388) Producer should only timeout a batch in the accumulator when metadata is missing.

[ https://issues.apache.org/jira/browse/KAFKA-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192535#comment-15192535 ] Jiangjie Qin commented on KAFKA-3388: - [~ijuma] I am currently blocked on this issue a

[jira] [Assigned] (KAFKA-3388) Producer should only timeout a batch in the accumulator when metadata is missing.

[ https://issues.apache.org/jira/browse/KAFKA-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-3388: --- Assignee: Jiangjie Qin > Producer should only timeout a batch in the accumulator when metadat

Re: KStreams Proposal

Hello Bill, We added transform() together with process() to support any user-customized stateful processor that can still concatenate to another KStream. So for your case, would `transform(...).to(topic)` provide the same functionality as "processTo(topic, ...)"? Guozhang On Sat, Mar 12, 2016

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

Agree with Gwen here. I feel like these additional pluggable Login Modules are making this KIP complex. Since the main goal of the KIP is to enable additional mechanism , can we limit the scope to that and If we feel necessary for pluggable Login and callback handler classes we can address in anoth

[jira] [Updated] (KAFKA-3392) ConsumerRecords iterator throws NoSuchElementException when a TopicPartition is empty

[ https://issues.apache.org/jira/browse/KAFKA-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Drausin Wulsin updated KAFKA-3392: -- Reviewer: Jay Kreps Status: Patch Available (was: Open) > ConsumerRecords iterator throws

[GitHub] kafka pull request: KAFKA-3392: ConsumerRecords iterator throws No...

GitHub user drausin opened a pull request: https://github.com/apache/kafka/pull/1055 KAFKA-3392: ConsumerRecords iterator throws NoSuchElementException when a TopicPartition is empty This contribution is my original work, and I license it under the project's open source license. Y

[jira] [Commented] (KAFKA-3392) ConsumerRecords iterator throws NoSuchElementException when a TopicPartition is empty

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

[jira] [Created] (KAFKA-3392) ConsumerRecords iterator throws NoSuchElementException when a TopicPartition is empty

Drausin Wulsin created KAFKA-3392: - Summary: ConsumerRecords iterator throws NoSuchElementException when a TopicPartition is empty Key: KAFKA-3392 URL: https://issues.apache.org/jira/browse/KAFKA-3392

[jira] [Updated] (KAFKA-3391) Kafka to ZK timeout

[ https://issues.apache.org/jira/browse/KAFKA-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Reddy updated KAFKA-3391: - Description: Hi Team, We have seen the below messages in the Kafka logs, indicating there was a

[jira] [Created] (KAFKA-3391) Kafka to ZK timeout

Karthik Reddy created KAFKA-3391: Summary: Kafka to ZK timeout Key: KAFKA-3391 URL: https://issues.apache.org/jira/browse/KAFKA-3391 Project: Kafka Issue Type: Bug Components: cons

[jira] [Updated] (KAFKA-3390) ReplicaManager may infinitely try-fail to shrink ISR set of deleted partition

[ https://issues.apache.org/jira/browse/KAFKA-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stevo Slavic updated KAFKA-3390: Description: For a topic whose deletion has been requested, Kafka replica manager may end up infini

[jira] [Created] (KAFKA-3390) ReplicaManager may infinitely try-fail to shrink ISR set of deleted partition

Stevo Slavic created KAFKA-3390: --- Summary: ReplicaManager may infinitely try-fail to shrink ISR set of deleted partition Key: KAFKA-3390 URL: https://issues.apache.org/jira/browse/KAFKA-3390 Project: Ka

[jira] [Created] (KAFKA-3389) ReplicaStateMachine areAllReplicasForTopicDeleted check not handling well case when there are no replicas for topic

Stevo Slavic created KAFKA-3389: --- Summary: ReplicaStateMachine areAllReplicasForTopicDeleted check not handling well case when there are no replicas for topic Key: KAFKA-3389 URL: https://issues.apache.org/jira/brow

[jira] [Commented] (KAFKA-3388) Producer should only timeout a batch in the accumulator when metadata is missing.

[ https://issues.apache.org/jira/browse/KAFKA-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192225#comment-15192225 ] Ismael Juma commented on KAFKA-3388: [~becket_qin], are you intending to work on this

[jira] [Updated] (KAFKA-3330) Truncate log cleaner offset checkpoint if the log is truncated

[ https://issues.apache.org/jira/browse/KAFKA-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3330: --- Reviewer: Jun Rao Status: Patch Available (was: Open) > Truncate log cleaner offset checkpoint

[jira] [Updated] (KAFKA-3047) Explicit offset assignment in Log.append can corrupt the log

[ https://issues.apache.org/jira/browse/KAFKA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3047: --- Resolution: Fixed Reviewer: Guozhang Wang (was: Jun Rao) Status: Resolved (was: Patch A

[jira] [Updated] (KAFKA-3047) Explicit offset assignment in Log.append can corrupt the log

[ https://issues.apache.org/jira/browse/KAFKA-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3047: --- Priority: Major (was: Blocker) > Explicit offset assignment in Log.append can corrupt the log > -