[jira] [Comment Edited] (KAFKA-4271) The console consumer fails on Windows with new consumer is used

[ https://issues.apache.org/jira/browse/KAFKA-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15704074#comment-15704074 ] Yu Yan edited comment on KAFKA-4271 at 11/29/16 7:53 AM: - I have met this problem

[jira] [Commented] (KAFKA-4458) Add per partition metrics for in-sync and assigned replica count

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

[GitHub] kafka pull request #2186: KAFKA-4458 add per partition in-sync and assigned ...

GitHub user xvrl opened a pull request: https://github.com/apache/kafka/pull/2186 KAFKA-4458 add per partition in-sync and assigned replica count You can merge this pull request into a Git repository by running: $ git pull https://github.com/xvrl/kafka

[jira] [Comment Edited] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15704164#comment-15704164 ] Abhi edited comment on KAFKA-1194 at 11/29/16 4:38 AM: --- Let me give a try... Little

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15704164#comment-15704164 ] Abhi commented on KAFKA-1194: - Let give a try... Little equipped at my end.. But I will definitely test the

[jira] [Work started] (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:all-tabpanel ] Work on KAFKA-3959 started by Onur Karaman. --- > __consumer_offsets wrong number of replicas at startup >

[jira] [Updated] (KAFKA-4453) add request prioritization

[ https://issues.apache.org/jira/browse/KAFKA-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-4453: Status: Patch Available (was: In Progress) > add request prioritization >

[jira] [Updated] (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:all-tabpanel ] Onur Karaman updated KAFKA-3959: Status: Patch Available (was: In Progress) > __consumer_offsets wrong number of replicas at

[jira] [Work started] (KAFKA-4453) add request prioritization

[ https://issues.apache.org/jira/browse/KAFKA-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4453 started by Onur Karaman. --- > add request prioritization > -- > > Key:

[jira] [Commented] (KAFKA-4271) The console consumer fails on Windows with new consumer is used

[ https://issues.apache.org/jira/browse/KAFKA-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15704074#comment-15704074 ] Yu Yan commented on KAFKA-4271: --- I have met this problem too. My jvm is 32 bit, and 64jvm may work well. But

[GitHub] kafka-site pull request #33: Update contact.html

GitHub user dossett opened a pull request: https://github.com/apache/kafka-site/pull/33 Update contact.html Update link to search-hadoop.com You can merge this pull request into a Git repository by running: $ git pull https://github.com/dossett/kafka-site patch-1

[jira] [Commented] (KAFKA-4444) Aggregate requests sent from controller to broker during controlled shutdown

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

[GitHub] kafka pull request #2141: KAFKA-4444; Aggregate requests sent from controlle...

Github user lindong28 closed the pull request at: https://github.com/apache/kafka/pull/2141 --- 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-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

[ https://issues.apache.org/jira/browse/KAFKA-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703758#comment-15703758 ] Mayuresh Gharat commented on KAFKA-4454: [~ijuma] [~jjkoshy] [~ashishsinghdev] [~parth.brahmbhatt]

[GitHub] kafka pull request #2185: MINOR: added logging to debug test

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2185 MINOR: added logging to debug test You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka hotfixResetToolTest Alternatively you can review

[jira] [Updated] (KAFKA-3715) Higher granularity streams metrics

[ https://issues.apache.org/jira/browse/KAFKA-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] aarti gupta updated KAFKA-3715: --- Assignee: Eno Thereska (was: aarti gupta) > Higher granularity streams metrics >

[jira] [Commented] (KAFKA-3715) Higher granularity streams metrics

[ https://issues.apache.org/jira/browse/KAFKA-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703705#comment-15703705 ] aarti gupta commented on KAFKA-3715: [~enothereska] go for it! > Higher granularity streams metrics

[DISCUSS] KIP-96 - Add per partition metrics for in-sync and assigned replica count

Hi, I created KIP-96 to propose per partition in-sync / assigned replica metrics. Should be straightforward, but submitting it for proposal since we require it for metrics changes. Here's the link to the KIP:

[jira] [Commented] (KAFKA-4039) Exit Strategy: using exceptions instead of inline invocation of exit/halt

[ https://issues.apache.org/jira/browse/KAFKA-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703697#comment-15703697 ] Guozhang Wang commented on KAFKA-4039: -- Ping [~hachikuji] [~ijuma] again. > Exit Strategy: using

[jira] [Commented] (KAFKA-4039) Exit Strategy: using exceptions instead of inline invocation of exit/halt

[ https://issues.apache.org/jira/browse/KAFKA-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703696#comment-15703696 ] Guozhang Wang commented on KAFKA-4039: -- Ping [~hachikuji] [~ijuma] again. > Exit Strategy: using

[jira] [Updated] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

[ https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4399: - Assignee: Alexey Ozeritskiy > Deadlock between cleanupGroupMetadata and offset commit >

[jira] [Issue Comment Deleted] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Json Tu updated KAFKA-4447: --- Comment: was deleted (was: [~wangg...@gmail.com] thank you for such a detailed analysis . as you

[jira] [Commented] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703688#comment-15703688 ] Json Tu commented on KAFKA-4447: [~wangg...@gmail.com] thank you for such a detailed analysis . as you

[jira] [Commented] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703687#comment-15703687 ] Json Tu commented on KAFKA-4447: [~wangg...@gmail.com] thank you for such a detailed analysis . as you

[jira] [Commented] (KAFKA-4436) Provide builder pattern for StreamsConfig

[ https://issues.apache.org/jira/browse/KAFKA-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703682#comment-15703682 ] Xavier Léauté commented on KAFKA-4436: -- [~gwenshap] One of the difference I see between configuring

[jira] [Updated] (KAFKA-4442) Controller should grab lock when it is being initialized to avoid race condition

[ https://issues.apache.org/jira/browse/KAFKA-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-4442: Description: Currently controller will register broker change listener before sending send

[jira] [Created] (KAFKA-4458) Add per partition metrics for in-sync and assigned replica count

Xavier Léauté created KAFKA-4458: Summary: Add per partition metrics for in-sync and assigned replica count Key: KAFKA-4458 URL: https://issues.apache.org/jira/browse/KAFKA-4458 Project: Kafka

[jira] [Commented] (KAFKA-4436) Provide builder pattern for StreamsConfig

[ https://issues.apache.org/jira/browse/KAFKA-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703620#comment-15703620 ] Matthias J. Sax commented on KAFKA-4436: bq. One of the goals in making KafkaStreams part of

[jira] [Assigned] (KAFKA-4439) Add a builder to NetworkClient

[ https://issues.apache.org/jira/browse/KAFKA-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe reassigned KAFKA-4439: -- Assignee: Colin P. McCabe > Add a builder to NetworkClient >

[jira] [Assigned] (KAFKA-4457) Add a command to list the broker version information

[ https://issues.apache.org/jira/browse/KAFKA-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe reassigned KAFKA-4457: -- Assignee: Colin P. McCabe > Add a command to list the broker version information >

Kafka Clients Survey

Hey Kafka Community, I'm trying to take a pulse on the current state of the Kafka clients ecosystem. Which languages are most popular in our community? What does the community value in clients? You can help me out by filling in the survey: https://goo.gl/forms/cZg1CJyf1PuqivTg2 I will lock the

[jira] [Commented] (KAFKA-4457) Add a command to list the broker version information

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

[GitHub] kafka pull request #2184: KAFKA-4457. Add BrokerVersionCommand

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2184 KAFKA-4457. Add BrokerVersionCommand You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-4457 Alternatively you can review and

[jira] [Commented] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

[ https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703435#comment-15703435 ] Guozhang Wang commented on KAFKA-4399: -- Ping [~hachikuji] [~ijuma] again. > Deadlock between

[jira] [Created] (KAFKA-4457) Add a command to list the broker version information

Colin P. McCabe created KAFKA-4457: -- Summary: Add a command to list the broker version information Key: KAFKA-4457 URL: https://issues.apache.org/jira/browse/KAFKA-4457 Project: Kafka Issue

[GitHub] kafka pull request #2183: Removed obsolete parameter form example config in ...

GitHub user soenkeliebau opened a pull request: https://github.com/apache/kafka/pull/2183 Removed obsolete parameter form example config in docs. Parameter controller.message.queue.size was removed in 0.9 (KAFKA-2122) but is still listed in an example broker configuration in the

[jira] [Commented] (KAFKA-2122) Remove controller.message.queue.size Config

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

[jira] [Commented] (KAFKA-4450) Add missing 0.10.1.x upgrade tests and ensure ongoing compatibility checks

[ https://issues.apache.org/jira/browse/KAFKA-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703349#comment-15703349 ] Guozhang Wang commented on KAFKA-4450: -- [~ewencp] [~ijuma] What's the status of this JIRA ticket? >

[jira] [Updated] (KAFKA-4450) Add missing 0.10.1.x upgrade tests and ensure ongoing compatibility checks

[ https://issues.apache.org/jira/browse/KAFKA-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4450: - Fix Version/s: (was: 0.11.0.0) > Add missing 0.10.1.x upgrade tests and ensure ongoing

[jira] [Commented] (KAFKA-4436) Provide builder pattern for StreamsConfig

[ https://issues.apache.org/jira/browse/KAFKA-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703313#comment-15703313 ] Gwen Shapira commented on KAFKA-4436: - One of the goals in making KafkaStreams part of Apache Kafka

[jira] [Updated] (KAFKA-4455) Commit during rebalance does not close RocksDB which later causes: org.rocksdb.RocksDBException: IO error: lock .../LOCK: No locks available

[ https://issues.apache.org/jira/browse/KAFKA-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davor Poldrugo updated KAFKA-4455: -- Description: h2. Problem description >From time to time a rebalance in Kafka Streams causes the

[jira] [Updated] (KAFKA-4455) Commit during rebalance does not close RocksDB which later causes: org.rocksdb.RocksDBException: IO error: lock .../LOCK: No locks available

[ https://issues.apache.org/jira/browse/KAFKA-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davor Poldrugo updated KAFKA-4455: -- Description: h2. Problem description >From time to time a rebalance in Kafka Streams causes the

[jira] [Work started] (KAFKA-4437) Incremental Batch Processing for Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4437 started by Matthias J. Sax. -- > Incremental Batch Processing for Kafka Streams >

Re: Data (re)processing with Kafka (new wiki page)

Thanks for your input! For (2), there is currently KafkaStream.toString(). You could theoretically parse the String to extract all required information -- of course, this is not a nice solution. -Matthias On 11/25/16 2:11 AM, saiprasad mishra wrote: > This page is really helpful.Thanks for

Re: [DISCUSS] 0.10.1.1 Plan

Getting out 0.10.1.1 quickly makes a lot of sense so perhaps the answer to the quality concern is to not publish the 2.12 tgz and instead simply publish the artifacts to maven central allowing the scala community to become a part of that quality process. That way when the 0.10.2.0 release

[jira] [Comment Edited] (KAFKA-3798) Kafka Consumer 0.10.0.0 killed after rebalancing exception

[ https://issues.apache.org/jira/browse/KAFKA-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703193#comment-15703193 ] Evan Nelson edited comment on KAFKA-3798 at 11/28/16 9:34 PM: -- We are

[jira] [Comment Edited] (KAFKA-3798) Kafka Consumer 0.10.0.0 killed after rebalancing exception

[ https://issues.apache.org/jira/browse/KAFKA-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703193#comment-15703193 ] Evan Nelson edited comment on KAFKA-3798 at 11/28/16 9:34 PM: -- We are

[jira] [Commented] (KAFKA-3798) Kafka Consumer 0.10.0.0 killed after rebalancing exception

[ https://issues.apache.org/jira/browse/KAFKA-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703193#comment-15703193 ] Evan Nelson commented on KAFKA-3798: We are experiencing the same issue with 0.8.2.2:

[jira] [Updated] (KAFKA-4455) Commit during rebalance does not close RocksDB which later causes: org.rocksdb.RocksDBException: IO error: lock .../LOCK: No locks available

[ https://issues.apache.org/jira/browse/KAFKA-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davor Poldrugo updated KAFKA-4455: -- Description: h2. Problem description >From time to time a rebalance in Kafka Streams causes the

[jira] [Updated] (KAFKA-4455) Commit during rebalance does not close RocksDB which later causes: org.rocksdb.RocksDBException: IO error: lock .../LOCK: No locks available

[ https://issues.apache.org/jira/browse/KAFKA-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davor Poldrugo updated KAFKA-4455: -- Description: h2. Problem description >From time to time a rebalance in Kafka Streams causes the

[jira] [Created] (KAFKA-4456) Offsets of deleted topics are not removed from consumer groups

Vahid Hashemian created KAFKA-4456: -- Summary: Offsets of deleted topics are not removed from consumer groups Key: KAFKA-4456 URL: https://issues.apache.org/jira/browse/KAFKA-4456 Project: Kafka

[jira] [Updated] (KAFKA-4455) Commit during rebalance does not close RocksDB which later causes: org.rocksdb.RocksDBException: IO error: lock .../LOCK: No locks available

[ https://issues.apache.org/jira/browse/KAFKA-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davor Poldrugo updated KAFKA-4455: -- Description: h2. Problem description >From time to time a rebalance in Kafka Streams causes the

[jira] [Updated] (KAFKA-4455) Commit during rebalance does not close RocksDB which later causes: org.rocksdb.RocksDBException: IO error: lock .../LOCK: No locks available

[ https://issues.apache.org/jira/browse/KAFKA-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davor Poldrugo updated KAFKA-4455: -- Attachment: RocksDBException_IO-error_stacktrace.txt > Commit during rebalance does not close

[jira] [Created] (KAFKA-4455) Commit during rebalance does not close RocksDB which later causes: org.rocksdb.RocksDBException: IO error: lock .../LOCK: No locks available

Davor Poldrugo created KAFKA-4455: - Summary: Commit during rebalance does not close RocksDB which later causes: org.rocksdb.RocksDBException: IO error: lock .../LOCK: No locks available Key: KAFKA-4455 URL:

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702991#comment-15702991 ] Soumyajit Sahu commented on KAFKA-1194: --- [~abhit011], [~bradvido] Could you please give the

[jira] [Created] (KAFKA-4454) Authorizer should also include the Principal generated by the PrincipalBuilder.

Mayuresh Gharat created KAFKA-4454: -- Summary: Authorizer should also include the Principal generated by the PrincipalBuilder. Key: KAFKA-4454 URL: https://issues.apache.org/jira/browse/KAFKA-4454

[GitHub] kafka pull request #2182: ConfigDef experimentation - support List and Ma...

GitHub user shikhar opened a pull request: https://github.com/apache/kafka/pull/2182 ConfigDef experimentation - support List and Map You can merge this pull request into a Git repository by running: $ git pull https://github.com/shikhar/kafka

Re: any plans to switch to java 8?

By supporting two Java versions, I mean supporting the two most recent ones. So, we'd only drop support for Java 7 after Java 9 is released, but no sooner (independently of how old or unsupported a particular version is). An alternative approach is to drop support a defined amount of time after a

Re: [DISCUSS] 0.10.1.1 Plan

@Radai I think Ismael's point is that people who coded their applications against 0.10.1.1 should be able to swipe in the 0.10.1.0 jar without breaking the code (in practice maybe it is more likely the reverse scenario, that people coded against 0.10.1.0 and trying to swipe in a newer 0.10.1.1).

[jira] [Commented] (KAFKA-4453) add request prioritization

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

[GitHub] kafka pull request #2181: KAFKA-4453: add request prioritization

GitHub user onurkaraman opened a pull request: https://github.com/apache/kafka/pull/2181 KAFKA-4453: add request prioritization Today all requests (client requests, broker requests, controller requests) to a broker are put into the same queue. They all have the same priority. So a

[jira] [Created] (KAFKA-4453) add request prioritization

Onur Karaman created KAFKA-4453: --- Summary: add request prioritization Key: KAFKA-4453 URL: https://issues.apache.org/jira/browse/KAFKA-4453 Project: Kafka Issue Type: Bug Reporter:

[DISCUSS] KIP-95: Incremental Batch Processing for Kafka Streams

Hi all, I want to start a discussion about KIP-95: https://cwiki.apache.org/confluence/display/KAFKA/KIP-95%3A+Incremental+Batch+Processing+for+Kafka+Streams Looking forward to your feedback. -Matthias signature.asc Description: OpenPGP digital signature

Re: [DISCUSS] KIP-93: Improve invalid timestamp handling in Kafka Streams

Done. If there is no further comments, I would like to start a voting thread in a separate email. -Matthias On 11/28/16 9:08 AM, Guozhang Wang wrote: > Yes it does not include these, again in my previous previous email I meant > when you say "This is a breaking, incompatible change" people may

Re: any plans to switch to java 8?

i dont completely understand the meaning behind supporting 2 java versions. given java's pretty good about backwards compatibility if you build against the oldest JDK you support (say 8) it should run on anything newer (say 9). what am i missing? On Mon, Nov 28, 2016 at 4:06 AM, Ismael Juma

Re: [VOTE] KIP-72 - Allow putting a bound on memory consumed by Incoming requests

will do (only added a single one so far, the rest TBD) On Mon, Nov 28, 2016 at 10:04 AM, Jun Rao wrote: > Hi, Radai, > > Could you add a high level description of the newly added metrics to the > KIP wiki? > > Thanks, > > Jun > > On Wed, Nov 23, 2016 at 3:45 PM, radai

[jira] [Updated] (KAFKA-4452) Server segfault in ContiguousSpace::block_size

[ https://issues.apache.org/jira/browse/KAFKA-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Rodgers updated KAFKA-4452: - Environment: JVM: java version "1.8.0_31" Java(TM) SE Runtime Environment (build 1.8.0_31-b13)

[jira] [Updated] (KAFKA-4452) Server segfault in ContiguousSpace::block_size

[ https://issues.apache.org/jira/browse/KAFKA-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Rodgers updated KAFKA-4452: - Description: Kafka server received SIGABRT and emitted this segfault message: {noformat} # # A

[jira] [Created] (KAFKA-4452) Server segfault in ContiguousSpace::block_size

Grant Rodgers created KAFKA-4452: Summary: Server segfault in ContiguousSpace::block_size Key: KAFKA-4452 URL: https://issues.apache.org/jira/browse/KAFKA-4452 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-4451) Recovering empty replica yields negative offsets in index of compact partitions

[ https://issues.apache.org/jira/browse/KAFKA-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Schiff updated KAFKA-4451: -- Fix Version/s: (was: 0.9.0.1) > Recovering empty replica yields negative offsets in index

[jira] [Updated] (KAFKA-4451) Recovering empty replica yields negative offsets in index of compact partitions

[ https://issues.apache.org/jira/browse/KAFKA-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Schiff updated KAFKA-4451: -- Affects Version/s: 0.9.0.1 > Recovering empty replica yields negative offsets in index of

Re: [VOTE] KIP-72 - Allow putting a bound on memory consumed by Incoming requests

Hi, Radai, Could you add a high level description of the newly added metrics to the KIP wiki? Thanks, Jun On Wed, Nov 23, 2016 at 3:45 PM, radai wrote: > Hi Jun, > > I've added the sensor you requested (or at least I think I did ) > > On Fri, Nov 18, 2016 at

[jira] [Commented] (KAFKA-4439) Add a builder to NetworkClient

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

[jira] [Commented] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702635#comment-15702635 ] Guozhang Wang commented on KAFKA-4447: -- My two cents here: 1. ZkClient's causing our listener

[GitHub] kafka pull request #2180: KAFKA-4439: NetworkClient: create a builder class ...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2180 KAFKA-4439: NetworkClient: create a builder class to encapsulate ctor arguments You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka

Re: [DISCUSS] KIP-93: Improve invalid timestamp handling in Kafka Streams

Yes it does not include these, again in my previous previous email I meant when you say "This is a breaking, incompatible change" people may interpret it differently. So better explain it more clearly. Guozhang On Thu, Nov 24, 2016 at 10:31 PM, Matthias J. Sax wrote: >

Re: How to commit bug fix to kafka mesos framework

If the bug is in Kafka, here is the process for submitting a fix: http://kafka.apache.org/contributing If the bug is in the mesos-kafka framework, I think you should look up that project and find out how to commit a bugfix there. I think it should not be more complicated than submitting a PR.

Re: A strange controller log in Kafka 0.9.0.1

thanks to Jason Gustafson, hope more contributor can take part in this discussion. https://issues.apache.org/jira/browse/KAFKA-4447 > 在 2016年11月27日，下午9:20，Json Tu 写道： > > AnyBody？This is very disconcerting! If convenient,

[jira] [Commented] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702465#comment-15702465 ] Json Tu commented on KAFKA-4447: may be the phenomenon of these listener is the same as one zk's callback

[jira] [Comment Edited] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702384#comment-15702384 ] Json Tu edited comment on KAFKA-4447 at 11/28/16 4:45 PM: -- [~skarface] thanks for

[jira] [Comment Edited] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702384#comment-15702384 ] Json Tu edited comment on KAFKA-4447 at 11/28/16 4:44 PM: -- [~skarface] thanks for

[GitHub] kafka pull request #2179: MINOR: Fix typos in KafkaConsumer docs

GitHub user jeffwidman opened a pull request: https://github.com/apache/kafka/pull/2179 MINOR: Fix typos in KafkaConsumer docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/jeffwidman/kafka patch-2 Alternatively you can

[jira] [Issue Comment Deleted] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Json Tu updated KAFKA-4447: --- Comment: was deleted (was: [~skarface] thanks for your reply. the latest release version

[jira] [Comment Edited] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702384#comment-15702384 ] Json Tu edited comment on KAFKA-4447 at 11/28/16 4:26 PM: -- [~skarface] thanks for

[jira] [Commented] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702383#comment-15702383 ] Json Tu commented on KAFKA-4447: [~skarface] thanks for your reply. the latest release version

[jira] [Commented] (KAFKA-4447) Controller resigned but it also acts as a controller for a long time

[ https://issues.apache.org/jira/browse/KAFKA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702384#comment-15702384 ] Json Tu commented on KAFKA-4447: [~skarface] thanks for your reply. the latest release version

[GitHub] kafka pull request #2178: Minor: Fix typos in KafkaConsumer docs

GitHub user jeffwidman opened a pull request: https://github.com/apache/kafka/pull/2178 Minor: Fix typos in KafkaConsumer docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/jeffwidman/kafka patch-1 Alternatively you can

[jira] [Commented] (KAFKA-4434) KafkaProducer configuration is logged twice

[ https://issues.apache.org/jira/browse/KAFKA-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702321#comment-15702321 ] kevin.chen commented on KAFKA-4434: --- can any one assign this to me? or add me to contributor for kafka

[jira] [Commented] (KAFKA-3715) Higher granularity streams metrics

[ https://issues.apache.org/jira/browse/KAFKA-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702299#comment-15702299 ] Eno Thereska commented on KAFKA-3715: - [~aartigupta] would it be ok if I take a pass or would you be

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

Hi Ismael, Thank you for the review. 1. I think you had asked earlier for SCRAM-SHA-1 to be removed since it is not secure :-) I am happy to add that back in so that clients which don't have access to a more secure algorithm can use it. But it would be a shame to prevent users who only need Java

Re: [VOTE] KIP-85: Dynamic JAAS configuration for Kafka clients

Ismael, Thank you for reviewing the KIP. I do agree that JAAS config format is not ideal. But I wanted to solve the generic configuration issue (need for physical file, single static config) for any SASL mechanism in an extensible, future-proof way. And that requires the ability to configure all

How to commit bug fix to kafka mesos framework

Hi Guys, I found a bug in kafka mesos framework related with support for kafka 0.9.x and later. Now I have a solution to fix the problem. So how could I commit the code to the project? Is there any process about it? And who could help me? Thanks, Jared, (??) Software developer Interested

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

Hi Rajini, Thanks for the KIP. I am in favour of introducing SCRAM as an additional SASL mechanism. A few comments: 1. Magnus raised the point that cyrus-sasl currently only implements SCRAM-SHA-1, so having a larger number of variants will involve more work for non-Java clients. Do we really

Re: [VOTE] KIP-85: Dynamic JAAS configuration for Kafka clients

I'm very late to this, but better late than never, I guess. I am +1 on this because it improves on the status quo, satisfies a real need and is simple to implement. Having said that, I'd also like to state that it's a bit of a shame that we are doubling down on the JAAS config format. It is a

Re: any plans to switch to java 8?

I think there are 3 main points that can be taken from that discussion with regards to the timing: 1. We should do the switch no earlier than Kafka's next major version bump (i.e. 0.11.0.0 at this point) 2. Some would prefer to support two Java versions, so we'd have to wait until Kafka's next

Re: [VOTE] KIP-72 - Allow putting a bound on memory consumed by Incoming requests

Thanks for the KIP, +1 from me. I have a few comments with regards to the method names chosen, but since none of the classes in question are public API, I'll comment directly in the PR. Ismael On Mon, Nov 7, 2016 at 9:08 PM, radai wrote: > Hi, > > I would like to

[jira] [Assigned] (KAFKA-3537) Provide access to low-level Metrics in ProcessorContext

[ https://issues.apache.org/jira/browse/KAFKA-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-3537: --- Assignee: Eno Thereska (was: Guozhang Wang) > Provide access to low-level Metrics in

[jira] [Commented] (KAFKA-1194) The kafka broker cannot delete the old log files after the configured time

[ https://issues.apache.org/jira/browse/KAFKA-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15701526#comment-15701526 ] Abhi commented on KAFKA-1194: - [~haraldk] Do you have the build for the same issue. I tried building kafka in

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

Another committer vote is needed for this to go through. Anyone have time to review? Thank you! On Tue, Nov 15, 2016 at 6:26 PM, Gwen Shapira wrote: > +1 > > On Mon, Nov 14, 2016 at 5:57 AM, Rajini Sivaram > wrote: > > Hi all, > > > > I would

[jira] [Updated] (KAFKA-3715) Higher granularity streams metrics

[ https://issues.apache.org/jira/browse/KAFKA-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-3715: Labels: api (was: api newbie) > Higher granularity streams metrics >

  1   2   >