Re: [VOTE] KIP-106 - Default unclean.leader.election.enabled True => False

+1 On Wed, Jan 11, 2017 at 10:56 AM, Ben Stopford wrote: > Looks like there was a good consensus on the discuss thread for KIP-106 so > lets move to a vote. > > Please chime in if you would like to change the default for > unclean.leader.election.enabled from true to false. > > https://cwiki.apac

Re: [VOTE] KIP-106 - Default unclean.leader.election.enabled True => False

+1 (non-binding) > On Jan 11, 2017, at 11:33 AM, Jay Kreps wrote: > > +1 > > On Wed, Jan 11, 2017 at 10:56 AM, Ben Stopford wrote: > >> Looks like there was a good consensus on the discuss thread for KIP-106 so >> lets move to a vote. >> >> Please chime in if you would like to change the def

[GitHub] kafka pull request #1446: KAFKA-3715: add granular metrics per node

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1446 --- 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: [VOTE] KIP-106 - Default unclean.leader.election.enabled True => False

+1 On Wed, Jan 11, 2017 at 10:56 AM, Ben Stopford wrote: > Looks like there was a good consensus on the discuss thread for KIP-106 so > lets move to a vote. > > Please chime in if you would like to change the default for > unclean.leader.election.enabled from true to false. > > https://cwiki.apa

[GitHub] kafka pull request #2264: Kafka 4507: The client should send older versions ...

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

[GitHub] kafka pull request #2182: ConfigDef experimentation - support List and Ma...

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

Re: [VOTE] KIP-106 - Default unclean.leader.election.enabled True => False

+1 On Wed, Jan 11, 2017 at 11:06 AM, Jason Gustafson wrote: > +1 > > On Wed, Jan 11, 2017 at 10:56 AM, Ben Stopford wrote: > > > Looks like there was a good consensus on the discuss thread for KIP-106 > so > > lets move to a vote. > > > > Please chime in if you would like to change the default

Re: [VOTE] KIP-106 - Default unclean.leader.election.enabled True => False

+1 On Wed, Jan 11, 2017 at 10:56 AM, Ben Stopford wrote: > Looks like there was a good consensus on the discuss thread for KIP-106 so > lets move to a vote. > > Please chime in if you would like to change the default for > unclean.leader.election.enabled from true to false. > > https://cwiki.apa

[GitHub] kafka pull request #2343: [WIP] Client Compatibility

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

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

See

[VOTE] KIP-106 - Default unclean.leader.election.enabled True => False

Looks like there was a good consensus on the discuss thread for KIP-106 so lets move to a vote. Please chime in if you would like to change the default for unclean.leader.election.enabled from true to false. https://cwiki.apache.org/confluence/display/KAFKA/%5BWIP%5D+KIP-106+-+Change+Default+uncl

Re: [VOTE] Vote for KIP-101 - Leader Epochs

OK - my mistake was mistaken! There is consensus. This KIP has been accepted. On Wed, Jan 11, 2017 at 6:48 PM Ben Stopford wrote: > Sorry - my mistake. Looks like I still need one more binding vote. Is > there a committer out there that could add their vote? > > B > > On Wed, Jan 11, 2017 at 6:4

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

See Changes: [wangguoz] KAFKA-4481: relax streams api type contraints -- [...truncated 18260 lines...] org.apache.kafka.streams.KafkaStreamsTest > testCannotStartOnceClosed PASSED org.apache.k

Re: [VOTE] Vote for KIP-101 - Leader Epochs

Sorry - my mistake. Looks like I still need one more binding vote. Is there a committer out there that could add their vote? B On Wed, Jan 11, 2017 at 6:44 PM Ben Stopford wrote: > So I believe we can mark this as Accepted. I've updated the KIP page. > Thanks for the input everyone. > > On Fri,

Re: [VOTE] Vote for KIP-101 - Leader Epochs

So I believe we can mark this as Accepted. I've updated the KIP page. Thanks for the input everyone. On Fri, Jan 6, 2017 at 9:31 AM Ben Stopford wrote: > Thanks Joel. I'll fix up the pics to make them consistent on nomenclature. > > > B > > On Fri, Jan 6, 2017 at 2:39 AM Joel Koshy wrote: > > (

[GitHub] kafka pull request #2292: MINOR: Update rocksDB dependency to 5.0.1

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2292 --- 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-4577) NPE in ControllerChannelManager.scala::addUpdateMetadataRequestForBrokers

[ https://issues.apache.org/jira/browse/KAFKA-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818922#comment-15818922 ] Scott Reynolds commented on KAFKA-4577: --- Nothing interesting was happening, obviousl

[jira] [Commented] (KAFKA-4060) Remove ZkClient dependency in Kafka Streams

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

[GitHub] kafka pull request #1884: KAFKA-4060: Remove zk client dependency in kafka s...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1884 --- 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-4060) Remove ZkClient dependency in Kafka Streams

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

[GitHub] kafka pull request #2345: MINOR: ConfigDef `parseType` exception message upd...

GitHub user Kamal15 opened a pull request: https://github.com/apache/kafka/pull/2345 MINOR: ConfigDef `parseType` exception message updated. - When Kafka configurations are provided programmatically, for the below configuration incorrect error message gets printed. * co

[jira] [Commented] (KAFKA-4481) Relax Kafka Streams API type constraints

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

[GitHub] kafka pull request #2205: KAFKA-4481: relax streams api type contraints

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2205 --- 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-4481) Relax Kafka Streams API type constraints

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

[GitHub] kafka pull request #2340: MINOR: ConfigDef `parseType` exception message upd...

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

Re: [DISCUSS] KIP-81: Max in-flight fetches

Ok thanks for the clarification. I agree too, I don't want a new config parameter. From the numbers we gathered (see Edoardo's comment above), it shouldn't be too hard to pick a meaningful value On Wed, Jan 11, 2017 at 3:58 PM, Rajini Sivaram wrote: > Mickael, > > I had based the comment on KIP-7

[jira] [Commented] (KAFKA-3601) fail fast when newer client connecting to older server

[ https://issues.apache.org/jira/browse/KAFKA-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818711#comment-15818711 ] Ismael Juma commented on KAFKA-3601: There's a bug in 0.9.0.1 that prevents it from di

[jira] [Commented] (KAFKA-3601) fail fast when newer client connecting to older server

[ https://issues.apache.org/jira/browse/KAFKA-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818703#comment-15818703 ] Colin P. McCabe commented on KAFKA-3601: [~cpennello_opentable], I believe 0.8, 0.

Re: [DISCUSS] KIP-81: Max in-flight fetches

Mickael, I had based the comment on KIP-72 description where brokers were muting all client channels once memory pool was empty. Having reviewed the PR today, I think it may be fine to delay muting and allocate small buffers outside of the pool. I would still not want to have a config parameter to

Re: [DISCUSS] KIP-107: Add purgeDataBefore() API in AdminClient

Hi Dong, As per "If the message's offset is below low_watermark, then it should have been deleted by log retention policy." ---> I am not sure if I understand this correctly. Do you mean to say that the low_watermark will be updated only when the log retention fires on the broker? Thanks, Mayu

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

while HTTP-style (string, string) are the most common and most familiar, there is a very significant impact on msg size, especially given that some payloads are literally a few integers (think stock quotes) and would be dwarfed by an http-like header segment. I think we're ok with not allowing for

Re: [DISCUSS] KIP-81: Max in-flight fetches

Rajini, Why do you think we don't want to do the same for brokers ? It feels like brokers would be affected the same way and could end up delaying group/hearbeat requests. Also given queued.max.requests it seems unlikely that small requests (<<1Kb) being allocated outside of the memory pool would

[jira] [Created] (KAFKA-4618) Enable clients to "re-bootstrap" in the event of a full cluster migration

Dustin Cote created KAFKA-4618: -- Summary: Enable clients to "re-bootstrap" in the event of a full cluster migration Key: KAFKA-4618 URL: https://issues.apache.org/jira/browse/KAFKA-4618 Project: Kafka

[jira] [Commented] (KAFKA-960) Upgrade Metrics to 3.x

[ https://issues.apache.org/jira/browse/KAFKA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818554#comment-15818554 ] Andrei Nechaev commented on KAFKA-960: -- Hello everyone, I created a pull request rela

[jira] [Updated] (KAFKA-4614) Long GC pause harming broker performance which is caused by mmap objects created for OffsetIndex

[ https://issues.apache.org/jira/browse/KAFKA-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4614: --- Labels: latency performance (was: ) > Long GC pause harming broker performance which is caused by mma

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression

Hi Ismael, 1. In the case of compression output, yes, lz4 is producing the smaller output than gzip. In fact, my benchmark was inspired by  MessageCompressionTest#testCompressSize unit test and the result is same - 396 bytes for gzip and 387 bytes for lz4. 2. I agree that my (former) approach ca

[GitHub] kafka pull request #2344: MINOR: add file append to connect-log4j.properties

GitHub user berryma4 opened a pull request: https://github.com/apache/kafka/pull/2344 MINOR: add file append to connect-log4j.properties The default log4j for kafka connect should include a log to file. (It would be nice) You can merge this pull request into a Git repository by

[GitHub] kafka pull request #2343: [WIP] Client Compatibility

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2343 [WIP] Client Compatibility Temporary PR to run tests in Jenkins, this will be merged to #2264 once @cmccabe comes online. You can merge this pull request into a Git repository by running: $ git

Re: Subscribe to mailing list

Hi Abhishek, Please follow the instructions here https://kafka.apache.org/contact. For your purpose the users list would be more appropriate I feel. -dhwani On Wednesday 11 January 2017 03:15 PM, Barot, Abhishek wrote: Hi Team, I would like to subscribe for the mailing list ( dev@kafka.apa

Subscribe to mailing list

Hi Team, I would like to subscribe for the mailing list ( dev@kafka.apache.org ). I would like to post few queries we've around setting up KAFKA cluster in our production Environment with respect to ideal configuration for 6 node cluster across 3 data centers. Than

Re: Build problems in Eclipse dev environment setup

Hi Edoardo, These kind of inconsistencies do not pose problems in most cases. For instance I was able to get things working in Eclipse by doing a full build on CLI and then importing the gradle eclipse plugin generated .project and .classpath files in eclipse. But as a counter example, the g

[jira] [Work started] (KAFKA-3714) Allow users greater access to register custom streams metrics

[ https://issues.apache.org/jira/browse/KAFKA-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3714 started by Eno Thereska. --- > Allow users greater access to register custom streams metrics > -

Re: Build problems in Eclipse dev environment setup

Just my personal preference the different output folders have not been annoying to me. I know that the eclipse compile output is different from the output generated running gradle on the CLI and am happy with that. -- Edoardo Comar IBM MessageHub e

[jira] [Commented] (KAFKA-4617) gradle-generated core eclipse project has incorrect source folder structure

[ https://issues.apache.org/jira/browse/KAFKA-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818047#comment-15818047 ] Edoardo Comar commented on KAFKA-4617: -- Hi [~dhwanikatagade], thanks I saw that threa

[jira] [Commented] (KAFKA-4617) gradle-generated core eclipse project has incorrect source folder structure

[ https://issues.apache.org/jira/browse/KAFKA-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818024#comment-15818024 ] Dhwani Katagade commented on KAFKA-4617: The gradle eclipse plugin seem to have ot

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression

Thanks Dongjin. I highly recommend using JMH for the benchmark, the existing one has a few problems that could result in unreliable results. Also, it's a bit surprising that LZ4 is producing smaller output than gzip. Is that right? Ismael On Wed, Jan 11, 2017 at 10:20 AM, Dongjin Lee wrote: > I

[jira] [Created] (KAFKA-4617) gradle-generated core eclipse project has incorrect source folder structure

Edoardo Comar created KAFKA-4617: Summary: gradle-generated core eclipse project has incorrect source folder structure Key: KAFKA-4617 URL: https://issues.apache.org/jira/browse/KAFKA-4617 Project: Ka

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression

Ismael, I pushed the benchmark code I used, with some updates (iteration: 20 -> 1000). I also updated the KIP page with the updated benchmark results. Please take a review when you are free. The attached screenshot shows how to run the benchmarker. Thanks, Dongjin On Tue, Jan 10, 2017 at 8:03 PM

[jira] [Commented] (KAFKA-4616) Message log is seen when kafka-producer-perf-test.sh is running and any broker restarted in middle in-between

[ https://issues.apache.org/jira/browse/KAFKA-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817886#comment-15817886 ] huxi commented on KAFKA-4616: - Could you set acks = -1 and retry the producer to see if there

[jira] [Comment Edited] (KAFKA-4614) Long GC pause harming broker performance which is caused by mmap objects created for OffsetIndex

[ https://issues.apache.org/jira/browse/KAFKA-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817849#comment-15817849 ] huxi edited comment on KAFKA-4614 at 1/11/17 10:00 AM: --- Great catch

[jira] [Created] (KAFKA-4616) Message log is seen when kafka-producer-perf-test.sh is running and any broker restarted in middle in-between

sandeep kumar singh created KAFKA-4616: -- Summary: Message log is seen when kafka-producer-perf-test.sh is running and any broker restarted in middle in-between Key: KAFKA-4616 URL: https://issues.apache.org/

[jira] [Commented] (KAFKA-4614) Long GC pause harming broker performance which is caused by mmap objects created for OffsetIndex

[ https://issues.apache.org/jira/browse/KAFKA-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817849#comment-15817849 ] huxi commented on KAFKA-4614: - Great catch for the whole things. As for the unmap things, se

[jira] [Commented] (KAFKA-4614) Long GC pause harming broker performance which is caused by mmap objects created for OffsetIndex

[ https://issues.apache.org/jira/browse/KAFKA-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817826#comment-15817826 ] Ismael Juma commented on KAFKA-4614: [~kawamuray], thanks for reporting this. Looking

[jira] [Created] (KAFKA-4615) AdminClient.send function poll without timeout

Guillaume Grossetie created KAFKA-4615: -- Summary: AdminClient.send function poll without timeout Key: KAFKA-4615 URL: https://issues.apache.org/jira/browse/KAFKA-4615 Project: Kafka Issu

[jira] [Commented] (KAFKA-4614) Long GC pause harming broker performance which is caused by mmap objects created for OffsetIndex

[ https://issues.apache.org/jira/browse/KAFKA-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817627#comment-15817627 ] Yuto Kawamura commented on KAFKA-4614: -- I've tried to fix this and now I'm testing pa

[jira] [Comment Edited] (KAFKA-4614) Long GC pause harming broker performance which is caused by mmap objects created for OffsetIndex

[ https://issues.apache.org/jira/browse/KAFKA-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15817627#comment-15817627 ] Yuto Kawamura edited comment on KAFKA-4614 at 1/11/17 8:19 AM: -

Re: [VOTE] KIP-104: Granular Sensors for Streams

Thank you, this KIP is now adopted. The votes were: Binding +1: Neha, Guozhang, Ismael, Sriram Non-binding +1: Bill, Matthias, Damian Thank you Eno & Aarti > On 10 Jan 2017, at 04:52, Neha Narkhede wrote: > > +1. Thanks Eno! > On Mon, Jan 9, 2017 at 1:05 PM Guozhang Wang wrote: > >> +1, than

[jira] [Created] (KAFKA-4614) Long GC pause harming broker performance which is caused by mmap objects created for OffsetIndex

Yuto Kawamura created KAFKA-4614: Summary: Long GC pause harming broker performance which is caused by mmap objects created for OffsetIndex Key: KAFKA-4614 URL: https://issues.apache.org/jira/browse/KAFKA-4614

<    1   2