[jira] [Updated] (KAFKA-1901) Move Kafka version to be generated in code by build (instead of in manifest)

[ https://issues.apache.org/jira/browse/KAFKA-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-1901: --- Fix Version/s: 0.8.3 > Move Kafka version to be generated in code by build (instead of in mani

[jira] [Commented] (KAFKA-2456) Disable SSLv3 for ssl.enabledprotocols config on client & broker side

[ https://issues.apache.org/jira/browse/KAFKA-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706332#comment-14706332 ] Ismael Juma commented on KAFKA-2456: Thanks for filing this Harsha, this is one of the

[jira] [Resolved] (KAFKA-1877) Expose version via JMX for 'new' producer

[ https://issues.apache.org/jira/browse/KAFKA-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-1877. Resolution: Fixed Reviewer: Joel Koshy Fix Version/s: 0.8.3 This got fixed p

[jira] [Updated] (KAFKA-2130) Resource leakage in AppInfo.scala during initialization

[ https://issues.apache.org/jira/browse/KAFKA-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-2130: --- Resolution: Fixed Assignee: Manikumar Reddy Fix Version/s: 0.8.3 Sta

[jira] [Comment Edited] (KAFKA-2130) Resource leakage in AppInfo.scala during initialization

[ https://issues.apache.org/jira/browse/KAFKA-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706375#comment-14706375 ] Manikumar Reddy edited comment on KAFKA-2130 at 8/21/15 8:04 AM: ---

[jira] [Updated] (KAFKA-1683) Implement a "session" concept in the socket server

[ https://issues.apache.org/jira/browse/KAFKA-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-1683: --- Affects Version/s: (was: 0.9.0) 0.8.2.1 > Implement a "session" concept in

[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=14706439#comment-14706439 ] Ismael Juma commented on KAFKA-2210: Thanks for the quick response [~parth.brahmbhatt]

[jira] [Commented] (KAFKA-873) Consider replacing zkclient with curator (with zkclient-bridge)

[ https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706510#comment-14706510 ] Flavio Junqueira commented on KAFKA-873: [~eribeiro]the problem is with application

[jira] [Created] (KAFKA-2457) StackOverflowError during builds

Ismael Juma created KAFKA-2457: -- Summary: StackOverflowError during builds Key: KAFKA-2457 URL: https://issues.apache.org/jira/browse/KAFKA-2457 Project: Kafka Issue Type: Bug Report

[GitHub] kafka pull request: KAFKA-2457; StackOverflowError during builds

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/157 KAFKA-2457; StackOverflowError during builds The default is typically `1m` for 64-bit machines and the Scala compiler sometimes needs more than this. You can merge this pull request into a Git reposit

[jira] [Commented] (KAFKA-2457) StackOverflowError during builds

[ https://issues.apache.org/jira/browse/KAFKA-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706546#comment-14706546 ] Ismael Juma commented on KAFKA-2457: I have verified that this fixed an instance where

[jira] [Work started] (KAFKA-2457) StackOverflowError during builds

[ https://issues.apache.org/jira/browse/KAFKA-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-2457 started by Ismael Juma. -- > StackOverflowError during builds > > >

[jira] [Commented] (KAFKA-2457) StackOverflowError during builds

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

[jira] [Updated] (KAFKA-2457) StackOverflowError during builds

[ https://issues.apache.org/jira/browse/KAFKA-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2457: --- Reviewer: Gwen Shapira Status: Patch Available (was: In Progress) > StackOverflowError during b

[jira] [Work started] (KAFKA-1811) ensuring registered broker host:port is unique

[ https://issues.apache.org/jira/browse/KAFKA-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-1811 started by Edward Ribeiro. - > ensuring registered broker host:port is unique >

[jira] [Work stopped] (KAFKA-1811) ensuring registered broker host:port is unique

[ https://issues.apache.org/jira/browse/KAFKA-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-1811 stopped by Edward Ribeiro. - > ensuring registered broker host:port is unique >

[jira] [Commented] (KAFKA-873) Consider replacing zkclient with curator (with zkclient-bridge)

[ https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706573#comment-14706573 ] Ismael Juma commented on KAFKA-873: --- The compatibility story is a bit complicated, partic

Re: KAFKA-2364 migrate docs from SVN to git

Hi All, Can we finalize the approach? So that we can proceed further. 1. Gwen's suggestion + existing svn repo 2. Gwen's suggestion + new git repo for docs kumar On Thu, Aug 20, 2015 at 11:48 PM, Manikumar Reddy wrote: > Also can we migrate svn repo to git repo? This will help us to fix >

Re: KAFKA-2364 migrate docs from SVN to git

My preference would be to do `2` because it reduces the number of tools we need to know. If we want to clone the repo for the generated site, we can use the same tools as we do for the code repo and we can watch for changes on GitHub, etc. Ismael On Fri, Aug 21, 2015 at 1:34 PM, Manikumar Reddy

Re: is SSL support feature ready to use in kafka-truck branch

Hi Qi Trunk seems fairly stable. There are guidelines here which includes how to generate keys https://cwiki.apache.org/confluence/display/KAFKA/Deploying+SSL+for+Kafka Your server config needs these properties (also

Re: Review Request 34493: Patch for KAFKA-2211

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/34493/#review96042 --- Thanks for this Parth. I did an initial pass where I left a number c

[jira] [Created] (KAFKA-2458) Documentation bug - Quickstart references 'bin/kafka-XXX-topic.sh' scripts which no longer exist

Craig McConomy created KAFKA-2458: - Summary: Documentation bug - Quickstart references 'bin/kafka-XXX-topic.sh' scripts which no longer exist Key: KAFKA-2458 URL: https://issues.apache.org/jira/browse/KAFKA-2458

[jira] [Commented] (KAFKA-2458) Documentation bug - Quickstart references 'bin/kafka-XXX-topic.sh' scripts which no longer exist

[ https://issues.apache.org/jira/browse/KAFKA-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706879#comment-14706879 ] Manikumar Reddy commented on KAFKA-2458: For 0.8.2.1, You should look here: http

[jira] [Resolved] (KAFKA-2458) Documentation bug - Quickstart references 'bin/kafka-XXX-topic.sh' scripts which no longer exist

[ https://issues.apache.org/jira/browse/KAFKA-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig McConomy resolved KAFKA-2458. --- Resolution: Not A Problem > Documentation bug - Quickstart references 'bin/kafka-XXX-topic.sh'

[jira] [Commented] (KAFKA-2458) Documentation bug - Quickstart references 'bin/kafka-XXX-topic.sh' scripts which no longer exist

[ https://issues.apache.org/jira/browse/KAFKA-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706897#comment-14706897 ] Craig McConomy commented on KAFKA-2458: --- I see - thank you. Maybe it could be made c

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

Github user ijuma 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 enable

[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=14707010#comment-14707010 ] ASF GitHub Bot commented on KAFKA-2411: --- Github user ijuma closed the pull request a

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

GitHub user benstopford opened 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 Alternativ

[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 ] Ismael Juma updated KAFKA-2411: --- Status: Open (was: Patch Available) Jun identified some issues with using `Selector` directly, so thi

[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=14707019#comment-14707019 ] ASF GitHub Bot commented on KAFKA-2453: --- GitHub user benstopford opened a pull reque

[jira] [Work started] (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 ] Work on KAFKA-2411 started by Ismael Juma. -- > remove usage of BlockingChannel in the broker > ---

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14707091#comment-14707091 ] Joel Koshy commented on KAFKA-2454: --- Thanks - got it. Will take a look at your patch tod

Re: Review Request 36652: Patch for KAFKA-2351

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36652/#review96061 --- core/src/main/scala/kafka/network/SocketServer.scala (line 264)

[jira] [Updated] (KAFKA-2412) Documentation bug: Add information for key.serializer and value.serializer to New Producer Config sections

[ https://issues.apache.org/jira/browse/KAFKA-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grayson Chao updated KAFKA-2412: Assignee: Grayson Chao Status: Patch Available (was: Open) > Documentation bug: Add informati

[jira] [Updated] (KAFKA-2412) Documentation bug: Add information for key.serializer and value.serializer to New Producer Config sections

[ https://issues.apache.org/jira/browse/KAFKA-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grayson Chao updated KAFKA-2412: Attachment: KAFKA-2412.diff I based the documentation for max.in.flight.requests.per.connection on J

[jira] [Comment Edited] (KAFKA-2412) Documentation bug: Add information for key.serializer and value.serializer to New Producer Config sections

[ https://issues.apache.org/jira/browse/KAFKA-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707159#comment-14707159 ] Grayson Chao edited comment on KAFKA-2412 at 8/21/15 6:00 PM: --

[jira] [Comment Edited] (KAFKA-2412) Documentation bug: Add information for key.serializer and value.serializer to New Producer Config sections

[ https://issues.apache.org/jira/browse/KAFKA-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707159#comment-14707159 ] Grayson Chao edited comment on KAFKA-2412 at 8/21/15 6:01 PM: --

[jira] [Updated] (KAFKA-2412) Documentation bug: Add information for key.serializer and value.serializer to New Producer Config sections

[ https://issues.apache.org/jira/browse/KAFKA-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grayson Chao updated KAFKA-2412: Attachment: (was: KAFKA-2412.diff) > Documentation bug: Add information for key.serializer and v

Re: Review Request 36652: Patch for KAFKA-2351

> On Aug. 21, 2015, 5:57 p.m., Joel Koshy wrote: > > core/src/main/scala/kafka/network/SocketServer.scala, line 264 > > > > > > Thanks for the reference - we currently have this pattern all over the > > place. We ca

[jira] [Updated] (KAFKA-2412) Documentation bug: Add information for key.serializer and value.serializer to New Producer Config sections

[ https://issues.apache.org/jira/browse/KAFKA-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grayson Chao updated KAFKA-2412: Attachment: KAFKA-2412.diff > Documentation bug: Add information for key.serializer and value.serial

[jira] [Updated] (KAFKA-2412) Documentation bug: Add information for key.serializer and value.serializer to New Producer Config sections

[ https://issues.apache.org/jira/browse/KAFKA-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grayson Chao updated KAFKA-2412: Attachment: (was: KAFKA-2412.diff) > Documentation bug: Add information for key.serializer and v

[jira] [Updated] (KAFKA-2412) Documentation bug: Add information for key.serializer and value.serializer to New Producer Config sections

[ https://issues.apache.org/jira/browse/KAFKA-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grayson Chao updated KAFKA-2412: Attachment: KAFKA-2412.diff > Documentation bug: Add information for key.serializer and value.serial

[jira] [Commented] (KAFKA-2412) Documentation bug: Add information for key.serializer and value.serializer to New Producer Config sections

[ https://issues.apache.org/jira/browse/KAFKA-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707174#comment-14707174 ] Grayson Chao commented on KAFKA-2412: - Also, this info https://cwiki.apache.org/confl

Re: is SSL support feature ready to use in kafka-truck branch

Hi Ben, Thank you very much for the information. This is very helpful. One question I have about the listeners and the advertising host and port. Now the listeners can have two host and port for non SSL and SSL. For advertising host and port, how do I specify both for remote client and brokers resp

Re: Review Request 36652: Patch for KAFKA-2351

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36652/#review96069 --- core/src/main/scala/kafka/network/SocketServer.scala (line 264)

Re: Review Request 36652: Patch for KAFKA-2351

> On Aug. 21, 2015, 6:14 p.m., Joel Koshy wrote: > > core/src/main/scala/kafka/network/SocketServer.scala, line 264 > > > > > > Yes that's exactly what we need. Any reason why we shouldn't use > > `NonFatal` as is?

[GitHub] kafka pull request: KAFKA-2457; StackOverflowError during builds

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/157 --- 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-2457) StackOverflowError during builds

[ https://issues.apache.org/jira/browse/KAFKA-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2457: Resolution: Fixed Fix Version/s: 0.8.3 Status: Resolved (was: Patch Available) Is

[jira] [Commented] (KAFKA-2457) StackOverflowError during builds

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

Re: is SSL support feature ready to use in kafka-truck branch

You can have a list of advertised.listeners On Fri, Aug 21, 2015 at 11:09 AM, Qi Xu wrote: > Hi Ben, > Thank you very much for the information. This is very helpful. > One question I have about the listeners and the advertising host and port. > Now the listeners can have two host and port for no

Re: is SSL support feature ready to use in kafka-truck branch

Qi,      yes you can use inter-broker communication over non-ssl(PLAINTEXT)  You can use this config security.inter.broker.protocol by default its PLAINTEXT and make sure you’ve two listeners one is for PLAINTEXT and another one SSL. Thanks,  Harsha On August 21, 2015 at 11:37:09 AM, Gwen Shapi

[jira] [Commented] (KAFKA-2412) Documentation bug: Add information for key.serializer and value.serializer to New Producer Config sections

[ https://issues.apache.org/jira/browse/KAFKA-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707249#comment-14707249 ] Gwen Shapira commented on KAFKA-2412: - Thank you for contributing! Documenting our con

Build failed in Jenkins: Kafka-trunk #595

See Changes: [cshapi] KAFKA-2457; StackOverflowError during builds -- [...truncated 2616 lines...] org.apache.kafka.clients.consumer.internals.HeartbeatTest > testShouldNotHeartbeat PASSED org.apach

Re: Build failed in Jenkins: Kafka-trunk #595

Hmm, looks like something in Jenkins is different than my local setup. Will investigate and submit a follow-up. Ismael On Fri, Aug 21, 2015 at 8:10 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [cshapi

[jira] [Commented] (KAFKA-2457) StackOverflowError during builds

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

[GitHub] kafka pull request: KAFKA-2457; Fix how the argument is passed to ...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/159 KAFKA-2457; Fix how the argument is passed to `compileScala` You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-2457-fix Alternativ

Re: Build failed in Jenkins: Kafka-trunk #595

Looks like I pushed an earlier iteration of the fix to the PR, sorry. Fix: https://github.com/apache/kafka/pull/159 Ismael On 21 Aug 2015 20:31, "Ismael Juma" wrote: > Hmm, looks like something in Jenkins is different than my local setup. > Will investigate and submit a follow-up. > > Ismael >

[GitHub] kafka pull request: KAFKA-2457; Fix how the argument is passed to ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/159 --- 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-2457) StackOverflowError during builds

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

[jira] [Commented] (KAFKA-1877) Expose version via JMX for 'new' producer

[ https://issues.apache.org/jira/browse/KAFKA-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707377#comment-14707377 ] Gwen Shapira commented on KAFKA-1877: - Thanks for updating the status. > Expose versi

Build failed in Jenkins: Kafka-trunk #596

See Changes: [cshapi] KAFKA-2457; Fix how the argument is passed to `compileScala` -- [...truncated 2902 lines...] kafka.integration.PrimitiveApiTest > testConsumerEmptyTopic PASSED kafka.consumer.Me

Re: Review Request 34493: Patch for KAFKA-2211

> On Aug. 21, 2015, 2:31 p.m., Ismael Juma wrote: > > Thanks for this Parth. I did an initial pass where I left a number comments > > (many of them style-related, see http://kafka.apache.org/coding-guide.html > > for reference). I know, we should have a tool that checks some of these > > thing

Re: Review Request 34493: Patch for KAFKA-2211

> On Aug. 21, 2015, 2:31 p.m., Ismael Juma wrote: > > Thanks for this Parth. I did an initial pass where I left a number comments > > (many of them style-related, see http://kafka.apache.org/coding-guide.html > > for reference). I know, we should have a tool that checks some of these > > thing

Re: Review Request 36652: Patch for KAFKA-2351

> On Aug. 21, 2015, 6:14 p.m., Joel Koshy wrote: > > core/src/main/scala/kafka/network/SocketServer.scala, line 264 > > > > > > Yes that's exactly what we need. Any reason why we shouldn't use > > `NonFatal` as is?

[jira] [Assigned] (KAFKA-2442) QuotasTest should not fail when cpu is busy

[ https://issues.apache.org/jira/browse/KAFKA-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Auradkar reassigned KAFKA-2442: -- Assignee: Aditya Auradkar (was: Dong Lin) > QuotasTest should not fail when cpu is bus

[jira] [Commented] (KAFKA-2442) QuotasTest should not fail when cpu is busy

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

[GitHub] kafka pull request: KAFKA-2442: Fixing transiently failing test

GitHub user auradkar opened a pull request: https://github.com/apache/kafka/pull/160 KAFKA-2442: Fixing transiently failing test Made the following changes: 1. Made the quotas very small. (100 and 10 bytes/sec for producer and consumer respectively) 2. For the producer, I'm

[jira] [Commented] (KAFKA-2442) QuotasTest should not fail when cpu is busy

[ https://issues.apache.org/jira/browse/KAFKA-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707492#comment-14707492 ] Aditya Auradkar commented on KAFKA-2442: [~jjkoshy] - Can you take a look? > Quot

[jira] [Updated] (KAFKA-2442) QuotasTest should not fail when cpu is busy

[ https://issues.apache.org/jira/browse/KAFKA-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-2442: -- Reviewer: Joel Koshy will do > QuotasTest should not fail when cpu is busy > --

Re: Review Request 33378: Patch for KAFKA-2136

> On Aug. 21, 2015, 12:13 a.m., Joel Koshy wrote: > > core/src/main/scala/kafka/server/ClientQuotaManager.scala, line 142 > > > > > > any specific reason for this change? recordAndMaybeThrottle returns an int value

Re: Review Request 33378: Patch for KAFKA-2136

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33378/ --- (Updated Aug. 21, 2015, 11:29 p.m.) Review request for kafka, Joel Koshy and Ju

[jira] [Updated] (KAFKA-2136) Client side protocol changes to return quota delays

[ https://issues.apache.org/jira/browse/KAFKA-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya A Auradkar updated KAFKA-2136: - Attachment: KAFKA-2136_2015-08-21_16:29:17.patch > Client side protocol changes to return

[jira] [Commented] (KAFKA-2136) Client side protocol changes to return quota delays

[ https://issues.apache.org/jira/browse/KAFKA-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707637#comment-14707637 ] Aditya A Auradkar commented on KAFKA-2136: -- Updated reviewboard https://reviews.a

Re: Review Request 33378: Patch for KAFKA-2136

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33378/ --- (Updated Aug. 21, 2015, 11:30 p.m.) Review request for kafka, Joel Koshy and Ju

[jira] [Updated] (KAFKA-1811) ensuring registered broker host:port is unique

[ https://issues.apache.org/jira/browse/KAFKA-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Ribeiro updated KAFKA-1811: -- Attachment: KAFKA-1811-2.patch A tentative (git) patch cut for addressing this issue. > ensurin

Re: is SSL support feature ready to use in kafka-truck branch

Hi Harsha,Ben, Thanks for your help. With advertised.listeners specified, it works perfect. Qi On Fri, Aug 21, 2015 at 11:46 AM, Sriharsha Chintalapani wrote: > Qi, > yes you can use inter-broker communication over non-ssl(PLAINTEXT) > You can use this config security.inter.broker.protocol

Re: Review Request 33378: Patch for KAFKA-2136

> On Aug. 21, 2015, 12:13 a.m., Joel Koshy wrote: > > core/src/main/scala/kafka/api/FetchResponse.scala, line 175 > > > > > > Since (in the event of multiple calls) this grouping would be repeated, > > should we ju

Re: Review Request 33378: Patch for KAFKA-2136

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/33378/#review96100 --- clients/src/main/java/org/apache/kafka/common/requests/FetchRespons

[GitHub] kafka pull request: KAFKA-1543; Changing replication factor

GitHub user apakulov opened a pull request: https://github.com/apache/kafka/pull/161 KAFKA-1543; Changing replication factor Adding support to change replication-factor via kafka-topics to avoid additional hassle of defining replicas explicilty. This change will allow to make this

[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=14707713#comment-14707713 ] ASF GitHub Bot commented on KAFKA-1543: --- GitHub user apakulov opened a pull request: