[jira] [Updated] (KAFKA-3748) Add consumer-property to console tools consumer (similar to --producer-property)

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

[jira] [Created] (KAFKA-3798) Kafka Consumer 0.10.0.0 killed after rebalancing exception

Sahitya Agrawal created KAFKA-3798: -- Summary: Kafka Consumer 0.10.0.0 killed after rebalancing exception Key: KAFKA-3798 URL: https://issues.apache.org/jira/browse/KAFKA-3798 Project: Kafka

[jira] [Commented] (KAFKA-3480) Autogenerate metrics documentation

[ https://issues.apache.org/jira/browse/KAFKA-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317992#comment-15317992 ] James Cheng commented on KAFKA-3480: Pinging [~gwenshap] and [~hachikuji] for feedback

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

See Changes: [me] KAFKA-3501: Console consumer process hangs on exit -- [...truncated 6524 lines...] kafka.security.auth.SimpleAclAuthorizerTest > testLoadCache PASSED kafka.integration.SaslPla

[jira] [Commented] (KAFKA-3793) Kafka Python Consumer library messages gets truncated

[ https://issues.apache.org/jira/browse/KAFKA-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317929#comment-15317929 ] Ewen Cheslack-Postava commented on KAFKA-3793: -- [~rgo...@threatmetrix.com] Ca

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

See Changes: [me] KAFKA-3781; Errors.exceptionName() can throw NPE -- [...truncated 5628 lines...] org.apache.kafka.streams.kstream.internals.KTableForeachTest > testForeach PASSED org.apache.

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

See

[jira] [Commented] (KAFKA-3797) Improve security of __consumer_offsets topic

[ https://issues.apache.org/jira/browse/KAFKA-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317835#comment-15317835 ] Vahid Hashemian commented on KAFKA-3797: [~hachikuji] I can take this on if you do

[GitHub] kafka pull request #1185: KAFKA-3501: Console consumer process hangs on exit

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

[jira] [Commented] (KAFKA-3501) Console consumer process hangs on SIGINT

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

[jira] [Updated] (KAFKA-3501) Console consumer process hangs on SIGINT

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

[jira] [Created] (KAFKA-3797) Improve security of __consumer_offsets topic

Jason Gustafson created KAFKA-3797: -- Summary: Improve security of __consumer_offsets topic Key: KAFKA-3797 URL: https://issues.apache.org/jira/browse/KAFKA-3797 Project: Kafka Issue Type: Im

[jira] [Commented] (KAFKA-3796) SslTransportLayerTest.testInvalidEndpointIdentification fails on trunk

[ https://issues.apache.org/jira/browse/KAFKA-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317764#comment-15317764 ] Ismael Juma commented on KAFKA-3796: Does this happen consistently on your computer?

[jira] [Commented] (KAFKA-3781) Errors.exceptionName() can throw NPE

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

[GitHub] kafka pull request #1476: KAFKA-3781; Errors.exceptionName() can throw NPE

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

[jira] [Updated] (KAFKA-3781) Errors.exceptionName() can throw NPE

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

[jira] [Commented] (KAFKA-3443) Support regex topics in addSource() and stream()

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

[GitHub] kafka pull request #1477: KAFKA-3443 [Kafka Stream] support for adding sourc...

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/1477 KAFKA-3443 [Kafka Stream] support for adding sources to KafkaStreams via Pattern This PR is the follow on to the closed PR #1410. You can merge this pull request into a Git repository by running:

Re: [DISCUSS] KIP-54 Sticky Partition Assignment Strategy

Hi Vahid, The only thing I added was the specification of the UserData field. The rest comes from here: https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol. See the section on the JoinGroup request. Generally speaking, I think having fewer assignment strategies include

[jira] [Updated] (KAFKA-3248) AdminClient Blocks Forever in send Method

[ https://issues.apache.org/jira/browse/KAFKA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3248: --- Resolution: Fixed Status: Resolved (was: Patch Available) This was fixed via KAFKA-3488. > A

[jira] [Updated] (KAFKA-3248) AdminClient Blocks Forever in send Method

[ https://issues.apache.org/jira/browse/KAFKA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3248: --- Fix Version/s: (was: 0.10.0.1) 0.10.0.0 > AdminClient Blocks Forever in send Me

[jira] [Updated] (KAFKA-2720) Periodic purging groups in the coordinator

[ https://issues.apache.org/jira/browse/KAFKA-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2720: --- Reviewer: Guozhang Wang > Periodic purging groups in the coordinator > ---

[jira] [Updated] (KAFKA-2720) Periodic purging groups in the coordinator

[ https://issues.apache.org/jira/browse/KAFKA-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2720: --- Status: Patch Available (was: Open) > Periodic purging groups in the coordinator > --

[jira] [Commented] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317726#comment-15317726 ] Ismael Juma commented on KAFKA-1211: [~guozhang], is this still an issue? > Hold the

[jira] [Commented] (KAFKA-3443) Support regex topics in addSource() and stream()

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

[GitHub] kafka pull request #1410: KAFKA-3443 [Kafka Streams] added support for subsc...

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

Jenkins build is back to normal : kafka-0.10.0-jdk7 #121

See

[jira] [Updated] (KAFKA-570) Kafka should not need snappy jar at runtime

[ https://issues.apache.org/jira/browse/KAFKA-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-570: -- Fix Version/s: (was: 0.10.1.0) 0.9.0.0 > Kafka should not need snappy jar at runti

[jira] [Resolved] (KAFKA-570) Kafka should not need snappy jar at runtime

[ https://issues.apache.org/jira/browse/KAFKA-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-570. --- Resolution: Fixed This is fixed in the new clients, closing. > Kafka should not need snappy jar at run

Jenkins build is back to normal : kafka-trunk-jdk8 #685

See

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

See Changes: [ismael] KAFKA-724; Allow automatic socket.send.buffer from operating system in [ismael] KAFKA-3783; Catch proper exception on path delete -- [...truncated 3354 lines...] kafka.too

[jira] [Updated] (KAFKA-3781) Errors.exceptionName() can throw NPE

[ https://issues.apache.org/jira/browse/KAFKA-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3781: --- Reviewer: Ewen Cheslack-Postava Status: Patch Available (was: Open) > Errors.exceptionName() ca

[jira] [Commented] (KAFKA-3781) Errors.exceptionName() can throw NPE

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

[GitHub] kafka pull request #1476: KAFKA-3781; Errors.exceptionName() can throw NPE

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1476 KAFKA-3781; Errors.exceptionName() can throw NPE You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-3781-exception-name-npe Altern

[jira] [Assigned] (KAFKA-3781) Errors.exceptionName() can throw NPE

[ https://issues.apache.org/jira/browse/KAFKA-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3781: -- Assignee: Ismael Juma > Errors.exceptionName() can throw NPE >

[jira] [Comment Edited] (KAFKA-1981) Make log compaction point configurable

[ https://issues.apache.org/jira/browse/KAFKA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317588#comment-15317588 ] Eric Wasserman edited comment on KAFKA-1981 at 6/7/16 12:56 AM:

[jira] [Comment Edited] (KAFKA-1981) Make log compaction point configurable

[ https://issues.apache.org/jira/browse/KAFKA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317588#comment-15317588 ] Eric Wasserman edited comment on KAFKA-1981 at 6/7/16 12:56 AM:

[jira] [Commented] (KAFKA-1981) Make log compaction point configurable

[ https://issues.apache.org/jira/browse/KAFKA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317588#comment-15317588 ] Eric Wasserman commented on KAFKA-1981: --- During the KIP-58 vote it was [suggested](

[jira] [Resolved] (KAFKA-3783) Race condition on last ACL removal for a resource fails with a ZkBadVersionException

[ https://issues.apache.org/jira/browse/KAFKA-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3783. Resolution: Fixed > Race condition on last ACL removal for a resource fails with a > ZkBadVersionEx

[jira] [Reopened] (KAFKA-3783) Race condition on last ACL removal for a resource fails with a ZkBadVersionException

[ https://issues.apache.org/jira/browse/KAFKA-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-3783: > Race condition on last ACL removal for a resource fails with a > ZkBadVersionException >

[jira] [Updated] (KAFKA-3783) Race condition on last ACL removal for a resource fails with a ZkBadVersionException

[ https://issues.apache.org/jira/browse/KAFKA-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3783: --- Status: Resolved (was: Closed) > Race condition on last ACL removal for a resource fails with a > Zk

[jira] [Closed] (KAFKA-3783) Race condition on last ACL removal for a resource fails with a ZkBadVersionException

[ https://issues.apache.org/jira/browse/KAFKA-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma closed KAFKA-3783. -- > Race condition on last ACL removal for a resource fails with a > ZkBadVersionException >

[jira] [Updated] (KAFKA-3783) Race condition on last ACL removal for a resource fails with a ZkBadVersionException

[ https://issues.apache.org/jira/browse/KAFKA-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3783: --- Assignee: Sébastien Launay > Race condition on last ACL removal for a resource fails with a > ZkBadVe

[jira] [Commented] (KAFKA-3783) Race condition on last ACL removal for a resource fails with a ZkBadVersionException

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

[jira] [Resolved] (KAFKA-3783) Race condition on last ACL removal for a resource fails with a ZkBadVersionException

[ https://issues.apache.org/jira/browse/KAFKA-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3783. Resolution: Fixed Fix Version/s: 0.10.0.1 Issue resolved by pull request 1461 [https://github

[GitHub] kafka pull request #1461: KAFKA-3783: Catch proper exception on path delete

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

[jira] [Updated] (KAFKA-3396) Unauthorized topics are returned to the user

[ https://issues.apache.org/jira/browse/KAFKA-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3396: --- Status: Patch Available (was: Open) > Unauthorized topics are returned to the user >

[jira] [Updated] (KAFKA-724) Allow automatic socket.send.buffer from operating system

[ https://issues.apache.org/jira/browse/KAFKA-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-724: -- Resolution: Fixed Reviewer: Ismael Juma (was: Jay Kreps) Status: Resolved (was: Patch Avai

[jira] [Commented] (KAFKA-724) Allow automatic socket.send.buffer from operating system

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

[GitHub] kafka pull request #1469: KAFKA-724; Allow automatic socket.send.buffer from...

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

Re: [DISCUSS] KIP-54 Sticky Partition Assignment Strategy

Hi Jason, Thanks for reviewing the KIP. I will add the details you requested, but to summarize: Regarding the structure of the user data: Right now the user data will have the current assignments only which is a mapping of consumers to their assigned topic partitions. Is this mapping what you'

[GitHub] kafka pull request #1475: MINOR: Add comment for round robin partitioner wit...

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1475 MINOR: Add comment for round robin partitioner with different subscriptions You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ishiihara/kafka ro

[jira] [Assigned] (KAFKA-3794) Add Stream / Table prefix in print functions

[ https://issues.apache.org/jira/browse/KAFKA-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck reassigned KAFKA-3794: -- Assignee: Bill Bejeck > Add Stream / Table prefix in print functions >

[jira] [Commented] (KAFKA-3794) Add Stream / Table prefix in print functions

[ https://issues.apache.org/jira/browse/KAFKA-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317475#comment-15317475 ] Bill Bejeck commented on KAFKA-3794: picking this one up, mea culpa > Add Stream / Ta

[jira] [Work started] (KAFKA-3167) Use local to the workspace Gradle cache and recreate it on every build

[ https://issues.apache.org/jira/browse/KAFKA-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3167 started by Ismael Juma. -- > Use local to the workspace Gradle cache and recreate it on every build > --

[jira] [Commented] (KAFKA-3167) Use local to the workspace Gradle cache and recreate it on every build

[ https://issues.apache.org/jira/browse/KAFKA-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317422#comment-15317422 ] Ismael Juma commented on KAFKA-3167: I changed this so that we do the following before

[jira] [Created] (KAFKA-3796) SslTransportLayerTest.testInvalidEndpointIdentification fails on trunk

Rekha Joshi created KAFKA-3796: -- Summary: SslTransportLayerTest.testInvalidEndpointIdentification fails on trunk Key: KAFKA-3796 URL: https://issues.apache.org/jira/browse/KAFKA-3796 Project: Kafka

[jira] [Updated] (KAFKA-3795) Transient system test failure upgrade_test.TestUpgrade

[ https://issues.apache.org/jira/browse/KAFKA-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3795: --- Description: >From a recent build running on the 0.10.0 branch: {code} test_id: 2016-06-06--001.k

[jira] [Created] (KAFKA-3795) Transient system test failure upgrade_test.TestUpgrade

Jason Gustafson created KAFKA-3795: -- Summary: Transient system test failure upgrade_test.TestUpgrade Key: KAFKA-3795 URL: https://issues.apache.org/jira/browse/KAFKA-3795 Project: Kafka Issu

Re: [DISCUSS] KIP-62: Allow consumer to send heartbeats from a background thread

Guozhang and Jason, I think we are on the same page that having rebalances done in the background thread has a much bigger impact to the users. So I agree that is is probably better to start with having 1) and 2). We can add 3) later if necessary. Another implementation detail I am not quite sure

[jira] [Created] (KAFKA-3794) Add Stream / Table prefix in print functions

Guozhang Wang created KAFKA-3794: Summary: Add Stream / Table prefix in print functions Key: KAFKA-3794 URL: https://issues.apache.org/jira/browse/KAFKA-3794 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-1981) Make log compaction point configurable

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

[GitHub] kafka pull request #1168: KAFKA-1981 Make log compaction point configurable

Github user ewasserman closed the pull request at: https://github.com/apache/kafka/pull/1168 --- 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-54 Sticky Partition Assignment Strategy

Hi Vahid, Can you add some detail to the KIP on the structure of the user data? I'm guessing it would be something like this: ProtocolName => "sticky" ProtocolMetadata => Version Subscription UserData Version => int16 Subscription => [Topic] Topic => string UserData => CurrentAssignmen

[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=15317147#comment-15317147 ] Ewen Cheslack-Postava commented on KAFKA-2394: -- [~cotedm] Sounds good. Maybe

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

See Changes: [ismael] KAFKA-2948; Remove unused topics from producer metadata set -- [...truncated 3293 lines...] kafka.integration.AutoOffsetResetTest > testResetToLatestWhenOffsetTooLow START

[jira] [Comment Edited] (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=15316992#comment-15316992 ] Dustin Cote edited comment on KAFKA-2394 at 6/6/16 6:57 PM: [~

[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=15316992#comment-15316992 ] Dustin Cote commented on KAFKA-2394: [~ewencp] I only got positive feedback on the cha

[jira] [Updated] (KAFKA-2948) Kafka producer does not cope well with topic deletions

[ https://issues.apache.org/jira/browse/KAFKA-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2948: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Kafka producer does not cope well

[jira] [Commented] (KAFKA-2948) Kafka producer does not cope well with topic deletions

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

[jira] [Commented] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316991#comment-15316991 ] Maysam Yabandeh commented on KAFKA-3693: My apology. That was a copy-paste error.

[GitHub] kafka pull request #645: KAFKA-2948: Remove unused topics from producer meta...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/645 --- 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-3748) Add consumer-property to console tools consumer (similar to --producer-property)

[ https://issues.apache.org/jira/browse/KAFKA-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated KAFKA-3748: -- Status: Patch Available (was: In Progress) > Add consumer-property to console tools con

[jira] [Updated] (KAFKA-3748) Add consumer-property to console tools consumer (similar to --producer-property)

[ https://issues.apache.org/jira/browse/KAFKA-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated KAFKA-3748: -- Attachment: KAFKA-3748.PATCH Attaching the patch file. > Add consumer-property to conso

Re: [DISCUSS] KIP-62: Allow consumer to send heartbeats from a background thread

Jiangjie: About doing the rebalance in the background thread, I'm a bit concerned as it will change a lot of the concurrency guarantees that consumer currently provides (think of a consumer caller thread committing externally while the rebalance is happening in the background thread), and hence if

Re: [DISCUSS] KIP-62: Allow consumer to send heartbeats from a background thread

(+ Matthias) Hello Henry, Specifically to your question regarding Kafka Streams: 1. Currently restoreActiveState() is triggered in the onPartitionAssigned callback, which is after the rebalance is completed from the coordinator's point of view, and hence is covered in the process timeout value i

Re: [DISCUSS] KIP-62: Allow consumer to send heartbeats from a background thread

Hi Becket, Thanks for the comments. It sounds like we are in basic agreement on this KIP. On the rebalance timeout, I share the same concern about the impact of tying the process and rebalance timeouts together. To be clear, this problem exists in the current consumer (with the session timeout), s

[GitHub] kafka pull request #1474: KAFKA-3748: Add consumer-property to console tools...

GitHub user bharatviswa504 opened a pull request: https://github.com/apache/kafka/pull/1474 KAFKA-3748: Add consumer-property to console tools consumer @ijuma @harshach @edoardocomar Can you please review the changes. @edoardocomar I have addressed your comment of extra spac

[jira] [Commented] (KAFKA-3748) Add consumer-property to console tools consumer (similar to --producer-property)

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

[jira] [Commented] (KAFKA-3748) Add consumer-property to console tools consumer (similar to --producer-property)

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

[GitHub] kafka pull request #1459: KAFKA-3748: Add consumer-property to console tools...

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

Re: [DISCUSS] KIP-63: Unify store and downstream caching in streams

On Mon, Jun 6, 2016 at 6:48 PM, Guozhang Wang wrote: > > About using Instrumentation.getObjectSize, yeah we were worried a lot about > its efficiency as well as accuracy when discussing internally, but not a > better solution was proposed. So if people have better ideas, please throw > them here,

Re: [DISCUSS] KIP-63: Unify store and downstream caching in streams

About the distribution of memory: I think it is good to evenly distribute the memory across threads, while what I was calling our for considerata is the distribution of memory within a thread, to its tasks / caches of the task, as the number of tasks and the number of caches in the task can vary fr

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

See -- [...truncated 3367 lines...] kafka.log.LogSegmentTest > testReadFromGap PASSED kafka.log.LogSegmentTest > testTruncate PASSED kafka.log.LogSegmentTest > testReadBeforeFirstOffset PASSED kafka.

Re: [DISCUSS] KIP-63: Unify store and downstream caching in streams

For the threads, I think it might be reasonable to just give each thread cache_bytes/num_threads for simplicity? Presumably you wouldn't want to have to make the cache threadsafe so you'd want to avoid sharing? Giving each thread the same cache isn't quite right, as you point out, but depending on

[jira] [Commented] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316652#comment-15316652 ] Jun Rao commented on KAFKA-3693: Yes, if the controller detects that a broker is down, it

Re: [DISCUSS] KIP-63: Unify store and downstream caching in streams

If we are going with a global setting, can the cache just be one gigantic LRU cache instead of many smaller ones? (partition_name, task_name) can be part of cache key. If there are many smaller caches, it's hard to achieve efficient global resource utilization (some caches are busy, some caches a

[jira] [Commented] (KAFKA-3792) Fix log spam in clients when topic doesn't exist

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

[GitHub] kafka pull request #1473: KAFKA-3792: Fix log spam in clients for unknown to...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/1473 KAFKA-3792: Fix log spam in clients for unknown topics You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka KAFKA-3792 Alt

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

See -- [...truncated 3367 lines...] kafka.log.LogManagerTest > testRecoveryDirectoryMappingWithRelativeDirectory PASSED kafka.log.LogManagerTest > testGetNonExistentLog PASSED kafka.log.LogManagerTes

Jenkins build is back to normal : kafka-trunk-jdk8 #683

See

[jira] [Resolved] (KAFKA-3764) Error processing append operation on partition

[ https://issues.apache.org/jira/browse/KAFKA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3764. Resolution: Duplicate Marking as duplicate of KAFKA-3789 as the latter describes the problem more c

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

See -- [...truncated 3170 lines...] kafka.network.SocketServerTest > testMaxConnectionsPerIp PASSED kafka.network.SocketServerTest > testBrokerSendAfterChannelClosedUpdatesRequestMetrics PASSED kafka

[jira] [Assigned] (KAFKA-3167) Use local to the workspace Gradle cache and recreate it on every build

[ https://issues.apache.org/jira/browse/KAFKA-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3167: -- Assignee: Ismael Juma > Use local to the workspace Gradle cache and recreate it on every build

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

See

Re: [DISCUSS] KIP-63: Unify store and downstream caching in streams

Hi Guozhang, About your first point: the alternative is not knowing how much memory a KafkaStreams instance will consume, since, as you mention, M and N can change. I agree the implementation is slightly harder since each cache now can change size dynamically (and the Kafka Streams instance nee

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

See -- Started by user ijuma [EnvInject] - Loading node environment variables. Building remotely on H11 (docker Ubuntu ubuntu yahoo-not-h2) in workspace

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

See -- Started by user ijuma [EnvInject] - Loading node environment variables. Building remotely on H11 (docker Ubuntu ubuntu yahoo-not-h2) in workspace

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

See Changes: [ismael] KAFKA-3771; Improving Kafka core code -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H11 (docker Ubuntu ubuntu yahoo-not

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

See Changes: [ismael] KAFKA-3771; Improving Kafka core code -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-us1 (Ubuntu ubuntu ubuntu-us

  1   2   >