Re: Delete Kafka Topic After Enable Ranger Plugin

Hi, You got any log for this? Also, which platform are you running this on? KR, On Fri, 14 Jul 2017 at 11:26 pm, amazon wrote: > Hi: > > Recently I develop some applications about kafka under ranger. But > when I set enable ranger kafka plugin I can not delete

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

See Changes: [jason] MINOR: Change log level for group member failure from debug to info [ismael] MINOR: Correct the ConsumerPerformance print format -- [...truncated

Kafka Offset Management

Hi , I have wrote kafka consumer where i am managing kafka offset within our storage. The reason why we are doing this, In case of failure we should be able to restart from same time. I have disabled auto commit flag for offset. The writing of db happened that include offset write on

Delete Kafka Topic After Enable Ranger Plugin

Hi: Recently I develop some applications about kafka under ranger. But when I set enable ranger kafka plugin I can not delete kafka topic completely even though set 'delete.topic.enable=true'. And I find when enable ranger kafka plugin it must be authrized. How can I delete kafka topic

[GitHub] kafka pull request #3417: MINOR: Correct the ConsumerPerformance print forma...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3417 --- 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 #3523: MINOR: log4j for member failure from debug to info

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

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

See

[GitHub] kafka pull request #3529: MINOR: Use correct connectionId in error message

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3529 MINOR: Use correct connectionId in error message You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka

Re: Comments on JIRAs

Hello Tom, All committers should have subscribed to the newly created jira@kafka mailing list, so they still get all the notifications. If you want to ping someone who's not committer and not yet watching the ticket, then you do need to ping her id in your comment (once she has replied to your

[GitHub] kafka pull request #3528: Kafka-4763 (Used for triggering test only)

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/3528 Kafka-4763 (Used for triggering test only) This patch is used only for triggering test. No need for review. You can merge this pull request into a Git repository by running: $ git

[GitHub] kafka pull request #3464: MINOR: Enable a number of xlint scalac warnings

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3464 --- 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-175: Additional '--describe' views for ConsumerGroupCommand

In other words, I think the default should be the exact behavior we have today plus the remaining group information from DescribeGroupResponse. On Fri, Jul 14, 2017 at 11:36 AM, Onur Karaman wrote: > I think if we had the opportunity to start from scratch,

Re: [DISCUSS] KIP-175: Additional '--describe' views for ConsumerGroupCommand

I think if we had the opportunity to start from scratch, --describe would have been the following: --describe --offsets: shows all offsets committed for the group as well as lag --describe --state (or maybe --members): shows the full DescribeGroupResponse output (including things like generation

[jira] [Created] (KAFKA-5595) Illegal state in SocketServer; attempt to send with another send in progress

Jason Gustafson created KAFKA-5595: -- Summary: Illegal state in SocketServer; attempt to send with another send in progress Key: KAFKA-5595 URL: https://issues.apache.org/jira/browse/KAFKA-5595

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

See Changes: [jason] KAFKA-5127; Replace pattern matching with foreach where the case None is -- [...truncated 2.62 MB...]

Re: Comments on JIRAs

Hi Tom, All active committers should be subscribed to jira@ so I don't think this changes much from that perspective. If you want to get wider input on a particular topic, then you should send an email to the mailing list, however. This was the case before the creation of jira@ as mailing list

Re: [DISCUSS] KIP-175: Additional '--describe' views for ConsumerGroupCommand

Hey Vahid, Thanks for the KIP. Looks like a nice improvement. One minor suggestion: Since consumers can be subscribed to a large number of topics, I'm wondering if it might be better to leave out the topic list from the "describe members" option so that the output remains concise? Perhaps we

Re: Comments on JIRAs

Thanks for bringing this up. I don't know what the solution is, but I agree it would be good to have something. On Jul 13, 2017 6:46 AM, "Tom Bentley" wrote: > The project recently switched from all JIRA events being sent to the dev > mailling list, to just issue

[GitHub] kafka pull request #3527: MINOR: Mention systemTestLibs in docker system tes...

Github user ijuma closed the pull request at: https://github.com/apache/kafka/pull/3527 --- 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 #2919: KAFKA-5127 Replace pattern matching with foreach w...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2919 --- 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 #3527: MINOR: Mention systemTestLibs in docker system tes...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3527 MINOR: Mention systemTestLibs in docker system test instructions Otherwise NoClassFoundExceptions are thrown for tests that attempt to start MiniKdc. You can merge this pull request into a Git

Re: [DISCUSS] KIP-171: Extend Consumer Group Reset Offset for Stream Application

Hi, KIP is updated. Changes: 1. Approach discussed to keep both tools (streams application resetter and consumer group reset offset). 2. Options has been aligned between both tools. 3. Zookeeper option from streams-application-resetted will be removed, and replaced internally for Kafka

[jira] [Created] (KAFKA-5594) Tag messages with authenticated user who produced it

Jack Andrews created KAFKA-5594: --- Summary: Tag messages with authenticated user who produced it Key: KAFKA-5594 URL: https://issues.apache.org/jira/browse/KAFKA-5594 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-5593) Kafka streams not re-balancing when 3 consumer streams are there

Yogesh BG created KAFKA-5593: Summary: Kafka streams not re-balancing when 3 consumer streams are there Key: KAFKA-5593 URL: https://issues.apache.org/jira/browse/KAFKA-5593 Project: Kafka

[jira] [Created] (KAFKA-5592) Connection with plain client to SSL-secured broker causes OOM

Marcin Łuczyński created KAFKA-5592: --- Summary: Connection with plain client to SSL-secured broker causes OOM Key: KAFKA-5592 URL: https://issues.apache.org/jira/browse/KAFKA-5592 Project: Kafka

[GitHub] kafka pull request #3526: KAFKA-5587: Remove channel only after staged recei...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3526 KAFKA-5587: Remove channel only after staged receives are delivered When idle connections are closed, ensure that channels with staged receives are retained in `closingChannels` until all

[jira] [Created] (KAFKA-5591) Infinite loop during failed Handshake

Marcin Łuczyński created KAFKA-5591: --- Summary: Infinite loop during failed Handshake Key: KAFKA-5591 URL: https://issues.apache.org/jira/browse/KAFKA-5591 Project: Kafka Issue Type: Bug

[DISCUSS] KIP-174 - Deprecate and remove internal converter configs in WorkerConfig

Hi there, Resending as probably missed earlier to grab your attention. Regards, Umesh -- Forwarded message - From: UMESH CHAUDHARY Date: Mon, 3 Jul 2017 at 11:04 Subject: [DISCUSS] KIP-174 - Deprecate and remove internal converter configs in WorkerConfig To: