[jira] [Commented] (KAFKA-4414) Unexpected "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15669513#comment-15669513 ] huxi commented on KAFKA-4414: - Could you reproduce the issue if setting a smaller value for

[GitHub] kafka pull request #2141: KAFKA-4415; Reduce time to create and send Metadat...

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/2141 KAFKA-4415; Reduce time to create and send MetadataUpdateRequest You can merge this pull request into a Git repository by running: $ git pull https://github.com/lindong28/kafka KAFKA-4415

[jira] [Commented] (KAFKA-4415) Reduce time to create and send MetadataUpdateRequest

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

[jira] [Created] (KAFKA-4415) Reduce time to create and send MetadataUpdateRequest

Dong Lin created KAFKA-4415: --- Summary: Reduce time to create and send MetadataUpdateRequest Key: KAFKA-4415 URL: https://issues.apache.org/jira/browse/KAFKA-4415 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-4390) Replace MessageSet usage with client-side equivalents

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

[GitHub] kafka pull request #2140: KAFKA-4390: Replace MessageSet usage with client-s...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/2140 KAFKA-4390: Replace MessageSet usage with client-side alternatives You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA4390

[jira] [Commented] (KAFKA-4391) On Windows, Kafka server stops with uncaught exception after coming back from sleep

[ https://issues.apache.org/jira/browse/KAFKA-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15669074#comment-15669074 ] huxi commented on KAFKA-4391: - If we focus on the renameTo issue, that's an infamous issue on Windows

[jira] [Commented] (KAFKA-4161) Decouple flush and offset commits

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

[GitHub] kafka pull request #2139: KAFKA-4161: KIP-89: Allow sink connectors to decou...

GitHub user shikhar opened a pull request: https://github.com/apache/kafka/pull/2139 KAFKA-4161: KIP-89: Allow sink connectors to decouple flush and offset commit You can merge this pull request into a Git repository by running: $ git pull https://github.com/shikhar/kafka

[jira] [Commented] (KAFKA-4331) Kafka Streams resetter is slow because it joins the same group for each topic

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

[GitHub] kafka pull request #2138: KAFKA-4331: Kafka Streams resetter is slow because...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2138 KAFKA-4331: Kafka Streams resetter is slow because it joins the same group for each topic - bug-fix follow up - Resetter fails if no intermediate topic is used because seekToEnd() commit ALL

[jira] [Updated] (KAFKA-4414) Unexpected "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Meyer Kizner updated KAFKA-4414: Description: Our Kafka installation runs with unclean leader election disabled, so brokers halt

[jira] [Created] (KAFKA-4414) Unexpected "Halting because log truncation is not allowed"

Meyer Kizner created KAFKA-4414: --- Summary: Unexpected "Halting because log truncation is not allowed" Key: KAFKA-4414 URL: https://issues.apache.org/jira/browse/KAFKA-4414 Project: Kafka Issue

[jira] [Updated] (KAFKA-4413) Kakfa should support default SSLContext

[ https://issues.apache.org/jira/browse/KAFKA-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenjie Zhang updated KAFKA-4413: Description: Currently, to enable SSL in either consumer or producer, we have to provide trustStore

[jira] [Created] (KAFKA-4413) Kakfa should support default SSLContext

Wenjie Zhang created KAFKA-4413: --- Summary: Kakfa should support default SSLContext Key: KAFKA-4413 URL: https://issues.apache.org/jira/browse/KAFKA-4413 Project: Kafka Issue Type: Improvement

Re: [DISCUSS] KIP 88: OffsetFetch Protocol Update

Hi Jason, I updated the KIP one more time to make use of AdminClient to access the updated API. I made a note of the previous two versions of the KIP under "Rejected Alternatives". Thanks. --Vahid From: Vahid S Hashemian/Silicon Valley/IBM@IBMUS To: dev@kafka.apache.org Date:

[jira] [Commented] (KAFKA-4396) Seeing offsets not resetting even when reset policy is configured explicitly

[ https://issues.apache.org/jira/browse/KAFKA-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668217#comment-15668217 ] Justin Miller commented on KAFKA-4396: -- Any updates on this? Thanks! > Seeing offsets not resetting

Re: [VOTE] KIP-84: Support SASL SCRAM mechanisms

Radai, I don't have a strong objection to using a more verbose format. But the reasons for choosing the cryptic s=,t=,... format: 1. Unlike other properties like quotas stored in Zookeeper which need to be human readable in order to query the values, these values only need to be parsed

[jira] [Commented] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668010#comment-15668010 ] Todd Palino commented on KAFKA-3959: As noted, I just want the config enforced. If RF=3 is configured,

[jira] [Created] (KAFKA-4412) Replication fetch stuck in loop on offset null

Xavier Lange created KAFKA-4412: --- Summary: Replication fetch stuck in loop on offset null Key: KAFKA-4412 URL: https://issues.apache.org/jira/browse/KAFKA-4412 Project: Kafka Issue Type: Bug

Re: [VOTE] KIP-84: Support SASL SCRAM mechanisms

+1 On Mon, Nov 14, 2016 at 5:57 AM, Rajini Sivaram wrote: > Hi all, > > I would like to initiate the voting process for *KIP-84: Support SASL/SCRAM > mechanisms*: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-84%3A+Support+SASL+SCRAM+mechanisms > > This

Re: [VOTE] KIP-84: Support SASL SCRAM mechanisms

+1 (non-binding) -- Edoardo Comar IBM MessageHub eco...@uk.ibm.com IBM UK Ltd, Hursley Park, SO21 2JN IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6

[jira] [Comment Edited] (KAFKA-559) Garbage collect old consumer metadata entries

[ https://issues.apache.org/jira/browse/KAFKA-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667548#comment-15667548 ] tony mancill edited comment on KAFKA-559 at 11/15/16 5:20 PM: -- Hi [~ewencp].

Re: [VOTE] KIP-84: Support SASL SCRAM mechanisms

small nitpick - given that s,t,k and i are used as part of a rather large CSV format, what is the gain in having them be single letter aliases? in other words - why not salt=... , serverKey=... , storedKey=... , iterations=... ? On Tue, Nov 15, 2016 at 7:26 AM, Mickael Maison

[jira] [Commented] (KAFKA-4406) Add support for custom Java Security Providers in configuration

[ https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667577#comment-15667577 ] Rajini Sivaram commented on KAFKA-4406: --- The PR adds the new configuration to clients, so I had

[jira] [Commented] (KAFKA-559) Garbage collect old consumer metadata entries

[ https://issues.apache.org/jira/browse/KAFKA-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667548#comment-15667548 ] tony mancill commented on KAFKA-559: Hi [~ewencp]. The attachment

[jira] [Resolved] (KAFKA-1933) Fine-grained locking in log append

[ https://issues.apache.org/jira/browse/KAFKA-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Ivanov resolved KAFKA-1933. - Resolution: Won't Fix This patch is not relevant anymore as Kafka finally matured enough to not

[jira] [Commented] (KAFKA-4406) Add support for custom Java Security Providers in configuration

[ https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667481#comment-15667481 ] Magnus Reftel commented on KAFKA-4406: -- For client applications, I agree that it is better to just

[jira] [Created] (KAFKA-4411) broker don't have access to kafka zookeeper nodes

Mohammed amine GARMES created KAFKA-4411: Summary: broker don't have access to kafka zookeeper nodes Key: KAFKA-4411 URL: https://issues.apache.org/jira/browse/KAFKA-4411 Project: Kafka

[jira] [Issue Comment Deleted] (KAFKA-3469) kafka-topics lock down znodes with user principal when zk security is enabled.

[ https://issues.apache.org/jira/browse/KAFKA-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammed amine GARMES updated KAFKA-3469: - Comment: was deleted (was: Hello, I spent much time with this problem before I

Re: [VOTE] KIP-84: Support SASL SCRAM mechanisms

+1 On Tue, Nov 15, 2016 at 10:57 AM, Rajini Sivaram wrote: > Jun, > > Thank you, I have made the updates to the KIP. > > On Tue, Nov 15, 2016 at 12:34 AM, Jun Rao wrote: > >> Hi, Rajini, >> >> Thanks for the proposal. +1. A few minor comments. >>

RE: Kafka 0.10 Monitoring tool

Thank you Otis for your reply. Kafka Manger does not work during the high load, it shows the timeout and Burrow and KafkaOffsetMonitor does not return the group names properly even during the load. SPM is not an open source, so do you have anything opensource that works in Kafka 0.10 version?

[GitHub] kafka pull request #2041: MINOR: Clarify how to fix conversion issues when p...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2041 --- 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-4407) Java consumer does not always send LEAVE_GROUP request during shut down

[ https://issues.apache.org/jira/browse/KAFKA-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor resolved KAFKA-4407. - Resolution: Duplicate Sorry for the duplicate, I'm closing this one. > Java consumer does not always send

[jira] [Commented] (KAFKA-4407) Java consumer does not always send LEAVE_GROUP request during shut down

[ https://issues.apache.org/jira/browse/KAFKA-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667173#comment-15667173 ] Rajini Sivaram commented on KAFKA-4407: --- KAFKA-3703 (PR https://github.com/apache/kafka/pull/1836)

[jira] [Work started] (KAFKA-1548) Refactor the "replica_id" in requests

[ https://issues.apache.org/jira/browse/KAFKA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-1548 started by Balint Molnar. > Refactor the "replica_id" in requests > -

[jira] [Commented] (KAFKA-1548) Refactor the "replica_id" in requests

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

[jira] [Assigned] (KAFKA-1548) Refactor the "replica_id" in requests

[ https://issues.apache.org/jira/browse/KAFKA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balint Molnar reassigned KAFKA-1548: Assignee: Balint Molnar (was: Gwen Shapira) > Refactor the "replica_id" in requests >

[GitHub] kafka pull request #2137: KAFKA-1548 Refactor the "replica_id" in requests

GitHub user baluchicken opened a pull request: https://github.com/apache/kafka/pull/2137 KAFKA-1548 Refactor the "replica_id" in requests You can merge this pull request into a Git repository by running: $ git pull https://github.com/baluchicken/kafka-1 KAFKA-1548

[jira] [Commented] (KAFKA-4406) Add support for custom Java Security Providers in configuration

[ https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15666982#comment-15666982 ] Ismael Juma commented on KAFKA-4406: [~rsivaram] beat me to it. I share the concern about setting a

[jira] [Commented] (KAFKA-4406) Add support for custom Java Security Providers in configuration

[ https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15666957#comment-15666957 ] Rajini Sivaram commented on KAFKA-4406: --- [~magnus.reftel] You will need to create a [Kafka

[GitHub] kafka pull request #2136: MINOR: Remove unused code

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2136 MINOR: Remove unused code You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka remove-unused-code Alternatively you can review and apply

[GitHub] kafka pull request #2135: KAFKA-3637: Added initial states

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2135 KAFKA-3637: Added initial states You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka KAFKA-3637-streams-state Alternatively

[jira] [Commented] (KAFKA-3637) Add method that checks if streams are initialised

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

Re: [DISCUSS] KIP-87 - Add Compaction Tombstone Flag

Hi Renu, Technically speaking we may not need to bump up the magic value. A tombstone is a message either with tombstone bit set OR with a null value.(once all the clients has been upgraded, it automatically becomes only based on tombstone) However, this leads to a few subtle issues. 1.

[jira] [Updated] (KAFKA-4406) Add support for custom Java Security Providers in configuration

[ https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Reftel updated KAFKA-4406: - Status: Patch Available (was: Open) https://github.com/apache/kafka/pull/2134 > Add support for

[jira] [Issue Comment Deleted] (KAFKA-4406) Add support for custom Java Security Providers in configuration

[ https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Reftel updated KAFKA-4406: - Comment: was deleted (was: https://github.com/apache/kafka/pull/2134) > Add support for custom

[jira] [Commented] (KAFKA-4406) Add support for custom Java Security Providers in configuration

[ https://issues.apache.org/jira/browse/KAFKA-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15666899#comment-15666899 ] Magnus Reftel commented on KAFKA-4406: -- https://github.com/apache/kafka/pull/2134 > Add support for

[GitHub] kafka pull request #2134: config: add ssl.provider.classes config option

GitHub user reftel opened a pull request: https://github.com/apache/kafka/pull/2134 config: add ssl.provider.classes config option You can merge this pull request into a Git repository by running: $ git pull https://github.com/reftel/kafka feature/security_providers_config

Re: [VOTE] KIP-84: Support SASL SCRAM mechanisms

Jun, Thank you, I have made the updates to the KIP. On Tue, Nov 15, 2016 at 12:34 AM, Jun Rao wrote: > Hi, Rajini, > > Thanks for the proposal. +1. A few minor comments. > > 30. Could you add that the broker config sasl.enabled.mechanisms can now > take more values? > > 31.

[jira] [Updated] (KAFKA-3637) Add method that checks if streams are initialised

[ https://issues.apache.org/jira/browse/KAFKA-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3637: Fix Version/s: 0.10.2.0 > Add method that checks if streams are initialised >

[jira] [Updated] (KAFKA-3637) Add method that checks if streams are initialised

[ https://issues.apache.org/jira/browse/KAFKA-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3637: Issue Type: Improvement (was: Sub-task) Parent: (was: KAFKA-2590) > Add method that

[jira] [Commented] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted

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

[GitHub] kafka pull request #2133: KAFKA-4355: Skip topics that have no partitions

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2133 KAFKA-4355: Skip topics that have no partitions You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka

[jira] [Updated] (KAFKA-4410) KafkaController sends double the expected number of StopReplicaRequests during controlled shutdown

[ https://issues.apache.org/jira/browse/KAFKA-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-4410: Description: We expect KafkaController to send the broker undergoing controlled shutdown one

[jira] [Commented] (KAFKA-4410) KafkaController sends double the expected number of StopReplicaRequests during controlled shutdown

[ https://issues.apache.org/jira/browse/KAFKA-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15666555#comment-15666555 ] Onur Karaman commented on KAFKA-4410: - To reproduce the bug, spin up zookeeper and two kafka brokers:

[jira] [Created] (KAFKA-4410) KafkaController sends double the expected number of StopReplicaRequests during controlled shutdown

Onur Karaman created KAFKA-4410: --- Summary: KafkaController sends double the expected number of StopReplicaRequests during controlled shutdown Key: KAFKA-4410 URL: https://issues.apache.org/jira/browse/KAFKA-4410