[GitHub] kafka pull request: MINOR: MetadataCache brokerId is not set on fi...

Github user granthenke closed the pull request at: https://github.com/apache/kafka/pull/1299 --- 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-3585) Shutdown slow when there is only one broker which is controller

[ https://issues.apache.org/jira/browse/KAFKA-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266141#comment-15266141 ] Gwen Shapira commented on KAFKA-3585: - Thanks for volunteering [~firstprayer]. I added you as

[jira] [Updated] (KAFKA-3585) Shutdown slow when there is only one broker which is controller

[ https://issues.apache.org/jira/browse/KAFKA-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3585: Assignee: Taiyuan Zhang > Shutdown slow when there is only one broker which is controller >

[jira] [Commented] (KAFKA-3646) Console producer using new producer should set timestamp

[ https://issues.apache.org/jira/browse/KAFKA-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266140#comment-15266140 ] Gwen Shapira commented on KAFKA-3646: - Keep in mind that the console producer also defaults to empty

[jira] [Commented] (KAFKA-3646) Console producer using new producer should set timestamp

[ https://issues.apache.org/jira/browse/KAFKA-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266129#comment-15266129 ] Michael Noll commented on KAFKA-3646: - We should also think about whether a negative timestamp (-1)

[jira] [Commented] (KAFKA-3585) Shutdown slow when there is only one broker which is controller

[ https://issues.apache.org/jira/browse/KAFKA-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266130#comment-15266130 ] Taiyuan Zhang commented on KAFKA-3585: -- Interested. How do I assign this to myself...? > Shutdown

[jira] [Updated] (KAFKA-3642) Fix NPE from ProcessorStateManager when the changelog topic not exists

[ https://issues.apache.org/jira/browse/KAFKA-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3642: - Reviewer: Guozhang Wang > Fix NPE from ProcessorStateManager when the changelog topic not exists

[jira] [Updated] (KAFKA-3642) Fix NPE from ProcessorStateManager when the changelog topic not exists

[ https://issues.apache.org/jira/browse/KAFKA-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3642: - Labels: architecture (was: ) > Fix NPE from ProcessorStateManager when the changelog topic not

[jira] [Created] (KAFKA-3646) Console producer using new producer should set timestamp

Guozhang Wang created KAFKA-3646: Summary: Console producer using new producer should set timestamp Key: KAFKA-3646 URL: https://issues.apache.org/jira/browse/KAFKA-3646 Project: Kafka Issue

Re: [VOTE] KIP-50: Move Authorizer to o.a.k.common package - Round 2

+1 (non binding) On 4/28/16, 7:47 AM, "Jun Rao" wrote: >Ashish, > >Thanks for the proposal. +1 > >Jun > >On Mon, Apr 25, 2016 at 10:04 AM, Ashish Singh wrote: > >> Hey Guys, >> >> I would like to re-initiate the voting process for KIP-50: Move

[jira] [Updated] (KAFKA-3627) New consumer doesn't run delayed tasks while under load

[ https://issues.apache.org/jira/browse/KAFKA-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3627: --- Priority: Critical (was: Major) > New consumer doesn't run delayed tasks while under load >

[jira] [Updated] (KAFKA-3627) New consumer doesn't run delayed tasks while under load

[ https://issues.apache.org/jira/browse/KAFKA-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3627: --- Fix Version/s: 0.10.0.0 > New consumer doesn't run delayed tasks while under load >

Re: [VOTE] KIP-47 - Add timestamp-based log deletion policy

Thanks Bill. Read through the KIP, LGTM overall. One clarification question: With this KIP the LogManager's cleanup logic would be, for each segment 1) delete the segment if its last timestamp is < current timstamp - log.retention.time (ms, minutes, hours, etc). 2) delete the segment if its

Re: [VOTE] 0.10.0.0 RC2

We had a blocking issue on the release ( https://github.com/apache/kafka/pull/1302 unfortunately only easily noticed after packaging). So we'll need another RC. https://issues.apache.org/jira/browse/KAFKA-3627 was also raised, which I think should probably also be a blocker as it affects liveness

[jira] [Commented] (KAFKA-3640) Reduce the latency of topic metadata requests

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

[GitHub] kafka pull request: KAFKA-3640: Reduce the latency of topic metada...

GitHub user fpj opened a pull request: https://github.com/apache/kafka/pull/1303 KAFKA-3640: Reduce the latency of topic metadata requests Changes based on KAFKA-2073 to reduce the latency of metadata requests. You can merge this pull request into a Git repository by running: