[jira] [Commented] (KAFKA-4104) Queryable state metadata is sometimes invalid

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

[jira] [Updated] (KAFKA-4104) Queryable state metadata is sometimes invalid

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

[GitHub] kafka pull request #1804: KAFKA-4104: Queryable state metadata is sometimes ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1804 --- 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 #1815: KAFKA-4115: grow default heap size for connect-dis...

GitHub user shikhar opened a pull request: https://github.com/apache/kafka/pull/1815 KAFKA-4115: grow default heap size for connect-distributed.sh to 1G You can merge this pull request into a Git repository by running: $ git pull https://github.com/shikhar/kafka

[jira] [Commented] (KAFKA-4115) Grow default heap settings for distributed Connect from 256M to 1G

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

[jira] [Created] (KAFKA-4115) Grow default heap settings for distributed Connect from 256M to 1G

Shikhar Bhushan created KAFKA-4115: -- Summary: Grow default heap settings for distributed Connect from 256M to 1G Key: KAFKA-4115 URL: https://issues.apache.org/jira/browse/KAFKA-4115 Project: Kafka

[GitHub] kafka pull request #1814: MINOR: doc fix related to monitoring consumer lag.

GitHub user alexlod opened a pull request: https://github.com/apache/kafka/pull/1814 MINOR: doc fix related to monitoring consumer lag. You can merge this pull request into a Git repository by running: $ git pull https://github.com/alexlod/kafka consumer-lag-doc-fix

[jira] [Comment Edited] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456584#comment-15456584 ] Vahid Hashemian edited comment on KAFKA-3144 at 9/2/16 12:44 AM: -

[jira] [Commented] (KAFKA-3148) SslSelectorTest.testRenegotiation can hang on slow boxes

[ https://issues.apache.org/jira/browse/KAFKA-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457099#comment-15457099 ] Ashish K Singh commented on KAFKA-3148: --- [~revans2] since you have figured out the issue, do you

[GitHub] kafka pull request #1813: make mirror maker threads daemons and make sure an...

GitHub user radai-rosenblatt opened a pull request: https://github.com/apache/kafka/pull/1813 make mirror maker threads daemons and make sure any uncaught exceptions are logged You can merge this pull request into a Git repository by running: $ git pull

[jira] [Updated] (KAFKA-4099) Change the time based log rolling to only based on the message timestamp.

[ https://issues.apache.org/jira/browse/KAFKA-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4099: Status: Patch Available (was: Open) > Change the time based log rolling to only based on the

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

See Changes: [wangguoz] KAFKA-4112: Remove alpha quality label from Kafka Streams in docs -- [...truncated 4698 lines...] kafka.admin.AdminRackAwareTest > testMoreReplicasThanRacks STARTED

[jira] [Commented] (KAFKA-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456866#comment-15456866 ] James Cheng commented on KAFKA-4113: I wrote a blog post on some other ways to know when you have read

Build failed in Jenkins: kafka-0.10.0-jdk7 #198

See Changes: [wangguoz] KAFKA-4112: Remove alpha quality label from Kafka Streams in docs -- [...truncated 5748 lines...] org.apache.kafka.streams.kstream.internals.KStreamForeachTest >

Jenkins build is back to normal : kafka-trunk-jdk7 #1513

See

[jira] [Comment Edited] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456584#comment-15456584 ] Vahid Hashemian edited comment on KAFKA-3144 at 9/1/16 8:56 PM: [~junrao]

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456584#comment-15456584 ] Vahid Hashemian commented on KAFKA-3144: [~junrao] How do you think the consumer group coordinator

Re: [DISCUSS] Remove beta label from the new Java consumer

Hey Harsha, I'm trying to understand your specific concern. Is it the fact that the client cannot tell the difference between non-existing topic and hence needlessly retries (instead of perhaps raising an error). Or is it specifically that in some cases, the consumer will block because of this?

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

See Changes: [me] KAFKA-4077: Backdate system test certificates to cope with clock skew -- [...truncated 12207 lines...] org.apache.kafka.streams.kstream.JoinWindowsTest > validWindows STARTED

[jira] [Resolved] (KAFKA-4112) Remove alpha quality label from Kafka Streams in docs

[ https://issues.apache.org/jira/browse/KAFKA-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4112. -- Resolution: Fixed Fix Version/s: 0.10.0.2 0.10.1.0 > Remove alpha

[jira] [Commented] (KAFKA-4112) Remove alpha quality label from Kafka Streams in docs

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

[GitHub] kafka pull request #1811: KAFKA-4112: Remove alpha quality label from Kafka ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1811 --- 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-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456332#comment-15456332 ] Matthias J. Sax commented on KAFKA-4113: Two things to add. (1) prioritizing smaller timestamps in

[jira] [Issue Comment Deleted] (KAFKA-3478) Finer Stream Flow Control

[ https://issues.apache.org/jira/browse/KAFKA-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3478: --- Comment: was deleted (was: [~bbejeck] I just created

[jira] [Commented] (KAFKA-3199) LoginManager should allow using an existing Subject

[ https://issues.apache.org/jira/browse/KAFKA-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456314#comment-15456314 ] Alejandro Abdelnur commented on KAFKA-3199: --- [~sriharsha], thanks for you quick reply.

[jira] [Commented] (KAFKA-3478) Finer Stream Flow Control

[ https://issues.apache.org/jira/browse/KAFKA-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456311#comment-15456311 ] Matthias J. Sax commented on KAFKA-3478: [~bbejeck] I just created

[jira] [Commented] (KAFKA-3478) Finer Stream Flow Control

[ https://issues.apache.org/jira/browse/KAFKA-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456310#comment-15456310 ] Matthias J. Sax commented on KAFKA-3478: [~bbejeck] I just created

[jira] [Comment Edited] (KAFKA-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456296#comment-15456296 ] Jay Kreps edited comment on KAFKA-4113 at 9/1/16 6:52 PM: -- Don't you get this

[jira] [Created] (KAFKA-4114) Allow for different "auto.offset.reset" strategies for different input streams

Matthias J. Sax created KAFKA-4114: -- Summary: Allow for different "auto.offset.reset" strategies for different input streams Key: KAFKA-4114 URL: https://issues.apache.org/jira/browse/KAFKA-4114

[jira] [Comment Edited] (KAFKA-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456296#comment-15456296 ] Jay Kreps edited comment on KAFKA-4113 at 9/1/16 6:51 PM: -- Don't you get this

Re: [DISCUSS] KIP-78: Cluster Id

Hey Ismael, Thanks for the KIP. I share the view with Harsha and would like to understand how the current approach of randomly generating cluster.id compares with the approach of manually specifying it in meta.properties. I think one big advantage of defining it manually in zookeeper is that we

[jira] [Commented] (KAFKA-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456296#comment-15456296 ] Jay Kreps commented on KAFKA-4113: -- Don't you get this naturally out of the message timestamps and the

[jira] [Created] (KAFKA-4113) Allow KTable bootstrap

Matthias J. Sax created KAFKA-4113: -- Summary: Allow KTable bootstrap Key: KAFKA-4113 URL: https://issues.apache.org/jira/browse/KAFKA-4113 Project: Kafka Issue Type: Sub-task

Re: PartitionAssignor / Sort members per subscription time before assigning partitions

Hi Florian, I'm not totally sure I understand the problem. The consumer id consists of the clientId configured by the user with a UUID appended to it. If the clientId has not been passed in configuration, we use "consumer-{n}" for it where n is incremented for every new consumer instance. Is the

Re: [DISCUSS] Remove beta label from the new Java consumer

I would like to see we address https://issues.apache.org/jira/browse/KAFKA-1894 . This is problematic in secure cluster when the users try to access the topics that they don't have ACLs turned on. -Harsha On Tue, Aug 30, 2016 at 9:40 PM Jaikiran Pai wrote: > We have

[jira] [Commented] (KAFKA-3199) LoginManager should allow using an existing Subject

[ https://issues.apache.org/jira/browse/KAFKA-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456228#comment-15456228 ] Sriharsha Chintalapani commented on KAFKA-3199: --- [~tucu00] HADOOP-13558 is not relevant

[jira] [Commented] (KAFKA-3199) LoginManager should allow using an existing Subject

[ https://issues.apache.org/jira/browse/KAFKA-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456209#comment-15456209 ] Alejandro Abdelnur commented on KAFKA-3199: --- [~sriharsha], if the {{Subject}} was given to the

[jira] [Resolved] (KAFKA-4106) Consumer / add configure method to PartitionAssignor interface

[ https://issues.apache.org/jira/browse/KAFKA-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-4106. Resolution: Resolved Assignee: Jason Gustafson The requested functionality already

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

See Changes: [me] KAFKA-4077: Backdate system test certificates to cope with clock skew -- [...truncated 4906 lines...] kafka.network.SocketServerTest > tooBigRequestIsRejected STARTED

Re: [DISCUSS] KIP-78: Cluster Id

Hi Jun, Thanks for the feedback. Using `Cluster` was appealing because it has the information we need and it is already a public class, so we would not need to introduce a new public class with a potentially confusing name. Having said that, I agree with your points and I have updated the KIP so

[jira] [Commented] (KAFKA-4077) Backdate validity of certificates in system tests to cope with clock skew

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

[jira] [Updated] (KAFKA-4077) Backdate validity of certificates in system tests to cope with clock skew

[ https://issues.apache.org/jira/browse/KAFKA-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4077: - Resolution: Fixed Fix Version/s: 0.10.1.0 Status: Resolved

[GitHub] kafka pull request #1810: KAFKA-4077: Backdate system test certificates to c...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1810 --- 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 #1812: KIP-74: Add Fetch Response Size Limit in Bytes (KI...

GitHub user nepal opened a pull request: https://github.com/apache/kafka/pull/1812 KIP-74: Add Fetch Response Size Limit in Bytes (KIP-74) [WIP] This PR is incomplete implementation of

PartitionAssignor / Sort members per subscription time before assigning partitions

Hi Kafka Team, I would like to have your opinion before creating a new JIRA. I'm working with the Java Consumer API. The current partition assignors use the consumer ids to sort members before assigning partitions. This works pretty well as long as all consumers are started into the same JVM

[jira] [Assigned] (KAFKA-3708) Rethink exception handling in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-3708: - Assignee: Damian Guy > Rethink exception handling in KafkaStreams >

[jira] [Created] (KAFKA-4112) Remove alpha quality label from Kafka Streams in docs

Damian Guy created KAFKA-4112: - Summary: Remove alpha quality label from Kafka Streams in docs Key: KAFKA-4112 URL: https://issues.apache.org/jira/browse/KAFKA-4112 Project: Kafka Issue Type:

Re: [VOTE] KIP-33 - Add a time based log index

Sounds good to me too. For completeness, one thing that is mentioned in the JIRA but not in the message below is: "If the first message in the segment does not have a timetamp, we will fall back to use the wall clock time for log rolling". Ismael On Wed, Aug 31, 2016 at 7:59 PM, Guozhang Wang

WIKI page outdated

Hello Mates, I may be reiterating the previously identified issue here so please forgive me if you find it noisy. The page : https://cwiki.apache.org/confluence/display/KAFKA/0.8.0+Producer+Example# is having Producer example which is seems to be outdated but having "partitioner.class" property

[jira] [Updated] (KAFKA-4111) broker compress data of certain size instead on a produce request

[ https://issues.apache.org/jira/browse/KAFKA-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] julien1987 updated KAFKA-4111: -- Summary: broker compress data of certain size instead on a produce request (was: broker compress data

[jira] [Created] (KAFKA-4111) broker compress data on certain size instead on a produce request

julien1987 created KAFKA-4111: - Summary: broker compress data on certain size instead on a produce request Key: KAFKA-4111 URL: https://issues.apache.org/jira/browse/KAFKA-4111 Project: Kafka

Re: Message sent ordering guarantees

For async you could set ack to -1, but it keep slow, because it has to wait for the broker(s), to know it is received in order, before sending the next one, you need this if order is very important. When sending async the order gets changed in case the leader becomes temporarily unavailable and

[jira] [Commented] (KAFKA-4106) Consumer / add configure method to PartitionAssignor interface

[ https://issues.apache.org/jira/browse/KAFKA-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15454817#comment-15454817 ] Florian Hussonnois commented on KAFKA-4106: --- Thank you very much, sorry to have created this

[jira] [Updated] (KAFKA-4110) When running multiple Kafka instances, the stop script kills all running instances

[ https://issues.apache.org/jira/browse/KAFKA-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Callewaert updated KAFKA-4110: -- Attachment: my-kafka-server-stop.sh Attached an update to the stop script which uses the path

[jira] [Created] (KAFKA-4110) When running multiple Kafka instances, the stop script kills all running instances

Jan Callewaert created KAFKA-4110: - Summary: When running multiple Kafka instances, the stop script kills all running instances Key: KAFKA-4110 URL: https://issues.apache.org/jira/browse/KAFKA-4110

[GitHub] kafka pull request #1811: MINOR: rephrase alpha quality kafka streams wordin...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/1811 MINOR: rephrase alpha quality kafka streams wording Rephrase 'alpha quality' wording in Streams section of api.html. Couple of other minor fixes in streams.html You can merge this pull request

[jira] [Updated] (KAFKA-4077) Backdate validity of certificates in system tests to cope with clock skew

[ https://issues.apache.org/jira/browse/KAFKA-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-4077: -- Status: Patch Available (was: Open) > Backdate validity of certificates in system tests to

[jira] [Commented] (KAFKA-4077) Backdate validity of certificates in system tests to cope with clock skew

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

[GitHub] kafka pull request #1810: KAFKA-4077: Backdate system test certificates to c...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/1810 KAFKA-4077: Backdate system test certificates to cope with clock skew You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka

[GitHub] kafka pull request #1780: Kafka 4077: Backdate system test certificates to c...

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