[jira] [Updated] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped

[ https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex updated KAFKA-4367: Description: MirrorMaker stops working without being stopped. From 30 minutes to 20 hours. No clue why this problem

[jira] [Commented] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped

[ https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632077#comment-15632077 ] Alex commented on KAFKA-4367: - This shouldn't be an issue since we run MirrorMaker detached fr

[jira] [Created] (KAFKA-4371) Sporadic ConnectException shuts down the whole connect process

Sagar Rao created KAFKA-4371: Summary: Sporadic ConnectException shuts down the whole connect process Key: KAFKA-4371 URL: https://issues.apache.org/jira/browse/KAFKA-4371 Project: Kafka Issue T

[jira] [Assigned] (KAFKA-2247) Merge kafka.utils.Time and kafka.common.utils.Time

[ https://issues.apache.org/jira/browse/KAFKA-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-2247: -- Assignee: Ismael Juma (was: Aditya Auradkar) > Merge kafka.utils.Time and kafka.common.utils.T

Re: [DISCUSS] KIP-84: Support SASL/SCRAM mechanisms

I don't have a strong objection to bumping up SaslHandshakeRequest version, though I am still not convinced of the usefulness. I do agree that KIP-35 should be standard way to determine client/broker compatibility. But I am not sure ApiVersionsRequest is a good fit for clients to choose a SASL mech

[GitHub] kafka pull request #2095: KAFKA-2247: Merge kafka.utils.Time and kafka.commo...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2095 KAFKA-2247: Merge kafka.utils.Time and kafka.common.utils.Time You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-2247-consolidate

[jira] [Commented] (KAFKA-2247) Merge kafka.utils.Time and kafka.common.utils.Time

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

[jira] [Updated] (KAFKA-2247) Merge kafka.utils.Time and kafka.common.utils.Time

[ https://issues.apache.org/jira/browse/KAFKA-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2247: --- Fix Version/s: 0.10.2.0 Status: Patch Available (was: Open) > Merge kafka.utils.Time and k

[GitHub] kafka pull request #2091: MINOR: Bug fixed

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2091 --- 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-2247) Merge kafka.utils.Time and kafka.common.utils.Time

[ https://issues.apache.org/jira/browse/KAFKA-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632383#comment-15632383 ] Ismael Juma commented on KAFKA-2247: I submitted a PR since no progress has been made

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

See Changes: [ismael] MINOR: Remove stray `%s` in `TopicMetadata.toString` -- [...truncated 45972 lines...] Caused by: java.nio.file.FileSystemException: /tmp/kafka-4894287765309

[jira] [Commented] (KAFKA-4371) Sporadic ConnectException shuts down the whole connect process

[ https://issues.apache.org/jira/browse/KAFKA-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632506#comment-15632506 ] Tianji Li commented on KAFKA-4371: -- This seems like a bug in the https://github.com/confl

[jira] [Comment Edited] (KAFKA-4371) Sporadic ConnectException shuts down the whole connect process

[ https://issues.apache.org/jira/browse/KAFKA-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632506#comment-15632506 ] Tianji Li edited comment on KAFKA-4371 at 11/3/16 11:50 AM: Th

Re: [DISCUSS] KIP-84: Support SASL/SCRAM mechanisms

Hi all, I'm currently with limited internet access so I have not done a proper review of the KIP, my apologies. A couple of thoughts: 1. I agree with Rajini and I don't see the value in bumping the protocol version in this case. As Rajini said, the enabled mechanisms are independent of the broker

[jira] [Commented] (KAFKA-4371) Sporadic ConnectException shuts down the whole connect process

[ https://issues.apache.org/jira/browse/KAFKA-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632717#comment-15632717 ] Sagar Rao commented on KAFKA-4371: -- Another thing to note is that we get this exception w

[jira] [Created] (KAFKA-4372) Kafka Connect REST API does not handle DELETE of connector with slashes in their names

Olivier Girardot created KAFKA-4372: --- Summary: Kafka Connect REST API does not handle DELETE of connector with slashes in their names Key: KAFKA-4372 URL: https://issues.apache.org/jira/browse/KAFKA-4372

[GitHub] kafka pull request #2096: KAFKA-4372: Kafka Connect REST API does not handle...

GitHub user ogirardot opened a pull request: https://github.com/apache/kafka/pull/2096 KAFKA-4372: Kafka Connect REST API does not handle DELETE of connector with slashes in their names Kafka Connect REST API does not handle in many places connectors with slashes in their names bec

[jira] [Commented] (KAFKA-4372) Kafka Connect REST API does not handle DELETE of connector with slashes in their names

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

RE: Kafka Connect key.converter and value.converter properties for Avro encoding

Thanks to Gwen and Tommy Baker for their helpful replies. Currently, the environment I need to work with doesn't use the Schema Registry; hopefully one day it will but for now that's not an option. Events are written to Kafka without the schema embedded and each side of the interface assumes a

Re: [DISCUSS] KIP-87 - Add Compaction Tombstone Flag

Hi Michael, Do you mean using a new configuration it is just the exiting message.format.version config? It seems the message.format.version config is enough in this case. And the default value would always be the latest version. > Message version migration would be handled as like in KIP-32 Also

[jira] [Created] (KAFKA-4373) Kafka Consumer API jumping offsets

Srinivasan Venkatraman created KAFKA-4373: - Summary: Kafka Consumer API jumping offsets Key: KAFKA-4373 URL: https://issues.apache.org/jira/browse/KAFKA-4373 Project: Kafka Issue Type

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

See

Re: [DISCUSS] KIP-84: Support SASL/SCRAM mechanisms

Ismael, 2) I left out MD5 because it is insecure, but thought of keeping SHA-1 since it is supported by most services that support SCRAM today. Since there is no actual requirement to support SHA-1 and we don't really want to store credentials in Zookeeper using SHA-1, it makes sense not to suppor

Re: [DISCUSS] KAFKA-4345: Run decktape test for each pull request

Thanks, Raghav . I am +1 for having this in Kafka. It will help identify any potential issues, especially with big patches. Given that we've some tests failing due to timing issues can we disable the failing tests for now so that we don't get any false negatives? Thanks, Harsha On Tue, Nov 1, 201

Re: [ANNOUNCE] New committer: Jiangjie (Becket) Qin

Congratulations, Becket! Well done. On Wed, Nov 2, 2016 at 1:34 PM Eno Thereska wrote: > Congrats! > Eno > > > On 1 Nov 2016, at 05:57, Harsha Chintalapani wrote: > > > > Congrats Becket! > > -Harsha > > > > On Mon, Oct 31, 2016 at 2:13 PM Rajini Sivaram < > rajinisiva...@googlemail.com> > > wr

Re: [DISCUSS] KIP-84: Support SASL/SCRAM mechanisms

Agree with Rajini on not incrementing the protocol version. As brokers are returning the list of supported mechanisms don't think it warrants a protocol version bump. Thanks, Harsha On Thu, Nov 3, 2016 at 7:59 AM Rajini Sivaram wrote: > Ismael, > > 2) I left out MD5 because it is insecure, but

Re: [ANNOUNCE] New committer: Jiangjie (Becket) Qin

Congratulations, Becket! Best, Efe 2016-11-03 11:22 GMT-04:00 Neha Narkhede : > Congratulations, Becket! Well done. > > On Wed, Nov 2, 2016 at 1:34 PM Eno Thereska > wrote: > > > Congrats! > > Eno > > > > > On 1 Nov 2016, at 05:57, Harsha Chintalapani wrote: > > > > > > Congrats Becket! > > >

[jira] [Created] (KAFKA-4374) Improve Response Errors Logging

Jesse Anderson created KAFKA-4374: - Summary: Improve Response Errors Logging Key: KAFKA-4374 URL: https://issues.apache.org/jira/browse/KAFKA-4374 Project: Kafka Issue Type: Bug Com

Re: [DISCUSS] KAFKA-4345: Run decktape test for each pull request

Thanks Raghav, +1 for the idea in general. One thing I am wondering is when the tests would be run? Would it be run when we merge a PR or it would be run every time a PR is created/updated? I am not sure how long do the tests in other projects take. For Kafka it may take a few hours to run all th

Re: [DISCUSS] KAFKA-4345: Run decktape test for each pull request

Hi Becket, The tests would be run each time a PR is created/updated this will look similar to https://github.com/apache/storm/pulls. Ducktape tests take about 7-8 hours to run on my laptop. For travis-ci we can split them in groups and run them in parallel. This was done in the POC run which took

[DISCUSS] KIP 88: DescribeGroups Protocol Update

Hi all, I started a new KIP under https://cwiki.apache.org/confluence/display/KAFKA/KIP-88%3A+DescribeGroups+Protocol+Update . The KIP is a proposal to update the DescribeGroups protocol to address KAFKA-3853 (https://issues.apache.org/jira/browse/KAFKA-3853). I appreciate your feedback. Than

Re: [DISCUSS] KAFKA-4345: Run decktape test for each pull request

Thanks for the explanation, Raghav. If the workload is not a concern then it is probably fine to run tests for each PR update, although it may not be necessary :) On Thu, Nov 3, 2016 at 10:40 AM, Raghav Kumar Gautam wrote: > Hi Becket, > > The tests would be run each time a PR is created/update

[jira] [Commented] (KAFKA-4366) KafkaStreams.close() blocks indefinitely

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

[GitHub] kafka pull request #2097: KAFKA-4366: KafkaStreams.close() blocks indefinite...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2097 KAFKA-4366: KafkaStreams.close() blocks indefinitely Added `timeout` and `timeUnit` to `KafkaStreams.close(..)`. Now do close on a thread and `join` that thread with the provided `timeout`. Changed

[jira] [Created] (KAFKA-4375) Kafka consumer may swallow some interrupts meant for the calling thread

Stig Rohde Døssing created KAFKA-4375: - Summary: Kafka consumer may swallow some interrupts meant for the calling thread Key: KAFKA-4375 URL: https://issues.apache.org/jira/browse/KAFKA-4375 Proje

[jira] [Commented] (KAFKA-4375) Kafka consumer may swallow some interrupts meant for the calling thread

[ https://issues.apache.org/jira/browse/KAFKA-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634044#comment-15634044 ] Shikhar Bhushan commented on KAFKA-4375: Good to have a report of this being a pro

[jira] [Resolved] (KAFKA-4356) o.a.k.common.utils.SystemTime.sleep() swallows InterruptedException

[ https://issues.apache.org/jira/browse/KAFKA-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shikhar Bhushan resolved KAFKA-4356. Resolution: Duplicate > o.a.k.common.utils.SystemTime.sleep() swallows InterruptedException

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

As others have laid out, I see strong reasons for a common message metadata structure for the Kafka ecosystem. In particular, I've seen that even within a single organization, infrastructure teams often own the message metadata while application teams own the application-level data format. Allow

[jira] [Commented] (KAFKA-4375) Kafka consumer may swallow some interrupts meant for the calling thread

[ https://issues.apache.org/jira/browse/KAFKA-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634337#comment-15634337 ] Stig Rohde Døssing commented on KAFKA-4375: --- Happy to hear that. I'll try resett

[jira] [Created] (KAFKA-4376) Add scala 2.12 support

Bernard Leach created KAFKA-4376: Summary: Add scala 2.12 support Key: KAFKA-4376 URL: https://issues.apache.org/jira/browse/KAFKA-4376 Project: Kafka Issue Type: Improvement Compon

[jira] [Created] (KAFKA-4377) Address 2.12 deprecations

Bernard Leach created KAFKA-4377: Summary: Address 2.12 deprecations Key: KAFKA-4377 URL: https://issues.apache.org/jira/browse/KAFKA-4377 Project: Kafka Issue Type: Sub-task Compon

[jira] [Created] (KAFKA-4378) Address 2.12 eta-expansion warnings

Bernard Leach created KAFKA-4378: Summary: Address 2.12 eta-expansion warnings Key: KAFKA-4378 URL: https://issues.apache.org/jira/browse/KAFKA-4378 Project: Kafka Issue Type: Sub-task

[GitHub] kafka pull request #2098: KAFA-4378: resolve eta-expansion of zero-argument ...

GitHub user leachbj opened a pull request: https://github.com/apache/kafka/pull/2098 KAFA-4378: resolve eta-expansion of zero-argument method warnings You can merge this pull request into a Git repository by running: $ git pull https://github.com/leachbj/kafka 4378-eta-expansi

[GitHub] kafka pull request #2099: MINOR: Fix re-raise of python error in system test...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/2099 MINOR: Fix re-raise of python error in system tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka fix-python-reraise Alternativel

[GitHub] kafka pull request #2100: KAFKA-4375: Reset thread interrupted state in a fe...

GitHub user srdo opened a pull request: https://github.com/apache/kafka/pull/2100 KAFKA-4375: Reset thread interrupted state in a few places where Inte… …rruptedException is caught in a thread Kafka didn't start. See https://issues.apache.org/jira/browse/KAFKA-4375 You

[jira] [Commented] (KAFKA-4375) Kafka consumer may swallow some interrupts meant for the calling thread

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

[jira] [Assigned] (KAFKA-4375) Kafka consumer may swallow some interrupts meant for the calling thread

[ https://issues.apache.org/jira/browse/KAFKA-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing reassigned KAFKA-4375: - Assignee: Stig Rohde Døssing > Kafka consumer may swallow some interrupts meant f

[jira] [Commented] (KAFKA-4377) Address 2.12 deprecations

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

[GitHub] kafka pull request #2101: KAFKA-4377: remove deprecated scala.collection.Jav...

GitHub user leachbj opened a pull request: https://github.com/apache/kafka/pull/2101 KAFKA-4377: remove deprecated scala.collection.JavaConversions calls JavaConversions are deprecated in 2.12 in favour of JavaConverters. You can merge this pull request into a Git repository by runn

[jira] [Commented] (KAFKA-4376) Add scala 2.12 support

[ https://issues.apache.org/jira/browse/KAFKA-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634454#comment-15634454 ] Bernard Leach commented on KAFKA-4376: -- 2.12 will need to be built using java8, curre

[jira] [Updated] (KAFKA-4375) Kafka consumer may swallow some interrupts meant for the calling thread

[ https://issues.apache.org/jira/browse/KAFKA-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated KAFKA-4375: -- Affects Version/s: 0.10.1.0 Status: Patch Available (was: Open) Reset th

[jira] [Issue Comment Deleted] (KAFKA-4375) Kafka consumer may swallow some interrupts meant for the calling thread

[ https://issues.apache.org/jira/browse/KAFKA-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated KAFKA-4375: -- Comment: was deleted (was: Reset thread interrupt state in a few places where Interrupte

[jira] [Commented] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped

[ https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634711#comment-15634711 ] huxi commented on KAFKA-4367: - Did you run it with nohup? > MirrorMaker shuts down gracefully

[jira] [Commented] (KAFKA-4373) Kafka Consumer API jumping offsets

[ https://issues.apache.org/jira/browse/KAFKA-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634757#comment-15634757 ] huxi commented on KAFKA-4373: - Could you paste your client code and the stack trace? > Kafka

[jira] [Commented] (KAFKA-4371) Sporadic ConnectException shuts down the whole connect process

[ https://issues.apache.org/jira/browse/KAFKA-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634793#comment-15634793 ] Ewen Cheslack-Postava commented on KAFKA-4371: -- [~sagarrao] I'm a bit confuse

[GitHub] kafka pull request #2102: KAFKA-2284: corrects value type in beforeReleasing...

GitHub user leachbj opened a pull request: https://github.com/apache/kafka/pull/2102 KAFKA-2284: corrects value type in beforeReleasingPartitions Previously the values in the map were scala Set values, now they are correctly java.util.Set as advertised by API. You can merge this

[jira] [Commented] (KAFKA-2284) ConsumerRebalanceListener receives wrong type in partitionOwnership values

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

[jira] [Commented] (KAFKA-2284) ConsumerRebalanceListener receives wrong type in partitionOwnership values

[ https://issues.apache.org/jira/browse/KAFKA-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634855#comment-15634855 ] Bernard Leach commented on KAFKA-2284: -- Just came across this as a failing test in h

[jira] [Commented] (KAFKA-4024) First metadata update always take retry.backoff.ms milliseconds to complete

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

[GitHub] kafka pull request #1707: KAFKA-4024: Fix metadata update to not apply backo...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1707 --- 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-4024) First metadata update always take retry.backoff.ms milliseconds to complete

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

[jira] [Commented] (KAFKA-955) After a leader change, messages sent with ack=0 are lost

[ https://issues.apache.org/jira/browse/KAFKA-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631889#comment-15631889 ] Bill Zhang commented on KAFKA-955: -- I am using Flume with Kafka Channel & facing below iss

[jira] [Commented] (KAFKA-4369) ZkClient is not closed upon streams shutdown

[ https://issues.apache.org/jira/browse/KAFKA-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631912#comment-15631912 ] Matthias J. Sax commented on KAFKA-4369: There is a PR for https://issues.apache.o

[jira] [Updated] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped

[ https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex updated KAFKA-4367: Summary: MirrorMaker shuts down gracefully without actually being stopped (was: MirrorMaker shuts down gracefully w

[jira] [Updated] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped

[ https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex updated KAFKA-4367: Description: MirrorMaker stops working without being stopped, 30 minutes after start. No clue why this problem occu