Re: Apache Kafka JIRA Worflow: Add Closed -> Reopen transition

Manikumar, Any reason for this. Before the workflow is to open a new JIRA if a JIRA closed. -Harsha On Fri, May 20, 2016, at 08:54 PM, Manikumar Reddy wrote: > Jun/Ismail, > > I requested Apache Infra to change JIRA workflow to add Closed -> > Reopen >

[jira] [Resolved] (KAFKA-2547) Make DynamicConfigManager to use the ZkNodeChangeNotificationListener introduced as part of KAFKA-2211

[ https://issues.apache.org/jira/browse/KAFKA-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-2547. Resolution: Fixed > Make DynamicConfigManager to use the ZkNodeChangeNotificationListener

[jira] [Updated] (KAFKA-2547) Make DynamicConfigManager to use the ZkNodeChangeNotificationListener introduced as part of KAFKA-2211

[ https://issues.apache.org/jira/browse/KAFKA-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-2547: --- Status: Reopened (was: Closed) > Make DynamicConfigManager to use the

[jira] [Resolved] (KAFKA-3219) Long topic names mess up broker topic state

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-3219. Resolution: Fixed > Long topic names mess up broker topic state >

[jira] [Updated] (KAFKA-3219) Long topic names mess up broker topic state

[ https://issues.apache.org/jira/browse/KAFKA-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-3219: --- Status: Reopened (was: Closed) > Long topic names mess up broker topic state >

Apache Kafka JIRA Worflow: Add Closed -> Reopen transition

Jun/Ismail, I requested Apache Infra to change JIRA workflow to add Closed -> Reopen transition. https://issues.apache.org/jira/browse/INFRA-11857 Let me know, If any concerns Manikumar

[jira] [Resolved] (KAFKA-2800) Update outdated dependencies

[ https://issues.apache.org/jira/browse/KAFKA-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-2800. Resolution: Fixed > Update outdated dependencies > > >

[jira] [Updated] (KAFKA-2800) Update outdated dependencies

[ https://issues.apache.org/jira/browse/KAFKA-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-2800: --- Status: Reopened (was: Closed) > Update outdated dependencies >

Re: KAFKA-3722 : Discussion about custom PrincipalBuilder and Authorizer configs

Mayuresh, Thanks for the write up. With principal builder, the idea is to reuse a single principal builder across all the security protocols where its applicable and given that principal builder has

Re: [VOTE] 0.10.0.0 RC6

+1, verified quickstart with source and binary release. On Saturday, May 21, 2016, Vahid S Hashemian wrote: > +1. I was able to successfully create a topic and run a producer and > consumer against it from the source on Ubuntu 15.04, Mac OS X Yosemite, > and Windows

KAFKA-3722 : Discussion about custom PrincipalBuilder and Authorizer configs

Hi All, I came across an issue with plugging in a custom PrincipalBuilder class using the config "principal.builder.class" along with a custom Authorizer class using the config "authorizer.class.name". Consider the following scenario : For PlainText we don't supply any PrincipalBuilder. For SSL

[jira] [Updated] (KAFKA-3742) Can't run connect-distributed.sh with -daemon flag

[ https://issues.apache.org/jira/browse/KAFKA-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3742: -- Description: Running on ubuntu 14.04. Discovered while experimenting various different kafka

Re: [VOTE] 0.10.0.0 RC6

+1. I was able to successfully create a topic and run a producer and consumer against it from the source on Ubuntu 15.04, Mac OS X Yosemite, and Windows 7. --Vahid From: Dana Powers To: "dev@kafka.apache.org" Date: 05/20/2016 12:13 PM

[jira] [Updated] (KAFKA-3742) Can't run connect-distributed.sh with -daemon flag

[ https://issues.apache.org/jira/browse/KAFKA-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3742: -- Summary: Can't run connect-distributed.sh with -daemon flag (was: Can't run connect-distributed with

[jira] [Updated] (KAFKA-3742) Can't run connect-distributed with -daemon flag

[ https://issues.apache.org/jira/browse/KAFKA-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoff Anderson updated KAFKA-3742: -- Description: Running on ubuntu 14.04. Discovered while experimenting various different kafka

[jira] [Assigned] (KAFKA-3742) Can't run connect-distributed with -daemon flag

[ https://issues.apache.org/jira/browse/KAFKA-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reassigned KAFKA-3742: - Assignee: Liquan Pei > Can't run connect-distributed with -daemon flag >

[jira] [Created] (KAFKA-3742) Can't run connect-distributed with -daemon flag

Geoff Anderson created KAFKA-3742: - Summary: Can't run connect-distributed with -daemon flag Key: KAFKA-3742 URL: https://issues.apache.org/jira/browse/KAFKA-3742 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3740) Add configs for RocksDBStores

[ https://issues.apache.org/jira/browse/KAFKA-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294310#comment-15294310 ] Henry Cai commented on KAFKA-3740: -- Worked now. > Add configs for RocksDBStores >

[jira] [Assigned] (KAFKA-3740) Add configs for RocksDBStores

[ https://issues.apache.org/jira/browse/KAFKA-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henry Cai reassigned KAFKA-3740: Assignee: Henry Cai > Add configs for RocksDBStores > - > >

[jira] [Commented] (KAFKA-3740) Add configs for RocksDBStores

[ https://issues.apache.org/jira/browse/KAFKA-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294302#comment-15294302 ] Guozhang Wang commented on KAFKA-3740: -- That is because you can only assign to yourself, but not

[jira] [Updated] (KAFKA-3741) KStream config for changelog min.in.sync.replicas

[ https://issues.apache.org/jira/browse/KAFKA-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3741: - Labels: api (was: ) > KStream config for changelog min.in.sync.replicas >

[jira] [Created] (KAFKA-3741) KStream config for changelog min.in.sync.replicas

Roger Hoover created KAFKA-3741: --- Summary: KStream config for changelog min.in.sync.replicas Key: KAFKA-3741 URL: https://issues.apache.org/jira/browse/KAFKA-3741 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3740) Add configs for RocksDBStores

[ https://issues.apache.org/jira/browse/KAFKA-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294270#comment-15294270 ] Henry Cai commented on KAFKA-3740: -- Don't see that 'assign' button > Add configs for RocksDBStores >

[jira] [Commented] (KAFKA-742) Existing directories under the Kafka data directory without any data cause process to not start

[ https://issues.apache.org/jira/browse/KAFKA-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294250#comment-15294250 ] David Tucker commented on KAFKA-742: And the "lost+found" issue still exists in Kafka 0.9 even when a

[jira] [Updated] (KAFKA-3735) RocksDB objects needs to be disposed after usage

[ https://issues.apache.org/jira/browse/KAFKA-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3735: - Fix Version/s: (was: 0.10.0.1) 0.10.1.0 > RocksDB objects needs to be

[jira] [Commented] (KAFKA-3740) Add configs for RocksDBStores

[ https://issues.apache.org/jira/browse/KAFKA-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294232#comment-15294232 ] Guozhang Wang commented on KAFKA-3740: -- I have added you to the contributor list, so you should be

[jira] [Commented] (KAFKA-3740) Add configs for RocksDBStores

[ https://issues.apache.org/jira/browse/KAFKA-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294204#comment-15294204 ] Henry Cai commented on KAFKA-3740: -- You can assign this one to me. > Add configs for RocksDBStores >

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

See Changes: [wangguoz] KAFKA-3735: Dispose all RocksObejcts upon completeness -- [...truncated 4026 lines...] kafka.log.LogConfigTest > testKafkaConfigToProps PASSED kafka.log.LogConfigTest >

Re: [VOTE] 0.10.0.0 RC6

+1 -- passed kafka-python integration tests -Dana On Fri, May 20, 2016 at 11:16 AM, Joe Stein wrote: > +1 ran quick start from source and binary release > > On Fri, May 20, 2016 at 1:07 PM, Ewen Cheslack-Postava > wrote: > >> +1 validated connect with a

[jira] [Commented] (KAFKA-3735) RocksDB objects needs to be disposed after usage

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

[GitHub] kafka pull request: KAFKA-3735: Dispose all RocksObejcts upon comp...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1411 --- 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-3735) RocksDB objects needs to be disposed after usage

[ https://issues.apache.org/jira/browse/KAFKA-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3735. -- Resolution: Fixed Fix Version/s: 0.10.0.1 Issue resolved by pull request 1411

[jira] [Commented] (KAFKA-3720) Remove BufferExhaustException from doSend() in KafkaProducer

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

[GitHub] kafka pull request: KAFKA-3720 : Deprecated BufferExhaustedExcepti...

GitHub user MayureshGharat opened a pull request: https://github.com/apache/kafka/pull/1417 KAFKA-3720 : Deprecated BufferExhaustedException and also removed its use and the related sensor metric BufferExhaustedException is no longer used and should be deprecated and the

[jira] [Assigned] (KAFKA-3739) Add no-arg constructor for library provided serdes

[ https://issues.apache.org/jira/browse/KAFKA-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reassigned KAFKA-3739: - Assignee: Liquan Pei > Add no-arg constructor for library provided serdes >

[jira] [Commented] (KAFKA-3740) Add configs for RocksDBStores

[ https://issues.apache.org/jira/browse/KAFKA-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293908#comment-15293908 ] Guozhang Wang commented on KAFKA-3740: -- [~h...@pinterest.com] Are you interested in picking it up? >

[jira] [Created] (KAFKA-3740) Add configs for RocksDBStores

Guozhang Wang created KAFKA-3740: Summary: Add configs for RocksDBStores Key: KAFKA-3740 URL: https://issues.apache.org/jira/browse/KAFKA-3740 Project: Kafka Issue Type: Bug

Re: [VOTE] 0.10.0.0 RC6

+1 ran quick start from source and binary release On Fri, May 20, 2016 at 1:07 PM, Ewen Cheslack-Postava wrote: > +1 validated connect with a couple of simple connectors and console > producer/consumer. > > -Ewen > > On Fri, May 20, 2016 at 9:53 AM, Guozhang Wang

[jira] [Created] (KAFKA-3739) Add no-arg constructor for library provided serdes

Guozhang Wang created KAFKA-3739: Summary: Add no-arg constructor for library provided serdes Key: KAFKA-3739 URL: https://issues.apache.org/jira/browse/KAFKA-3739 Project: Kafka Issue Type:

Re: [VOTE] 0.10.0.0 RC6

+1 validated connect with a couple of simple connectors and console producer/consumer. -Ewen On Fri, May 20, 2016 at 9:53 AM, Guozhang Wang wrote: > +1. Validated maven (should be > https://repository.apache.org/content/groups/staging/org/apache/kafka/ > btw) > and binary

[jira] [Resolved] (KAFKA-3730) Problem when updating from 0.8.2 to 0.9.0

[ https://issues.apache.org/jira/browse/KAFKA-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clint Hillerman resolved KAFKA-3730. Resolution: Not A Problem Operator error > Problem when updating from 0.8.2 to 0.9.0 >

Re: [VOTE] 0.10.0.0 RC6

+1. Validated maven (should be https://repository.apache.org/content/groups/staging/org/apache/kafka/ btw) and binary libraries, quick start. On Fri, May 20, 2016 at 9:36 AM, Harsha wrote: > +1 . Ran a 3-node cluster with few system tests on our side. Looks good. > > -Harsha >

[GitHub] kafka pull request: Specifiy keyalg RSA for SSL key generation.

GitHub user harshach opened a pull request: https://github.com/apache/kafka/pull/1416 Specifiy keyalg RSA for SSL key generation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/harshach/kafka ssl-doc-fix Alternatively you can

[jira] [Commented] (KAFKA-3730) Problem when updating from 0.8.2 to 0.9.0

[ https://issues.apache.org/jira/browse/KAFKA-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293678#comment-15293678 ] Clint Hillerman commented on KAFKA-3730: I don't know how to edit that horrible english. >

Re: [VOTE] 0.10.0.0 RC6

+1 . Ran a 3-node cluster with few system tests on our side. Looks good. -Harsha On Thu, May 19, 2016, at 07:47 PM, Jun Rao wrote: > Thanks for running the release. +1 from me. Verified the quickstart. > > Jun > > On Tue, May 17, 2016 at 10:00 PM, Gwen Shapira wrote: > > >

[jira] [Commented] (KAFKA-3730) Problem when updating from 0.8.2 to 0.9.0

[ https://issues.apache.org/jira/browse/KAFKA-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293646#comment-15293646 ] Clint Hillerman commented on KAFKA-3730: Omg I got it. You right from the beginning. There was 4th

[jira] [Commented] (KAFKA-3730) Problem when updating from 0.8.2 to 0.9.0

[ https://issues.apache.org/jira/browse/KAFKA-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293641#comment-15293641 ] Ismael Juma commented on KAFKA-3730: You can change it by using ZooKeeper's chroot functionality. but

[jira] [Commented] (KAFKA-3730) Problem when updating from 0.8.2 to 0.9.0

[ https://issues.apache.org/jira/browse/KAFKA-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293636#comment-15293636 ] Clint Hillerman commented on KAFKA-3730: I'm having trouble finding the script: I look in:

[jira] [Commented] (KAFKA-3730) Problem when updating from 0.8.2 to 0.9.0

[ https://issues.apache.org/jira/browse/KAFKA-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293631#comment-15293631 ] Clint Hillerman commented on KAFKA-3730: Oh no I didn't. I've never used the zookeeper-shell

[jira] [Commented] (KAFKA-3730) Problem when updating from 0.8.2 to 0.9.0

[ https://issues.apache.org/jira/browse/KAFKA-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293628#comment-15293628 ] Clint Hillerman commented on KAFKA-3730: Like it's a path that I can't change? That's really

[jira] [Commented] (KAFKA-3730) Problem when updating from 0.8.2 to 0.9.0

[ https://issues.apache.org/jira/browse/KAFKA-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293626#comment-15293626 ] Vahid Hashemian commented on KAFKA-3730: Did you try it using the ZooKeeper shell

[jira] [Commented] (KAFKA-3730) Problem when updating from 0.8.2 to 0.9.0

[ https://issues.apache.org/jira/browse/KAFKA-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293624#comment-15293624 ] Ismael Juma commented on KAFKA-3730: That's a path inside ZooKeeper. > Problem when updating from

[jira] [Commented] (KAFKA-3730) Problem when updating from 0.8.2 to 0.9.0

[ https://issues.apache.org/jira/browse/KAFKA-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293613#comment-15293613 ] Clint Hillerman commented on KAFKA-3730: Ok, I'll include that when I can. I don't have

[jira] [Commented] (KAFKA-3730) Problem when updating from 0.8.2 to 0.9.0

[ https://issues.apache.org/jira/browse/KAFKA-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293606#comment-15293606 ] Ismael Juma commented on KAFKA-3730: ZooKeeper stores information about the brokers under:

[jira] [Comment Edited] (KAFKA-3730) Problem when updating from 0.8.2 to 0.9.0

[ https://issues.apache.org/jira/browse/KAFKA-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293606#comment-15293606 ] Ismael Juma edited comment on KAFKA-3730 at 5/20/16 4:01 PM: - ZooKeeper stores

[jira] [Commented] (KAFKA-3730) Problem when updating from 0.8.2 to 0.9.0

[ https://issues.apache.org/jira/browse/KAFKA-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293589#comment-15293589 ] Clint Hillerman commented on KAFKA-3730: Thanks for the response. I'm fairly certain I updated

[jira] [Created] (KAFKA-3738) Add system test against memory leak in Kafka Streams

Guozhang Wang created KAFKA-3738: Summary: Add system test against memory leak in Kafka Streams Key: KAFKA-3738 URL: https://issues.apache.org/jira/browse/KAFKA-3738 Project: Kafka Issue

Re: [DISCUSS] KIP-58 - Make Log Compaction Point Configurable

Tom, Documentation improvements are always welcome. The docs are in /docs under the main repository, just sent a PR for trunk and we are good :) Segment sizes - I have some objections, but this can be discussed in its own thread. I feel like I did enough hijacking and Eric may get annoyed at

[jira] [Commented] (KAFKA-2450) Kafka 0.8.2.1 kafka-console-consumer.sh broken

[ https://issues.apache.org/jira/browse/KAFKA-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293483#comment-15293483 ] Joseph Lawson commented on KAFKA-2450: -- {quote} ./kafka-console-producer.sh --topic bidhistory

[jira] [Commented] (KAFKA-2450) Kafka 0.8.2.1 kafka-console-consumer.sh broken

[ https://issues.apache.org/jira/browse/KAFKA-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293497#comment-15293497 ] Joseph Lawson commented on KAFKA-2450: -- Turns out I had my $CLASSPATH set. Unsetting that fixed it.

[jira] [Commented] (KAFKA-3567) Add --security-protocol option to console consumer and producer

[ https://issues.apache.org/jira/browse/KAFKA-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293490#comment-15293490 ] Bharat Viswanadham commented on KAFKA-3567: --- I have opened a pull request for this Jira. This is

[jira] [Commented] (KAFKA-2450) Kafka 0.8.2.1 kafka-console-consumer.sh broken

[ https://issues.apache.org/jira/browse/KAFKA-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293478#comment-15293478 ] Joseph Lawson commented on KAFKA-2450: -- I got this on kafka_2.10-0.8.2.1 and kafka_2.10-0.8.2.2 >

[jira] [Commented] (KAFKA-3737) Closing connection during produce request should be log with WARN level.

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

[GitHub] kafka pull request: KAFKA-3737: Change log level for error during ...

GitHub user fhussonnois opened a pull request: https://github.com/apache/kafka/pull/1415 KAFKA-3737: Change log level for error during produce request Minor change for https://issues.apache.org/jira/browse/KAFKA-3737 You can merge this pull request into a Git repository by running:

[jira] [Created] (KAFKA-3737) Closing connection during produce request should be log with WARN level.

Florian Hussonnois created KAFKA-3737: - Summary: Closing connection during produce request should be log with WARN level. Key: KAFKA-3737 URL: https://issues.apache.org/jira/browse/KAFKA-3737

Default log.roll.ms to the default retention or the retention in that topic

Hi, Kafka has a configuration property, log.roll.ms (and log.roll.hours because Kafka likes having lots of conflicting settings). By default it's set at 168 hours, which exactly matches the default retention of 168 hours. # Reminder of what the setting does, please skip if you know This setting

[jira] [Commented] (KAFKA-3736) Add http metrics reporter

[ https://issues.apache.org/jira/browse/KAFKA-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293377#comment-15293377 ] Adrian Muraru commented on KAFKA-3736: -- But is this change changing the public interfaces? > Add

[jira] [Commented] (KAFKA-3736) Add http metrics reporter

[ https://issues.apache.org/jira/browse/KAFKA-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293328#comment-15293328 ] Ben Stopford commented on KAFKA-3736: - I think it's the "Any change that impacts the public interfaces

[jira] [Commented] (KAFKA-3736) Add http metrics reporter

[ https://issues.apache.org/jira/browse/KAFKA-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293323#comment-15293323 ] Adrian Muraru commented on KAFKA-3736: -- I can add a KIP no problem but I was wondering if this is

[jira] [Commented] (KAFKA-3736) Add http metrics reporter

[ https://issues.apache.org/jira/browse/KAFKA-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293322#comment-15293322 ] Adrian Muraru commented on KAFKA-3736: -- Agree - let me see if I can extract this to a

[jira] [Commented] (KAFKA-3728) EndToEndAuthorizationTest offsets_topic misconfigured

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

[GitHub] kafka pull request: KAFKA-3728 EndToEndAuthorizationTest offsets_t...

GitHub user edoardocomar opened a pull request: https://github.com/apache/kafka/pull/1414 KAFKA-3728 EndToEndAuthorizationTest offsets_topic misconfigured Set OffsetsTopicReplicationFactorProp to 3 like MinInSyncReplicasProp and OffsetCommitRequiredAcksProp to 1 to avoid

[jira] [Commented] (KAFKA-3728) EndToEndAuthorizationTest offsets_topic misconfigured

[ https://issues.apache.org/jira/browse/KAFKA-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293272#comment-15293272 ] Edoardo Comar commented on KAFKA-3728: -- Thanks [~rsivaram] it wasn't obvious that ack=-1 requires a

[jira] [Updated] (KAFKA-3728) EndToEndAuthorizationTest offsets_topic misconfigured

[ https://issues.apache.org/jira/browse/KAFKA-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edoardo Comar updated KAFKA-3728: - Summary: EndToEndAuthorizationTest offsets_topic misconfigured (was: inconsistent behavior of

Re: [DISCUSS] KIP-58 - Make Log Compaction Point Configurable

Hi, >From our perspective (running thousands of Kafka clusters), the main issues we see with compacted topics *aren't* disk space usage, or IO utilization of the log cleaner. Size matters a *lot* to the usability of consumers bootstrapping from the beginning - in fact we've been debating tuning

[jira] [Commented] (KAFKA-3718) propagate all KafkaConfig __consumer_offsets configs to OffsetConfig instantiation

[ https://issues.apache.org/jira/browse/KAFKA-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293251#comment-15293251 ] Ismael Juma commented on KAFKA-3718: This is too late for 0.10.0.0, so updated the fix version. >

[jira] [Updated] (KAFKA-3718) propagate all KafkaConfig __consumer_offsets configs to OffsetConfig instantiation

[ https://issues.apache.org/jira/browse/KAFKA-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3718: --- Fix Version/s: (was: 0.10.0.0) 0.10.0.1 > propagate all KafkaConfig

[jira] [Commented] (KAFKA-3736) Add http metrics reporter

[ https://issues.apache.org/jira/browse/KAFKA-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293249#comment-15293249 ] Ismael Juma commented on KAFKA-3736: Yes, we need a KIP indeed. It also adds new dependencies to the

[jira] [Updated] (KAFKA-3736) Add http metrics reporter

[ https://issues.apache.org/jira/browse/KAFKA-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3736: --- Fix Version/s: (was: 0.10.0.0) 0.10.1.0 > Add http metrics reporter >

[jira] [Updated] (KAFKA-3733) Avoid long command lines by setting CLASSPATH in environment

[ https://issues.apache.org/jira/browse/KAFKA-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3733: --- Fix Version/s: (was: 0.10.0.0) 0.10.0.1 > Avoid long command lines by setting

[jira] [Commented] (KAFKA-3733) Avoid long command lines by setting CLASSPATH in environment

[ https://issues.apache.org/jira/browse/KAFKA-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293244#comment-15293244 ] Ismael Juma commented on KAFKA-3733: Thanks for the JIRA and PR. It's too late for 0.10.0.0, so

[jira] [Commented] (KAFKA-3736) Add http metrics reporter

[ https://issues.apache.org/jira/browse/KAFKA-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293234#comment-15293234 ] Ben Stopford commented on KAFKA-3736: - Nice little idea! I think it might require a KIP as technically

[jira] [Updated] (KAFKA-3733) Avoid long command lines by setting CLASSPATH in environment

[ https://issues.apache.org/jira/browse/KAFKA-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Muraru updated KAFKA-3733: - Fix Version/s: 0.10.0.0 Status: Patch Available (was: Open) > Avoid long command

[jira] [Updated] (KAFKA-3736) Add http metrics reporter

[ https://issues.apache.org/jira/browse/KAFKA-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Muraru updated KAFKA-3736: - Fix Version/s: 0.10.0.0 Status: Patch Available (was: Open) > Add http metrics

[GitHub] kafka pull request: MINOR: set charset of Javadoc to UTF-8

GitHub user sasakitoa opened a pull request: https://github.com/apache/kafka/pull/1413 MINOR: set charset of Javadoc to UTF-8 Currently javadoc doesn't specify charset. This pull reqeust will set this to UTF-8. You can merge this pull request into a Git repository by running:

[jira] [Commented] (KAFKA-3732) Add an auto accept option to kafka-acls.sh

[ https://issues.apache.org/jira/browse/KAFKA-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293026#comment-15293026 ] Mickael Maison commented on KAFKA-3732: --- I considered removing the prompt altogether, but thought it

[jira] [Commented] (KAFKA-3736) Add http metrics reporter

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

[GitHub] kafka pull request: KAFKA-3736: Add HTTP Metrics reporter

GitHub user amuraru opened a pull request: https://github.com/apache/kafka/pull/1412 KAFKA-3736: Add HTTP Metrics reporter You can merge this pull request into a Git repository by running: $ git pull https://github.com/hstack/kafka KAFKA-3736 Alternatively you can review and

[jira] [Created] (KAFKA-3736) Add http metrics reporter

Adrian Muraru created KAFKA-3736: Summary: Add http metrics reporter Key: KAFKA-3736 URL: https://issues.apache.org/jira/browse/KAFKA-3736 Project: Kafka Issue Type: New Feature

[jira] [Commented] (KAFKA-3664) When subscription set changes on new consumer, the partitions may be removed without offset being committed.

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

[jira] [Commented] (KAFKA-3664) When subscription set changes on new consumer, the partitions may be removed without offset being committed.

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

[GitHub] kafka pull request: KAFKA-3664: Commit offset of unsubscribed part...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1363 KAFKA-3664: Commit offset of unsubscribed partitions of the new consumer on a subscription change When users are using group management, if they call consumer.subscribe() to change the

[GitHub] kafka pull request: KAFKA-3664: Commit offset of unsubscribed part...

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