[jira] [Commented] (KAFKA-2501) getting one test failed when building apache kafka

[ https://issues.apache.org/jira/browse/KAFKA-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728567#comment-14728567 ] naresh gundu commented on KAFKA-2501: - root@69bb9e99fb8d:/kafka/core/build/dependant-l

[jira] [Commented] (KAFKA-2501) getting one test failed when building apache kafka

[ https://issues.apache.org/jira/browse/KAFKA-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728564#comment-14728564 ] naresh gundu commented on KAFKA-2501: - Hi Even, I following the below steps to build

[jira] [Commented] (KAFKA-2506) Refactor KafkaConsumer.partitionsFor(topic) to get metadata of topic without modifying state of Metadata

[ https://issues.apache.org/jira/browse/KAFKA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728522#comment-14728522 ] Ewen Cheslack-Postava commented on KAFKA-2506: -- [~singhashish] While reviewin

[jira] [Commented] (KAFKA-2501) getting one test failed when building apache kafka

[ https://issues.apache.org/jira/browse/KAFKA-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728519#comment-14728519 ] Ewen Cheslack-Postava commented on KAFKA-2501: -- Can you find the snappy-java

[jira] [Updated] (KAFKA-2461) request logger no longer logs extra information in debug mode

[ https://issues.apache.org/jira/browse/KAFKA-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2461: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 16

[jira] [Commented] (KAFKA-2461) request logger no longer logs extra information in debug mode

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

[GitHub] kafka pull request: KAFKA-2461: request logger no longer logs extr...

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

[jira] [Commented] (KAFKA-2447) Add capability to KafkaLog4jAppender to be able to use SSL

[ https://issues.apache.org/jira/browse/KAFKA-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728507#comment-14728507 ] Gwen Shapira commented on KAFKA-2447: - Agree. But as nice-to-have, not a blocker on re

[jira] [Commented] (KAFKA-2447) Add capability to KafkaLog4jAppender to be able to use SSL

[ https://issues.apache.org/jira/browse/KAFKA-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728503#comment-14728503 ] Ashish K Singh commented on KAFKA-2447: --- [~gwenshap] I think it will be nice to have

[jira] [Created] (KAFKA-2506) Refactor KafkaConsumer.partitionsFor(topic) to get metadata of topic without modifying state of Metadata

Ashish K Singh created KAFKA-2506: - Summary: Refactor KafkaConsumer.partitionsFor(topic) to get metadata of topic without modifying state of Metadata Key: KAFKA-2506 URL: https://issues.apache.org/jira/browse/KAFK

[jira] [Updated] (KAFKA-2501) getting one test failed when building apache kafka

[ https://issues.apache.org/jira/browse/KAFKA-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] naresh gundu updated KAFKA-2501: Environment: Ubuntu 15.04 ppc64 le (was: Ubuntu 15.04) Remaining Estimate: 48h (was: 1m)

[jira] [Commented] (KAFKA-2501) getting one test failed when building apache kafka

[ https://issues.apache.org/jira/browse/KAFKA-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728500#comment-14728500 ] naresh gundu commented on KAFKA-2501: - i am working on rhel7.1 and Ubuntu 15.04 ppc64

[jira] [Commented] (KAFKA-2501) getting one test failed when building apache kafka

[ https://issues.apache.org/jira/browse/KAFKA-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728491#comment-14728491 ] Ewen Cheslack-Postava commented on KAFKA-2501: -- This looks like there's somet

[GitHub] kafka pull request: Kafka 1686. Implement SASL/Kerberos.

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

[jira] [Commented] (KAFKA-1686) Implement SASL/Kerberos

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

[GitHub] kafka pull request: KAFKA-1686: Implement SASL/Kerberos.

GitHub user harshach opened a pull request: https://github.com/apache/kafka/pull/191 KAFKA-1686: Implement SASL/Kerberos. You can merge this pull request into a Git repository by running: $ git pull https://github.com/harshach/kafka KAFKA-1686-V1 Alternatively you can review

[GitHub] kafka pull request: Kafka 1686. Implement SASL/Kerberos.

GitHub user harshach opened a pull request: https://github.com/apache/kafka/pull/190 Kafka 1686. Implement SASL/Kerberos. You can merge this pull request into a Git repository by running: $ git pull https://github.com/harshach/kafka KAFKA-1686 Alternatively you can review and

[jira] [Commented] (KAFKA-2397) leave group request

[ https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728410#comment-14728410 ] Ewen Cheslack-Postava commented on KAFKA-2397: -- [~hachikuji] My primary objec

Jenkins build is back to normal : Kafka-trunk #613

See

[jira] [Updated] (KAFKA-2505) Add trace/debug description modes to the new Request/Response API

[ https://issues.apache.org/jira/browse/KAFKA-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-2505: -- Description: It was pointed out on KAFKA-2461 that trace/debug description modes are required fo

[jira] [Created] (KAFKA-2505) Add trace/debug description modes to the new Request/Response API

Ashish K Singh created KAFKA-2505: - Summary: Add trace/debug description modes to the new Request/Response API Key: KAFKA-2505 URL: https://issues.apache.org/jira/browse/KAFKA-2505 Project: Kafka

[jira] [Resolved] (KAFKA-2437) Controller does not handle zk node deletion correctly.

[ https://issues.apache.org/jira/browse/KAFKA-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy resolved KAFKA-2437. --- Resolution: Fixed Fix Version/s: 0.8.3 > Controller does not handle zk node deletion correctly.

[jira] [Commented] (KAFKA-2437) Controller does not handle zk node deletion correctly.

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

[GitHub] kafka pull request: KAFKA-2437: Fix ZookeeperLeaderElector to hand...

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

[jira] [Updated] (KAFKA-2210) KafkaAuthorizer: Add all public entities, config changes and changes to KafkaAPI and kafkaServer to allow pluggable authorizer implementation.

[ https://issues.apache.org/jira/browse/KAFKA-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2210: --- Resolution: Fixed Status: Resolved (was: Patch Available) [~parth.brahmbhatt], thanks a lot of the pa

[jira] [Commented] (KAFKA-1543) Changing replication factor

[ https://issues.apache.org/jira/browse/KAFKA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728340#comment-14728340 ] Alexander Pakulov commented on KAFKA-1543: -- I didn't check for this scenario, I'l

Re: Review Request 34492: Patch for KAFKA-2210

> On Sept. 2, 2015, 1:11 p.m., Ismael Juma wrote: > > Hi Parth, I finally had a bit of time to look into this in more detail and > > I pushed a commit with my suggestions to make the `KafkaApis` code a bit > > more readable: > > > > https://github.com/ijuma/kafka/commit/7737a9feb0c6d8cb4be3fe2

[jira] [Commented] (KAFKA-2437) Controller does not handle zk node deletion correctly.

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

[GitHub] kafka pull request: KAFKA-2437: Fix ZookeeperLeaderElector to hand...

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/189 KAFKA-2437: Fix ZookeeperLeaderElector to handle node deletion correctly. You can merge this pull request into a Git repository by running: $ git pull https://github.com/becketqin/kafka KAFKA

Re: Review Request 34492: Patch for KAFKA-2210

> On Sept. 2, 2015, 4:36 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/common/ErrorMapping.scala, lines 55-57 > > > > > > Could you add the missing error cords 23-28 in the comment? copied the error constant fr

Re: Review Request 34492: Patch for KAFKA-2210

> On Sept. 2, 2015, 1:11 p.m., Ismael Juma wrote: > > Hi Parth, I finally had a bit of time to look into this in more detail and > > I pushed a commit with my suggestions to make the `KafkaApis` code a bit > > more readable: > > > > https://github.com/ijuma/kafka/commit/7737a9feb0c6d8cb4be3fe2

Re: Review Request 34492: Patch for KAFKA-2210

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34492/#review97582 --- Ship it! Thanks Parth, LGTM. - Ismael Juma On Sept. 3, 2015, 12:

[jira] [Updated] (KAFKA-2210) KafkaAuthorizer: Add all public entities, config changes and changes to KafkaAPI and kafkaServer to allow pluggable authorizer implementation.

[ https://issues.apache.org/jira/browse/KAFKA-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Brahmbhatt updated KAFKA-2210: Attachment: KAFKA-2210_2015-09-02_17:36:47.patch > KafkaAuthorizer: Add all public entities,

[jira] [Commented] (KAFKA-2210) KafkaAuthorizer: Add all public entities, config changes and changes to KafkaAPI and kafkaServer to allow pluggable authorizer implementation.

[ https://issues.apache.org/jira/browse/KAFKA-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728299#comment-14728299 ] Parth Brahmbhatt commented on KAFKA-2210: - Updated reviewboard https://reviews.apa

Re: Review Request 34492: Patch for KAFKA-2210

> On Sept. 2, 2015, 11:13 p.m., Jun Rao wrote: > > Hmm, did you attach the right patch? It doesn't seem to apply to trunk and > > my last round of minor comments didn't seem to get addressed. Also, one > > more suggestion below. Can you take a look now? I am not sure why the patch looked weird

Re: Review Request 34492: Patch for KAFKA-2210

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34492/ --- (Updated Sept. 3, 2015, 12:36 a.m.) Review request for kafka. Bugs: KAFKA-221

[jira] [Updated] (KAFKA-2210) KafkaAuthorizer: Add all public entities, config changes and changes to KafkaAPI and kafkaServer to allow pluggable authorizer implementation.

[ https://issues.apache.org/jira/browse/KAFKA-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Brahmbhatt updated KAFKA-2210: Attachment: KAFKA-2210_2015-09-02_17:32:06.patch > KafkaAuthorizer: Add all public entities,

[jira] [Commented] (KAFKA-2210) KafkaAuthorizer: Add all public entities, config changes and changes to KafkaAPI and kafkaServer to allow pluggable authorizer implementation.

[ https://issues.apache.org/jira/browse/KAFKA-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728293#comment-14728293 ] Parth Brahmbhatt commented on KAFKA-2210: - Updated reviewboard https://reviews.apa

Re: Review Request 34492: Patch for KAFKA-2210

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34492/ --- (Updated Sept. 3, 2015, 12:32 a.m.) Review request for kafka. Bugs: KAFKA-221

[jira] [Updated] (KAFKA-1937) Mirror maker needs to clear the unacked offset map after rebalance.

[ https://issues.apache.org/jira/browse/KAFKA-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-1937: Resolution: Not A Problem Status: Resolved (was: Patch Available) Not applicable any more.

[jira] [Updated] (KAFKA-1840) Add a simple message handler in Mirror Maker

[ https://issues.apache.org/jira/browse/KAFKA-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-1840: Resolution: Fixed Status: Resolved (was: Patch Available) The code has been checked in KAFK

[jira] [Updated] (KAFKA-1057) Trim whitespaces from user specified configs

[ https://issues.apache.org/jira/browse/KAFKA-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1057: --- Fix Version/s: (was: 0.8.2.2) > Trim whitespaces from user specified configs > ---

[jira] [Updated] (KAFKA-1836) metadata.fetch.timeout.ms set to zero blocks forever

[ https://issues.apache.org/jira/browse/KAFKA-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1836: --- Fix Version/s: (was: 0.8.2.2) > metadata.fetch.timeout.ms set to zero blocks forever > ---

[jira] [Updated] (KAFKA-2096) Enable keepalive socket option for broker to prevent socket leak

[ https://issues.apache.org/jira/browse/KAFKA-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2096: --- Fix Version/s: (was: 0.8.2.2) > Enable keepalive socket option for broker to prevent socket leak > ---

[jira] [Updated] (KAFKA-1758) corrupt recovery file prevents startup

[ https://issues.apache.org/jira/browse/KAFKA-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1758: --- Fix Version/s: (was: 0.8.2.2) > corrupt recovery file prevents startup > -

[jira] [Updated] (KAFKA-2114) Unable to change min.insync.replicas default

[ https://issues.apache.org/jira/browse/KAFKA-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2114: --- Fix Version/s: (was: 0.8.2.2) > Unable to change min.insync.replicas default > ---

[jira] [Updated] (KAFKA-1883) NullPointerException in RequestSendThread

[ https://issues.apache.org/jira/browse/KAFKA-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1883: --- Fix Version/s: (was: 0.8.2.2) > NullPointerException in RequestSendThread > --

[jira] [Updated] (KAFKA-1668) TopicCommand doesn't warn if --topic argument doesn't match any topics

[ https://issues.apache.org/jira/browse/KAFKA-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1668: --- Fix Version/s: (was: 0.8.2.2) > TopicCommand doesn't warn if --topic argument doesn't match any topics > -

[jira] [Updated] (KAFKA-2235) LogCleaner offset map overflow

[ https://issues.apache.org/jira/browse/KAFKA-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2235: --- Fix Version/s: (was: 0.8.2.2) > LogCleaner offset map overflow > -- > >

[jira] [Commented] (KAFKA-2437) Controller does not handle zk node deletion correctly.

[ https://issues.apache.org/jira/browse/KAFKA-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728248#comment-14728248 ] Jiangjie Qin commented on KAFKA-2437: - Debugged with [~jjkoshy] and found the followin

[jira] [Updated] (KAFKA-2437) Controller did not handle zk node deletion correctly.

[ https://issues.apache.org/jira/browse/KAFKA-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2437: Summary: Controller did not handle zk node deletion correctly. (was: Controller lost /controller zo

[jira] [Updated] (KAFKA-2437) Controller does not handle zk node deletion correctly.

[ https://issues.apache.org/jira/browse/KAFKA-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-2437: Summary: Controller does not handle zk node deletion correctly. (was: Controller did not handle zk

[jira] [Commented] (KAFKA-2209) Change client quotas dynamically using DynamicConfigManager

[ https://issues.apache.org/jira/browse/KAFKA-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728228#comment-14728228 ] Jun Rao commented on KAFKA-2209: With the dynamic configuration, do we plan to remove the

Re: Review Request 34492: Patch for KAFKA-2210

> On Sept. 2, 2015, 11:13 p.m., Jun Rao wrote: > > core/src/main/scala/kafka/server/KafkaApis.scala, line 676 > > > > > > Could we change the test to the following to make it more consistent > > with the rest of pl

Re: Review Request 34492: Patch for KAFKA-2210

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34492/#review97554 --- Hmm, did you attach the right patch? It doesn't seem to apply to tru

[jira] [Commented] (KAFKA-2338) Warn users if they change max.message.bytes that they also need to update broker and consumer settings

[ https://issues.apache.org/jira/browse/KAFKA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728149#comment-14728149 ] Edward Ribeiro commented on KAFKA-2338: --- Updated reviewboard https://reviews.apache.

[jira] [Updated] (KAFKA-2338) Warn users if they change max.message.bytes that they also need to update broker and consumer settings

[ https://issues.apache.org/jira/browse/KAFKA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Ribeiro updated KAFKA-2338: -- Attachment: KAFKA-2338_2015-09-02_19:27:17.patch > Warn users if they change max.message.bytes t

Re: Review Request 36578: Patch for KAFKA-2338

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36578/ --- (Updated Sept. 2, 2015, 10:30 p.m.) Review request for kafka. Bugs: KAFKA-233

[jira] [Commented] (KAFKA-1543) Changing replication factor

[ https://issues.apache.org/jira/browse/KAFKA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728131#comment-14728131 ] Alexander Pakulov commented on KAFKA-1543: -- Agree, but since I've been working on

[jira] [Updated] (KAFKA-1387) Kafka getting stuck creating ephemeral node it has already created when two zookeeper sessions are established in a very short period of time

[ https://issues.apache.org/jira/browse/KAFKA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1387: Priority: Critical (was: Blocker) > Kafka getting stuck creating ephemeral node it has already crea

[jira] [Updated] (KAFKA-2258) Port mirrormaker_testsuite

[ https://issues.apache.org/jira/browse/KAFKA-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2258: Priority: Blocker (was: Major) > Port mirrormaker_testsuite > -- > >

[jira] [Updated] (KAFKA-2257) port replication_testsuite

[ https://issues.apache.org/jira/browse/KAFKA-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2257: Priority: Blocker (was: Major) > port replication_testsuite > -- > >

[jira] [Updated] (KAFKA-2259) port offset_management_testsuite

[ https://issues.apache.org/jira/browse/KAFKA-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2259: Priority: Blocker (was: Major) > port offset_management_testsuite > ---

[jira] [Updated] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2311: Reviewer: Jason Gustafson (was: Neha Narkhede) > Consumer's ensureNotClosed method not thread safe

[jira] [Updated] (KAFKA-2311) Consumer's ensureNotClosed method not thread safe

[ https://issues.apache.org/jira/browse/KAFKA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2311: Priority: Major (was: Blocker) > Consumer's ensureNotClosed method not thread safe > --

[jira] [Commented] (KAFKA-2210) KafkaAuthorizer: Add all public entities, config changes and changes to KafkaAPI and kafkaServer to allow pluggable authorizer implementation.

[ https://issues.apache.org/jira/browse/KAFKA-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728093#comment-14728093 ] Parth Brahmbhatt commented on KAFKA-2210: - Updated reviewboard https://reviews.apa

[jira] [Updated] (KAFKA-2338) Warn users if they change max.message.bytes that they also need to update broker and consumer settings

[ https://issues.apache.org/jira/browse/KAFKA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2338: Priority: Critical (was: Blocker) > Warn users if they change max.message.bytes that they also need

[jira] [Updated] (KAFKA-2210) KafkaAuthorizer: Add all public entities, config changes and changes to KafkaAPI and kafkaServer to allow pluggable authorizer implementation.

[ https://issues.apache.org/jira/browse/KAFKA-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Brahmbhatt updated KAFKA-2210: Attachment: KAFKA-2210_2015-09-02_14:50:29.patch > KafkaAuthorizer: Add all public entities,

Re: Review Request 34492: Patch for KAFKA-2210

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34492/#review97481 --- core/src/main/scala/kafka/server/KafkaApis.scala (line 296)

Re: Review Request 34492: Patch for KAFKA-2210

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34492/ --- (Updated Sept. 2, 2015, 9:50 p.m.) Review request for kafka. Bugs: KAFKA-2210

[jira] [Updated] (KAFKA-2454) Dead lock between delete log segment and shutting down.

[ https://issues.apache.org/jira/browse/KAFKA-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2454: Priority: Major (was: Blocker) > Dead lock between delete log segment and shutting down. >

Re: Kafka New Consumer Performance Test ThroughPut Degradation

Hi Poorna, We've been looking at the same issue as part of KAFKA-2489. I suspect the initial rebalance is causing the test to timeout, but we're still investigating. Thanks, Jason On Wed, Sep 2, 2015 at 2:03 PM, Poorna Chandra Tejashvi Reddy < pctre...@gmail.com> wrote: > Hi, > > I have checked

Re: Kafka New Consumer Performance Test ThroughPut Degradation

Hi, I have checked out the latest code out of https://github.com/apache/kafka based on commit id e582447adb4708731aff74aa294e7ce2b30b0a41. Looks like the performance test on the new-consumer is broken. in/kafka-consumer-perf-test.sh --zookeeper zkip:2181 --broker-list brokerIp:9092 --topic test -

[jira] [Resolved] (KAFKA-824) java.lang.NullPointerException in commitOffsets

[ https://issues.apache.org/jira/browse/KAFKA-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-824. --- Resolution: Fixed Fix Version/s: 0.8.3 [~parth.brahmbhatt], thanks for confirming this. Resolving this j

[jira] [Commented] (KAFKA-2212) KafkaAuthorizer: Add CLI for Acl management.

[ https://issues.apache.org/jira/browse/KAFKA-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727975#comment-14727975 ] Jun Rao commented on KAFKA-2212: One thing that I realized is that not all operations make

[jira] [Commented] (KAFKA-2211) KafkaAuthorizer: Add simpleACLAuthorizer implementation.

[ https://issues.apache.org/jira/browse/KAFKA-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727971#comment-14727971 ] Jun Rao commented on KAFKA-2211: A couple of other things: 1. Since the authorizer uses Ka

[jira] [Commented] (KAFKA-1929) Convert core kafka module to use the errors in org.apache.kafka.common.errors

[ https://issues.apache.org/jira/browse/KAFKA-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727964#comment-14727964 ] Jason Gustafson commented on KAFKA-1929: [~jholoman] Are you still working on this

[jira] [Updated] (KAFKA-2491) Update ErrorMapping with New Consumer Errors

[ https://issues.apache.org/jira/browse/KAFKA-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2491: --- Status: Patch Available (was: Open) > Update ErrorMapping with New Consumer Errors >

[jira] [Commented] (KAFKA-2491) Update ErrorMapping with New Consumer Errors

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

[GitHub] kafka pull request: KAFKA-2491; update ErrorMapping with new consu...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/188 KAFKA-2491; update ErrorMapping with new consumer errors You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-2491 Alternativ

[jira] [Commented] (KAFKA-2477) Replicas spuriously deleting all segments in partition

[ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727933#comment-14727933 ] Håkon Hitland commented on KAFKA-2477: -- I don't think enabling trace logging would be

[jira] [Commented] (KAFKA-2504) Stop logging WARN when client disconnects

[ https://issues.apache.org/jira/browse/KAFKA-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727886#comment-14727886 ] Ismael Juma commented on KAFKA-2504: Probably a similar one was fixed, this one has be

Build failed in Jenkins: Kafka-trunk #612

See Changes: [cshapi] TRIVIAL: Updated testing readme [junrao] KAFKA-2411; remove usage of blocking channel -- [...truncated 1667 lines...] kafka.coordinator.ConsumerCoordinatorResponseTest > testVal

[jira] [Updated] (KAFKA-2504) Stop logging WARN when client disconnects

[ https://issues.apache.org/jira/browse/KAFKA-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2504: Fix Version/s: 0.8.3 > Stop logging WARN when client disconnects > -

[jira] [Created] (KAFKA-2504) Stop logging WARN when client disconnects

Gwen Shapira created KAFKA-2504: --- Summary: Stop logging WARN when client disconnects Key: KAFKA-2504 URL: https://issues.apache.org/jira/browse/KAFKA-2504 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-2411) remove usage of BlockingChannel in the broker

[ https://issues.apache.org/jira/browse/KAFKA-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-2411: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 151 [https:/

[GitHub] kafka pull request: KAFKA-2411; remove usage of blocking channel

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

[jira] [Commented] (KAFKA-2411) remove usage of BlockingChannel in the broker

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

[jira] [Commented] (KAFKA-2453) enable new consumer in EndToEndLatency

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

[jira] [Commented] (KAFKA-2453) enable new consumer in EndToEndLatency

[ https://issues.apache.org/jira/browse/KAFKA-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727824#comment-14727824 ] ASF GitHub Bot commented on KAFKA-2453: --- GitHub user benstopford reopened a pull req

[GitHub] kafka pull request: KAFKA-2453: Enable new consumer in EndToEndLat...

GitHub user benstopford reopened a pull request: https://github.com/apache/kafka/pull/158 KAFKA-2453: Enable new consumer in EndToEndLatency You can merge this pull request into a Git repository by running: $ git pull https://github.com/benstopford/kafka KAFKA-2453b Alternat

[GitHub] kafka pull request: KAFKA-2453: Enable new consumer in EndToEndLat...

Github user benstopford closed the pull request at: https://github.com/apache/kafka/pull/158 --- 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] [Updated] (KAFKA-2502) Quotas documentation for 0.8.3

[ https://issues.apache.org/jira/browse/KAFKA-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2502: -- Description: Complete quotas documentation Also, https://cwiki.apache.org/confluence/display/KAFKA/A+G

[jira] [Commented] (KAFKA-2397) leave group request

[ https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727809#comment-14727809 ] Jason Gustafson commented on KAFKA-2397: Bumping this issue. One nice thing about

[GitHub] kafka pull request: Updated testing readme

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

[GitHub] kafka pull request: Updated testing readme

GitHub user granders opened a pull request: https://github.com/apache/kafka/pull/187 Updated testing readme Minor update to point to testing tutorial, and install the correct version of vagrant-hostmanager You can merge this pull request into a Git repository by running: $ git

Jenkins build is back to normal : Kafka-trunk #611

See

[jira] [Created] (KAFKA-2503) Metrics should be better documented

Gwen Shapira created KAFKA-2503: --- Summary: Metrics should be better documented Key: KAFKA-2503 URL: https://issues.apache.org/jira/browse/KAFKA-2503 Project: Kafka Issue Type: Bug R

[jira] [Commented] (KAFKA-2452) enable new consumer in mirror maker

[ https://issues.apache.org/jira/browse/KAFKA-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727733#comment-14727733 ] Jiangjie Qin commented on KAFKA-2452: - I want to wait for KAFKA-2389 to be checked in

[jira] [Commented] (KAFKA-2394) Use RollingFileAppender by default in log4j.properties

[ https://issues.apache.org/jira/browse/KAFKA-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727725#comment-14727725 ] Jason Gustafson commented on KAFKA-2394: [~jinxing6...@126.com] You should be able

  1   2   >