Re: Snazzy new look to our website

Big improvement, it looks much better ! I noticed the Javadoc links in the API section on the documentation page seem to be broken On Wed, Oct 5, 2016 at 10:58 PM, Avi Flax wrote: > >> On Oct 4, 2016, at 19:38, Guozhang Wang wrote: >> >> The new

[GitHub] kafka pull request #1977: HOTFIX: Cannot Stop Kafka with Shell Script (Solut...

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

[GitHub] kafka pull request #1978: HOTFIX: Cannot Stop Kafka with Shell Script (Solut...

GitHub user Mabin-J opened a pull request: https://github.com/apache/kafka/pull/1978 HOTFIX: Cannot Stop Kafka with Shell Script (Solution 2) If Kafka's homepath is long, kafka cannot stop with 'kafka-server-stop.sh'. That command showed this message: ``` No kafka

[GitHub] kafka pull request #1979: KAFKA-4259: Dynamic JAAS configuration for Kafka c...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/1979 KAFKA-4259: Dynamic JAAS configuration for Kafka clients Implementation of KIP-85: https://cwiki.apache.org/confluence/display/KAFKA/KIP-85%3A+Dynamic+JAAS+configuration+for+Kafka+clients

[jira] [Commented] (KAFKA-4259) Enable JAAS configuration for Kafka clients without a config file

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

[jira] [Created] (KAFKA-4260) Improve documentation of configuration listeners=PLAINTEXT://0.0.0.0:9092

Michal Turek created KAFKA-4260: --- Summary: Improve documentation of configuration listeners=PLAINTEXT://0.0.0.0:9092 Key: KAFKA-4260 URL: https://issues.apache.org/jira/browse/KAFKA-4260 Project: Kafka

[jira] [Created] (KAFKA-4259) Enable JAAS configuration for Kafka clients without a config file

Rajini Sivaram created KAFKA-4259: - Summary: Enable JAAS configuration for Kafka clients without a config file Key: KAFKA-4259 URL: https://issues.apache.org/jira/browse/KAFKA-4259 Project: Kafka

[jira] [Created] (KAFKA-4258) Page not found http://kafka.apache.org/streams.html

Andrey Dyachkov created KAFKA-4258: -- Summary: Page not found http://kafka.apache.org/streams.html Key: KAFKA-4258 URL: https://issues.apache.org/jira/browse/KAFKA-4258 Project: Kafka Issue

Re: [DISCUSS] KIP-82 - Add Record Headers

Hi All, We have updated a sample version of an implementation of the KIP with Integer,Byte[] headers to aid discussion. See: https://github.com/michaelandrepearce/kafka/tree/headers On the kip there are a few outstanding bits that I would like to have discussed and get some majority consensus

[jira] [Updated] (KAFKA-4259) Enable JAAS configuration for Kafka clients without a config file

[ https://issues.apache.org/jira/browse/KAFKA-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4259: -- Description: See KIP-85 for details:

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

Hi all, I have just created KIP-85 to enable JAAS login context for Kafka clients to be configured without a physical file: https://cwiki.apache.org/confluence/display/KAFKA/KIP-85%3A+Dynamic+JAAS+configuration+for+Kafka+clients Comments and suggestions are welcome. Thank you... Regards,

[jira] [Commented] (KAFKA-4252) Missing ProducerRequestPurgatory

[ https://issues.apache.org/jira/browse/KAFKA-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551696#comment-15551696 ] Rajini Sivaram commented on KAFKA-4252: --- I think the documentation was not updated when the class

[jira] [Commented] (KAFKA-4260) Improve documentation of configuration listeners=PLAINTEXT://0.0.0.0:9092

[ https://issues.apache.org/jira/browse/KAFKA-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551925#comment-15551925 ] David Watzke commented on KAFKA-4260: - Also quite disturbing was the fact that there was no relevant

Issue while closing consumer

hi , I have an issue in kafka..I am using inbound channel adapter for spring kafka in kafka consumer consumer code.when i undeploy my consumer application ..i tried to close the adapter but it is still consuming messages even if it is undeployed .it does not stop consuming messages

[jira] [Commented] (KAFKA-3544) Missing topics on startup

[ https://issues.apache.org/jira/browse/KAFKA-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552065#comment-15552065 ] Mykola Polonskyi commented on KAFKA-3544: - [~guozhang] greetings! My comment a bit late but I

[jira] [Created] (KAFKA-4262) Intermittent unit test failure ReassignPartitionsClusterTest.shouldExecuteThrottledReassignment

Rajini Sivaram created KAFKA-4262: - Summary: Intermittent unit test failure ReassignPartitionsClusterTest.shouldExecuteThrottledReassignment Key: KAFKA-4262 URL: https://issues.apache.org/jira/browse/KAFKA-4262

[GitHub] kafka pull request #1980: KAFKA-4252: Fix metric name in documentation

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/1980 KAFKA-4252: Fix metric name in documentation You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka KAFKA-4252

[jira] [Commented] (KAFKA-4252) Missing ProducerRequestPurgatory

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

[jira] [Commented] (KAFKA-4261) Provide debug option in vagrant-up.sh

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

[jira] [Assigned] (KAFKA-4252) Missing ProducerRequestPurgatory

[ https://issues.apache.org/jira/browse/KAFKA-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-4252: - Assignee: Rajini Sivaram > Missing ProducerRequestPurgatory >

Re: [DISCUSS] KIP-80: Kafka REST Server

I also think it would be good to have a REST client that can interact with the new management API's coming down the pipe. On Tue, Oct 4, 2016 at 10:35 PM, Edoardo Comar wrote: > Harsha > thanks for opening the discussion on this KIP. > > While I understand he founding

[jira] [Updated] (KAFKA-4253) Fix Kafka Stream thread shutting down process ordering

[ https://issues.apache.org/jira/browse/KAFKA-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4253: -- Status: Patch Available (was: In Progress) > Fix Kafka Stream thread shutting down process ordering >

[GitHub] kafka pull request #1981: KAFKA-4261: Provide debug option in vagrant-up.sh

GitHub user fpj opened a pull request: https://github.com/apache/kafka/pull/1981 KAFKA-4261: Provide debug option in vagrant-up.sh You can merge this pull request into a Git repository by running: $ git pull https://github.com/fpj/kafka vagrant-debug-option Alternatively you

[jira] [Updated] (KAFKA-4252) Missing ProducerRequestPurgatory

[ https://issues.apache.org/jira/browse/KAFKA-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4252: -- Status: Patch Available (was: Open) > Missing ProducerRequestPurgatory >

[jira] [Commented] (KAFKA-3302) Pass kerberos keytab and principal as part of client config

[ https://issues.apache.org/jira/browse/KAFKA-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551821#comment-15551821 ] Edoardo Comar commented on KAFKA-3302: -- looks like [~rsivaram]'s

[GitHub] kafka pull request #1974: AN-75711 Spike for Kafka server side changes to pr...

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

[jira] [Assigned] (KAFKA-4261) Provide debug option in vagrant-up.sh

[ https://issues.apache.org/jira/browse/KAFKA-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Junqueira reassigned KAFKA-4261: --- Assignee: Flavio Junqueira > Provide debug option in vagrant-up.sh >

[jira] [Created] (KAFKA-4261) Provide debug option in vagrant-up.sh

Flavio Junqueira created KAFKA-4261: --- Summary: Provide debug option in vagrant-up.sh Key: KAFKA-4261 URL: https://issues.apache.org/jira/browse/KAFKA-4261 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-4264) kafka-server-stop.sh fails is Kafka launched via kafka-server-start.sh

[ https://issues.apache.org/jira/browse/KAFKA-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552637#comment-15552637 ] Alex Schmitz commented on KAFKA-4264: - Pull request with fix here:

[jira] [Commented] (KAFKA-4264) kafka-server-stop.sh fails is Kafka launched via kafka-server-start.sh

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

[GitHub] kafka-site pull request #23: Grammar updated

GitHub user muehlburger opened a pull request: https://github.com/apache/kafka-site/pull/23 Grammar updated Just a little grammar update. You can merge this pull request into a Git repository by running: $ git pull https://github.com/muehlburger/kafka-site asf-site

[GitHub] kafka-site pull request #22: fix issue with rewrite rules blocking access to...

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

Re: [DISCUSS] KIP-82 - Add Record Headers

1. tending towards no, but I dont have any strong opinions on header ordering. it offers a potential speedup for header lookup in a serialized blob (in wire format) but that goes away if the headers are fully serialized/deserialized always. on the downside its an implementation detail that 3rd

Re: [DISCUSS] KIP-82 - Add Record Headers

+1 Nacho, Radai. Ordering the Keys would help if we were gonna look at the headers linearly but given the disadvantage that the client implementations have to know the order of headers in order that the reading system in the pipeline doesn't break, unordered list sounds better. Thanks, Mayuresh

Re: [DISCUSS] KIP-82 - Add Record Headers

I'm also 1. no (ordered keys) 2. yes (propose key space) 1. I don't think there is going to be much savings in ordering the keys. I'm assuming some parsing will happen either way. Ordering the keys would be useful if we were doing linear search on the headers, and even then, the performance

Build failed in Jenkins: kafka-0.10.1-jdk7 #50

See Changes: [jason] KAFKA-4252; Fix purgatory metric name in documentation -- [...truncated 3797 lines...] kafka.admin.ReassignPartitionsCommandArgsTest >

Re: Snazzy new look to our website

Thanks Mickael and Jonathon for reporting the problem with the javdocs. The links should be fixed now. -Jason On Thu, Oct 6, 2016 at 10:59 AM, Jonathan Bond wrote: > Hi, > > I'm having a problem with the new website. Whenever I try to follow a link > to the Kafka

[jira] [Commented] (KAFKA-4254) Questionable handling of unknown partitions in KafkaProducer

[ https://issues.apache.org/jira/browse/KAFKA-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15553228#comment-15553228 ] Joel Koshy commented on KAFKA-4254: --- It seems (2) would still help as there are use-cases which set

[jira] [Commented] (KAFKA-4254) Questionable handling of unknown partitions in KafkaProducer

[ https://issues.apache.org/jira/browse/KAFKA-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15553410#comment-15553410 ] Jason Gustafson commented on KAFKA-4254: [~jjkoshy] Yeah, good point. > Questionable handling of

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

See Changes: [jason] MINOR: Clarify 0.10.1.0 upgrade docs [wangguoz] KAFKA-4253: Fix Kafka Stream thread shutting down process ordering -- [...truncated 2403 lines...] at

[GitHub] kafka pull request #1984: mods grep target to find kafka process, fixes KAFK...

GitHub user davemcphee opened a pull request: https://github.com/apache/kafka/pull/1984 mods grep target to find kafka process, fixes KAFKA-4264 Fixes issue described here: https://issues.apache.org/jira/browse/KAFKA-4264 You can merge this pull request into a Git repository by

Re: [DISCUSS] KIP-82 - Add Record Headers

@Mayuresh Yes exactly, it is a real nasty race issue. This is why I look forward to being able to trash our custom workaround :) Kostya 06.10.2016, 02:36, "Mayuresh Gharat" : > @Kostya > > Regarding "To get around this we have an awful *cough* solution whereby we >

Build failed in Jenkins: kafka-0.10.1-jdk7 #49

See Changes: [jason] MINOR: Clarify 0.10.1.0 upgrade docs [wangguoz] KAFKA-4253: Fix Kafka Stream thread shutting down process ordering -- [...truncated 7449 lines...]

[jira] [Commented] (KAFKA-3370) Add options to auto.offset.reset to reset offsets upon initialization only

[ https://issues.apache.org/jira/browse/KAFKA-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15553047#comment-15553047 ] Marcin Kuthan commented on KAFKA-3370: -- As I understand we need two separate properties:

[jira] [Assigned] (KAFKA-4254) Questionable handling of unknown partitions in KafkaProducer

[ https://issues.apache.org/jira/browse/KAFKA-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantine Karantasis reassigned KAFKA-4254: - Assignee: Konstantine Karantasis (was: Jason Gustafson) > Questionable

[GitHub] kafka pull request #1980: KAFKA-4252: Fix metric name in documentation

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1980 --- 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-4252) Missing ProducerRequestPurgatory

[ https://issues.apache.org/jira/browse/KAFKA-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4252: --- Resolution: Fixed Fix Version/s: 0.10.1.0 Status: Resolved (was: Patch

[jira] [Commented] (KAFKA-4252) Missing ProducerRequestPurgatory

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

[jira] [Commented] (KAFKA-3370) Add options to auto.offset.reset to reset offsets upon initialization only

[ https://issues.apache.org/jira/browse/KAFKA-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15553085#comment-15553085 ] Cody Koeninger commented on KAFKA-3370: --- Throwing an exception should be the default IMHO. Silent

[GitHub] kafka pull request #1667: KAFKA-3993 Console Producer Drops Data

Github user theduderog closed the pull request at: https://github.com/apache/kafka/pull/1667 --- 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-3993) Console producer drops data

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

Re: Snazzy new look to our website

Hi, I'm having a problem with the new website. Whenever I try to follow a link to the Kafka javadoc, either from within the website or a google link - it always takes me to the top of the Kafka 0.10 documentation page. I can't figure out how to get to the javadoc. Thanks, Jonathan On Tue, Oct

[jira] [Updated] (KAFKA-4253) Fix Kafka Stream thread shutting down process ordering

[ https://issues.apache.org/jira/browse/KAFKA-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4253: - Resolution: Fixed Fix Version/s: 0.10.1.1 0.10.2.0 Status:

[GitHub] kafka pull request #1970: KAFKA-4253: Fix Kafka Stream thread shutting down ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1970 --- 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-4253) Fix Kafka Stream thread shutting down process ordering

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

Re: [DISCUSS] KIP-80: Kafka REST Server

Hi Manikumar, I agree totally agree that REST is important. What I don't understand is why we'd duplicate the existing REST interface inside the Kafka project. That seems to needlessly fragment things. -Jay On Sat, Oct 1, 2016 at 5:38 AM, Manikumar wrote: > Hi Jay,

[jira] [Created] (KAFKA-4263) QueryableStateIntegrationTest.concurrentAccess is failing occasionally in jenkins builds

Damian Guy created KAFKA-4263: - Summary: QueryableStateIntegrationTest.concurrentAccess is failing occasionally in jenkins builds Key: KAFKA-4263 URL: https://issues.apache.org/jira/browse/KAFKA-4263

Build failed in Jenkins: kafka-trunk-jdk7 #1606

See Changes: [jason] KAFKA-4252; Fix purgatory metric name in documentation -- [...truncated 2425 lines...] kafka.api.AdminClientTest > testDescribeConsumerGroup STARTED

Re: [VOTE] 0.10.1.0 RC0

Jason, Thanks a lot for managing this release. I ran the quick start (Steps 2-8) with this release candidate on Ubuntu, Windows, and Mac and they mostly look great. These are some, hopefully, minor items and gaps I noticed with respect to the existing quick start documentation (and the updated

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

See Changes: [jason] KAFKA-4252; Fix purgatory metric name in documentation -- [...truncated 14069 lines...] org.apache.kafka.streams.processor.internals.assignment.TaskAssignorTest >

Re: [VOTE] 0.10.1.0 RC0

Why is this feature in the release note? - [KAFKA-264 ] - Change the consumer side load balancing and distributed co-ordination to use a consumer co-ordinator I thought this was already done in 2015. On Thu, Oct 6, 2016 at 4:55 PM,

[GitHub] kafka pull request #1985: MINOR: A bunch of clean-ups related to usage of un...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1985 MINOR: A bunch of clean-ups related to usage of unused variables There should be only 2 cases where these clean-ups have a functional impact: 1. Fix a bug in the newly introduced

Re: [DISCUSS] KIP-82 - Add Record Headers

+1 Nacho, Radai, Mayuresh 1) yes for unordered keys. Given the expected number of headers is not that high linear searching is ok. The overhead of ordering and the dependence on client implementations makes it error prone. 2) yes on proposed key space. Adding structure makes it easier to manage

[jira] [Commented] (KAFKA-4262) Intermittent unit test failure ReassignPartitionsClusterTest.shouldExecuteThrottledReassignment

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

[GitHub] kafka pull request #1982: KAFKA-4262: Increase data volume in replication te...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/1982 KAFKA-4262: Increase data volume in replication test To prevent test from completing without throttling before config change takes effect, produce more messages in the test. You can merge

Re: [DISCUSS] KIP-83 - Allow multiple SASL PLAIN authenticated Java clients in a single JVM process

HI after Rajini's excellent KIP-85 I am no longer sure KIP-83 needs to exist as is. Building on top of KIP-85, all it takes to achieve KIP-83 goal is to change the caching of LoginManager on the client side. For example using the new sasl.jaas.config value as the key. This should solve both

[GitHub] kafka pull request #1971: MINOR: Clarify 0.10.1.0 upgrade docs

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

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

Hi Rajini great improvement and I see you had the code ready ... ! I now think it'd easier to implement a PR for KIP-83 (multiple logins per JVM) on top of yours, as you have now identified a client property that can be used for caching logins. I'm actually wondering if I caused you to cut

Re: [DISCUSS] KIP-80: Kafka REST Server

I personally think it would be quite wasteful to re-implement the REST gateway just because that an actively-maintained piece of Apache-licensed software is not governed directly by the Apache Kafka community... While kafka-rest repo is owned by Confluent, the contributors including the main one

[GitHub] kafka pull request #1983: client fails trying to bind to jmx port already in...

GitHub user edi-bice opened a pull request: https://github.com/apache/kafka/pull/1983 client fails trying to bind to jmx port already in use by server Enabling JMX_PORT causes Kafka clients to attempt to bind to a port already bound by server. Modified so as to distinguish if being