[GitHub] kafka pull request #2682: KAFKA-4859: Set shorter commit interval for integr...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/2682 KAFKA-4859: Set shorter commit interval for integration tests with caching You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-4859) Transient test failure: org.apache.kafka.streams.integration.JoinIntegrationTest.shouldCountClicksPerRegion (again)

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

[jira] [Assigned] (KAFKA-4893) async topic deletion conflicts with max topic length

[ https://issues.apache.org/jira/browse/KAFKA-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-4893: -- Assignee: Vahid Hashemian > async topic deletion conflicts with max topic length >

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

I'm torn between my desire to get this in already and the fact that parts of the API feel a bit alien to Kafka. I will resolve my difficulties by giving my feedback here and then going to vote +1 on the vote thread. Colin can choose whether to address my concerns now or use his "unstable" option

[jira] [Created] (KAFKA-4893) async topic deletion conflicts with max topic length

Onur Karaman created KAFKA-4893: --- Summary: async topic deletion conflicts with max topic length Key: KAFKA-4893 URL: https://issues.apache.org/jira/browse/KAFKA-4893 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-4878) Kafka Connect does not log connector configuration errors

[ https://issues.apache.org/jira/browse/KAFKA-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4878: Fix Version/s: 0.10.2.1 > Kafka Connect does not log connector configuration errors >

[jira] [Updated] (KAFKA-4878) Kafka Connect does not log connector configuration errors

[ https://issues.apache.org/jira/browse/KAFKA-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4878: Priority: Blocker (was: Major) > Kafka Connect does not log connector configuration errors >

[jira] [Comment Edited] (KAFKA-4878) Kafka Connect does not log connector configuration errors

[ https://issues.apache.org/jira/browse/KAFKA-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923586#comment-15923586 ] Gwen Shapira edited comment on KAFKA-4878 at 3/14/17 5:07 AM: -- This is even

[jira] [Commented] (KAFKA-4878) Kafka Connect does not log connector configuration errors

[ https://issues.apache.org/jira/browse/KAFKA-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923586#comment-15923586 ] Gwen Shapira commented on KAFKA-4878: - This is even worse in stand-alone mode because if you start it

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

StreamsBuilder would be my vote. > On Mar 13, 2017, at 9:42 PM, Jay Kreps wrote: > > Hey Matthias, > > Make sense, I'm more advocating for removing the word topology than any > particular new replacement. > > -Jay > > On Mon, Mar 13, 2017 at 12:30 PM, Matthias J. Sax

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

Hey Matthias, Make sense, I'm more advocating for removing the word topology than any particular new replacement. -Jay On Mon, Mar 13, 2017 at 12:30 PM, Matthias J. Sax wrote: > Jay, > > thanks for your feedback > > > What if instead we called it KStreamsBuilder? > >

[jira] [Commented] (KAFKA-4277) creating ephemeral node already exist

[ https://issues.apache.org/jira/browse/KAFKA-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923516#comment-15923516 ] Jun Rao commented on KAFKA-4277: [~Wrikken], the only case when we need to re-register the broker in ZK is

Re: [DISCUSS] KIP-126 - Allow KafkaProducer to batch based on uncompressed size

Bump up the thread for further comments. If there is no more comments on the KIP I will start the voting thread on Wed. Thanks, Jiangjie (Becket) Qin On Tue, Mar 7, 2017 at 9:48 AM, Becket Qin wrote: > Hi Dong, > > Thanks for the comments. > > The patch is mostly for

[jira] [Commented] (KAFKA-4890) State directory being deleted when another thread holds the lock

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

[GitHub] kafka pull request #2681: KAFKA-4890: Improve log4j for debugging [WIP]

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/2681 KAFKA-4890: Improve log4j for debugging [WIP] You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka K4890-state-lock-cleanup

[jira] [Commented] (KAFKA-4890) State directory being deleted when another thread holds the lock

[ https://issues.apache.org/jira/browse/KAFKA-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923361#comment-15923361 ] Guozhang Wang commented on KAFKA-4890: -- I have uploaded a small PR to improve the log4j for

[jira] [Commented] (KAFKA-4890) State directory being deleted when another thread holds the lock

[ https://issues.apache.org/jira/browse/KAFKA-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923328#comment-15923328 ] Guozhang Wang commented on KAFKA-4890: -- Since I do not have the code sketch it is hard to reproduce

[jira] [Comment Edited] (KAFKA-4890) State directory being deleted when another thread holds the lock

[ https://issues.apache.org/jira/browse/KAFKA-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923322#comment-15923322 ] Guozhang Wang edited comment on KAFKA-4890 at 3/14/17 12:41 AM:

[jira] [Created] (KAFKA-4892) kafka 0.8.2.1 getOffsetsBefore API returning correct offset given timestamp in unix epoch format

Chris Bedford created KAFKA-4892: Summary: kafka 0.8.2.1 getOffsetsBefore API returning correct offset given timestamp in unix epoch format Key: KAFKA-4892 URL: https://issues.apache.org/jira/browse/KAFKA-4892

[GitHub] kafka pull request #2680: KAFKA-4859: Raised Timeout

GitHub user original-brownbear opened a pull request: https://github.com/apache/kafka/pull/2680 KAFKA-4859: Raised Timeout This fixes https://issues.apache.org/jira/browse/KAFKA-4859 for me over hundreds of iterations while I could easily reproduce it with less than ~30-40

[jira] [Commented] (KAFKA-4859) Transient test failure: org.apache.kafka.streams.integration.JoinIntegrationTest.shouldCountClicksPerRegion (again)

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

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

See Changes: [jason] HOTFIX: Fix apache headers in float serde class files -- [...truncated 21.52 KB...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[8]

Re: [DISCUSS] KIP-113: Support replicas movement between log directories

Hey Jun, Thanks much for your detailed comments. Please see my reply below. On Mon, Mar 13, 2017 at 9:09 AM, Jun Rao wrote: > Hi, Dong, > > Thanks for the updated KIP. Some more comments below. > > 10. For the .move log, do we perform any segment deletion (based on >

[jira] [Commented] (KAFKA-4859) Transient test failure: org.apache.kafka.streams.integration.JoinIntegrationTest.shouldCountClicksPerRegion (again)

[ https://issues.apache.org/jira/browse/KAFKA-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923095#comment-15923095 ] Armin Braun commented on KAFKA-4859: [~guozhang] so basically this can just be resolved by setting a

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

See Changes: [wangguoz] KAFKA-4769: Add Float serializer, deserializer, serde [wangguoz] KAFKA-4657: Improve test coverage of CompositeReadOnlyWindowStore [becket.qin] KAFKA-4891; kafka.request.logger TRACE

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

Hi Radai, Thanks for looking at the KIP again. On Mon, Mar 13, 2017, at 12:33, radai wrote: > looking at the KIP as it is now, looks like all *Options objects have a > common timeout property. could it be extracted to a common > AdminRequestOptions or something? Perhaps I'm missing something,

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

See

Re: [DISCUSS] KIP-125: ZookeeperConsumerConnector to KafkaConsumer Migration and Rollback

Oh, seems I missed your comment saying the default would be "auto." Hmm... If that's safe, then it sounds good to me. -Jason On Mon, Mar 13, 2017 at 2:32 PM, Jason Gustafson wrote: > Hey Onur, > > >> Regarding 1: I've been considering something like this for a while now. >>

Re: [DISCUSS] KIP-132: Augment KStream.print to allow extra parameters in the printed string

Can you please add the KIP to this table: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals#KafkaImprovementProposals-KIPsunderdiscussion Thanks, Matthias On 3/13/17 8:08 AM, Marc Juchli wrote: > Dear all, > > The following describes KIP-132, which I just

Re: [DISCUSS] KIP-125: ZookeeperConsumerConnector to KafkaConsumer Migration and Rollback

Hey Onur, > Regarding 1: I've been considering something like this for a while now. > KIP-122 has a similar issue and I brought up some hacks in that discussion > to work around it (http://markmail.org/message/kk4ng74riejidify). While > solving this problem would help loosen the requirements for

[jira] [Commented] (KAFKA-4859) Transient test failure: org.apache.kafka.streams.integration.JoinIntegrationTest.shouldCountClicksPerRegion (again)

[ https://issues.apache.org/jira/browse/KAFKA-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15922979#comment-15922979 ] Armin Braun commented on KAFKA-4859: [~guozhang] zeroing in on it :) Should have a PR in either ~ 2h

[jira] [Commented] (KAFKA-4643) Improve test coverage of StreamsKafkaClient

[ https://issues.apache.org/jira/browse/KAFKA-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15922945#comment-15922945 ] Andrey Dyachkov commented on KAFKA-4643: I would like to grab this one, could you explain more on

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

See Changes: [wangguoz] KAFKA-4769: Add Float serializer, deserializer, serde [wangguoz] KAFKA-4657: Improve test coverage of CompositeReadOnlyWindowStore --

Re: [DISCUSS] KIP-131 : Add access to OffsetStorageReader from SourceConnector

Can you please add the KIP to this table: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals#KafkaImprovementProposals-KIPsunderdiscussion Thanks, Matthias On 3/7/17 1:24 PM, Florian Hussonnois wrote: > Hi all, > > I've created a new KIP to add access to

[jira] [Commented] (KAFKA-4835) Allow users control over repartitioning

[ https://issues.apache.org/jira/browse/KAFKA-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15922911#comment-15922911 ] Matthias J. Sax commented on KAFKA-4835: Agreed. I just wanted to point out, that there a

[GitHub] kafka pull request #2679: HOTFIX: Fix apache headers in float serde class fi...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2679 --- 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-4840) There are are still cases where producer buffer pool will not remove waiters.

[ https://issues.apache.org/jira/browse/KAFKA-4840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean McCauliff updated KAFKA-4840: -- Description: There are several problems dealing with errors in BufferPool.allocate(int size,

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

Jay, thanks for your feedback > What if instead we called it KStreamsBuilder? That's the current name and I personally think it's not the best one. The main reason why I don't like KStreamsBuilder is, that we have the concepts of KStreams and KTables, and the builder creates both. However, the

Re: [DISCUSS] KIP-132: Augment KStream.print to allow extra parameters in the printed string

Marc, Thanks for the KIP. Can you please update the KIP in a way such that it is self contained. Right now, you link to all kind of other places making it hard to read the KIP. The KIP should be the "center of truth" -- if there is important information elsewhere, please c it into the KIP.

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

Guozhang, 1) I updated the KIP to option (b). 3) Agreed. So we leave this part out, and tackle it within KIP-130 -Matthias On 3/12/17 3:48 PM, Guozhang Wang wrote: > Thanks Matthias. > > 1) Given that TopologyDescription is for debugging purposes before > `KafkaStreams.start()`. I think the

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

Steven, thanks for your feedback. I am not sure about KafkaStreamsBuilder (even if agree that it is better than KStreamBuilder), because it sounds like a builder that creates a KafkaStreams instance. But that's of course not the case. It builds a Topology -- that was the reason to consider

[jira] [Resolved] (KAFKA-4891) kafka.request.logger TRACE regression

[ https://issues.apache.org/jira/browse/KAFKA-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-4891. - Resolution: Fixed > kafka.request.logger TRACE regression > -

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

See -- Failed to access build log java.io.IOException: remote file operation failed: /home/jenkins/jenkins-slave/workspace/kafka-trunk-jdk8 at

[jira] [Updated] (KAFKA-4891) kafka.request.logger TRACE regression

[ https://issues.apache.org/jira/browse/KAFKA-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4891: Fix Version/s: (was: 0.10.2.1) 0.11.0.0 > kafka.request.logger TRACE

[GitHub] kafka pull request #2679: HOTFIX: Fix apache headers in float serde class fi...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/2679 HOTFIX: Fix apache headers in float serde class files @hachikuji You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka

[jira] [Updated] (KAFKA-4891) kafka.request.logger TRACE regression

[ https://issues.apache.org/jira/browse/KAFKA-4891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-4891: Fix Version/s: 0.10.2.1 > kafka.request.logger TRACE regression >

[jira] [Commented] (KAFKA-4891) kafka.request.logger TRACE regression

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

[GitHub] kafka pull request #2678: KAFKA-4891 kafka.request.logger TRACE regression

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2678 --- 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-120: Cleanup Kafka Streams builder API

> On Mar 13, 2017, at 12:30 PM, Matthias J. Sax wrote: > > Jay, > > thanks for your feedback > >> What if instead we called it KStreamsBuilder? > > That's the current name and I personally think it's not the best one. > The main reason why I don't like KStreamsBuilder

[jira] [Commented] (KAFKA-4887) Enabling caching on a persistent window store breaks support for duplicate insertion

[ https://issues.apache.org/jira/browse/KAFKA-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15922826#comment-15922826 ] Elias Levy commented on KAFKA-4887: --- It is a bit complicated. I am abusing the {{RocksDBWnidowStore}}

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

looking at the KIP as it is now, looks like all *Options objects have a common timeout property. could it be extracted to a common AdminRequestOptions or something? On Thu, Mar 9, 2017 at 2:14 PM, Colin McCabe wrote: > Hi all, > > We've been discussing this for a while

[jira] [Commented] (KAFKA-4887) Enabling caching on a persistent window store breaks support for duplicate insertion

[ https://issues.apache.org/jira/browse/KAFKA-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15922789#comment-15922789 ] Guozhang Wang commented on KAFKA-4887: -- Thanks Elias, this does sound a bug to me. Just curious what

[jira] [Commented] (KAFKA-4859) Transient test failure: org.apache.kafka.streams.integration.JoinIntegrationTest.shouldCountClicksPerRegion (again)

[ https://issues.apache.org/jira/browse/KAFKA-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15922772#comment-15922772 ] Guozhang Wang commented on KAFKA-4859: -- [~original-brownbear] Thanks a lot for picking this up! Any

[jira] [Resolved] (KAFKA-4657) Improve test coverage of CompositeReadOnlyWindowStore

[ https://issues.apache.org/jira/browse/KAFKA-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4657. -- Resolution: Fixed Issue resolved by pull request 2672

[jira] [Commented] (KAFKA-4657) Improve test coverage of CompositeReadOnlyWindowStore

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

[jira] [Assigned] (KAFKA-4848) Stream thread getting into deadlock state while trying to get rocksdb lock in retryWithBackoff

[ https://issues.apache.org/jira/browse/KAFKA-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-4848: -- Assignee: Sachin Mittal > Stream thread getting into deadlock state while trying to

[jira] [Commented] (KAFKA-4848) Stream thread getting into deadlock state while trying to get rocksdb lock in retryWithBackoff

[ https://issues.apache.org/jira/browse/KAFKA-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15922762#comment-15922762 ] Guozhang Wang commented on KAFKA-4848: -- [~sjmittal] BTW I have added you to the contributor list. >

[GitHub] kafka pull request #2672: KAFKA-4657: Improve test coverage of CompositeRead...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2672 --- 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-120: Cleanup Kafka Streams builder API

Two things: 1. This is a minor thing but the proposed new name for KStreamBuilder is StreamsTopologyBuilder. I actually think we should not put topology in the name as topology is not a concept you need to understand at the kstreams layer right now. I'd think of three categories of

[jira] [Commented] (KAFKA-4769) Add Float serializer, deserializer, serde

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

[GitHub] kafka pull request #2554: KAFKA-4769: Add Float serializer, deserializer, se...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2554 --- 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-4769) Add Float serializer, deserializer, serde

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

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

the common "stack" we envision at linkedin would consist of (at least) the following components that add headers to every outgoing request: 1. auditing/"lineage" - appends a header containing "node" (hostname etc), time (UTC time) and destination (cluster/topic). these accumulate as requests get

[jira] [Commented] (KAFKA-4891) kafka.request.logger TRACE regression

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

[GitHub] kafka pull request #2678: KAFKA-4891 kafka.request.logger TRACE regression

GitHub user onurkaraman opened a pull request: https://github.com/apache/kafka/pull/2678 KAFKA-4891 kafka.request.logger TRACE regression Both the headers and requests have regressed to just show object ids instead of their contents from their underlying structs. I'm guessing this

[jira] [Commented] (KAFKA-4574) Transient failure in ZooKeeperSecurityUpgradeTest.test_zk_security_upgrade with security_protocol = SASL_PLAINTEXT, SSL

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

[GitHub] kafka pull request #2677: MINOR: set trace logging for zookeeper upgrade tes...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/2677 MINOR: set trace logging for zookeeper upgrade test This adds logging which will hopefully help root cause https://issues.apache.org/jira/browse/KAFKA-4574. You can merge this pull request into a

[jira] [Created] (KAFKA-4891) kafka.request.logger TRACE regression

Onur Karaman created KAFKA-4891: --- Summary: kafka.request.logger TRACE regression Key: KAFKA-4891 URL: https://issues.apache.org/jira/browse/KAFKA-4891 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-4890) State directory being deleted when another thread holds the lock

[ https://issues.apache.org/jira/browse/KAFKA-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4890: -- Description: Looks like a state directory is being cleaned up when another thread already has the

Re: [DISCUSS] KIP-113: Support replicas movement between log directories

Hi, Dong, Thanks for the updated KIP. Some more comments below. 10. For the .move log, do we perform any segment deletion (based on retention) or log cleaning (if a compacted topic)? Or do we only enable that after the swap? 11. kafka-reassign-partitions.sh 11.1 If all reassigned replicas are

[jira] [Created] (KAFKA-4890) State directory being deleted when another thread holds the lock

Damian Guy created KAFKA-4890: - Summary: State directory being deleted when another thread holds the lock Key: KAFKA-4890 URL: https://issues.apache.org/jira/browse/KAFKA-4890 Project: Kafka

[jira] [Updated] (KAFKA-4128) Kafka broker losses messages when zookeeper session times out

[ https://issues.apache.org/jira/browse/KAFKA-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4128: --- Labels: reliability (was: ) > Kafka broker losses messages when zookeeper session times out >

[DISCUSS] KIP-132: Augment KStream.print to allow extra parameters in the printed string

Dear all, The following describes KIP-132, which I just created. See: https://cwiki.apache.org/confluence/display/KAFKA/KIP-132+-+Augment+KStream.print+to+allow+extra+parameters+in+the+printed+string Motivation As for now, KStream#print leads to a predefined output where key and value are

[jira] [Commented] (KAFKA-4835) Allow users control over repartitioning

[ https://issues.apache.org/jira/browse/KAFKA-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907523#comment-15907523 ] Michal Borowiecki commented on KAFKA-4835: -- My point above was that if the customerRef (which is

Re: Add to contributor list

Thank you Raja Guru T On Mon, Mar 13, 2017 at 3:24 AM, Guozhang Wang wrote: > Done. > > Guozhang > > On Sun, Mar 12, 2017 at 11:19 AM, Raja Guru Thirumavalavan < > geeky.rajag...@gmail.com> wrote: > > > Hi,,Can you please add me to contributor list. > > or is there any other

Re: Doubts regarding KafkaProducer implemetation

Hi, java producer waits for the metadata of the given topic to be available. We will get TimeoutException if we didn't get metadata within max.block.ms. As observed by you, this behavior is different from old producer. "retries" config is not applicable to metadata fetch. We can adjust

[jira] [Created] (KAFKA-4889) 2G8lc

Vamsi Jakkula created KAFKA-4889: Summary: 2G8lc Key: KAFKA-4889 URL: https://issues.apache.org/jira/browse/KAFKA-4889 Project: Kafka Issue Type: Task Reporter: Vamsi Jakkula

Doubts regarding KafkaProducer implemetation

Hi, We have three brokers in a cluster with replication factor is 3. We are using Kafka-0.10.0.1. We see some failures on metadata timeout exceptions while producing. We have configured retries=3 and max in flight request=1. After comparing with the old scala Producer code found that in new

[jira] [Commented] (KAFKA-4829) Improve logging of StreamTask commits

[ https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907078#comment-15907078 ] Nicolas Fouché commented on KAFKA-4829: --- Some comments on how we felt that some logs were missing at

[jira] [Resolved] (KAFKA-4884) __consumer_offsets topic processing consuming all resources

[ https://issues.apache.org/jira/browse/KAFKA-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Coupland resolved KAFKA-4884. - Resolution: Invalid > __consumer_offsets topic processing consuming all resources >

[jira] [Comment Edited] (KAFKA-4277) creating ephemeral node already exist

[ https://issues.apache.org/jira/browse/KAFKA-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906972#comment-15906972 ] Wrikken edited comment on KAFKA-4277 at 3/13/17 7:53 AM: - [~junrao]: it was not

[jira] [Commented] (KAFKA-4277) creating ephemeral node already exist

[ https://issues.apache.org/jira/browse/KAFKA-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906972#comment-15906972 ] Wrikken commented on KAFKA-4277: [~junrao]: it was not there several hours later, but I haven't been able

Re: SASL security issue

I'd like to proceed with SASL implementation enhancement: https://issues.apache.org/jira/browse/KAFKA-4874 As this feature introduces new configuration parameter, I think KIP would be of use. Is there any chance I can get permissions to wiki in order to create KIP document? Provided it is