Re: [VOTE] 2.0.0 RC0

[Thomas Crayford]

+1 (non-binding) Heroku has run our usual set of upgrade and performance
tests, and we haven't found any notable issues through that.

On Sat, Jun 23, 2018 at 12:30 AM, Vahid S Hashemian <
vahidhashem...@us.ibm.com> wrote:

> +1 (non-binding)
>
> Built from source and ran quickstart successfully on Ubuntu (with Java 8
> and Java 9).
>
> Thanks Rajini!
> --Vahid
>
>

Re: Running kafka in containers

[Thomas Crayford]

We (heroku) have run databases in containers since 2012, and kafka works
just as well as everything else. So: yes

Re: Kafka in virtualized environments

[Thomas Crayford]

We run many thousands of clusters on EC2 without notable issues, and
achieve great performance there. The real thing that matters is how good
your virtualization layer is and how much of a performance impact it has.
E.g. in modern EC2, the performance overhead of using virtualized IO is
around 1-5% tops, which isn't enough of an impact for kafka to really
notice.

On Thu, Nov 30, 2017 at 11:56 AM, Wim Van Leuven <
wim.vanleu...@highestpoint.biz> wrote:

> We are running kafka on openstack for a testing/staging environment.
>
> It runs good and stable, but it obviously is way slower than bare-metal.
> Simple reason is the distance to the disk (as with any IO batch oriented
> system on virtualisation) and virtual network.
>
> HTH
> -wim
>
>
> On Thu, 30 Nov 2017 at 11:22 Viktor Somogyi 
> wrote:
>
> > Hi folks,
> >
> > Recently I bumped into an interesting question: using kafka in
> virtualized
> > environments, such as vmware. I'm not really familiar with virtualization
> > in-depth (how disk virtualization works, what are the OS level supports
> > etc.), therefore I think this is an interesting discussion from Kafka's
> > point. As far as I know Kafka is designed for a non-virtualized
> environment
> > mainly (although I haven't seen it explicitly anywhere) but thinking of
> > it's hard reliance on disk optimization I always assumed this.
> >
> > Anyone has experiences with virtualized Kafka? Are you aware of any pain
> > points that people should consider (or performance issues)?
> > Are there any publications on this topic?
> >
> > Regards,
> > Viktor
> >
>

Re: Kafka JVM heap limit

[Thomas Crayford]

Hi there,

There are some cases you may want to consider bigger heaps. Heroku runs
some clusters with 20GB heaps now, because said clusters:

1. Use SSL exclusively for connectivity. SSL means message bytes traverse
the JVM heap during encryption/etc, which uses more memory
2. Have a high number of partitions and connected clients. Each partition
uses some amount of memory, as does each connected client.

We've still had a great time with the G1 collector (which is the default in
kafka for a long time now) even with the larger heap.

On Wed, Nov 8, 2017 at 1:48 PM, John Yost  wrote:

> In addition, in my experience, a memory heap > 8 GB leads to long GC pauses
> which causes the ISR statuses to constantly change, leading to an unstable
> cluster.
>
> --John
>
> On Wed, Nov 8, 2017 at 4:30 AM, chidigam .  wrote:
>
> > Meaning, already read the doc, but couldn't relate, having large Heap for
> > JVM will not help
> > Now it all make sense.
> > Many thanks.
> > Bhanu
> >
> > On Wed, Nov 8, 2017 at 2:34 PM, chidigam . 
> wrote:
> >
> > > Hi Jakub,
> > > Thank you very much. I have read this concept I/O cache in design
> > section.
> > > But couldn't connect the dots.
> > >
> > > Regards
> > > Bhanu
> > >
> > > On Wed, Nov 8, 2017 at 2:10 PM, Jakub Scholz  wrote:
> > >
> > >> This is probably because Kafka uses quite heavily the disk cache
> > >> maintained
> > >> by the operating system instead of storing messages in the JVM memory.
> > So
> > >> the requirements for the heap memory can be fairly small. The design
> > >> section of the documentation describes the details:
> > >> http://kafka.apache.org/documentation/#design
> > >>
> > >> Jakub
> > >>
> > >> On Wed, Nov 8, 2017 at 9:30 AM, chidigam . 
> > wrote:
> > >>
> > >> > Hi All,
> > >> > I have basic question on Kafka JVM configuration, in most of forums
> I
> > >> have
> > >> > seen max heap as 8GB.  Why it is not recommended beyond that. Is
> there
> > >> any
> > >> > design limitation ?
> > >> > Any help in this regards is highly appreciated.
> > >> >
> > >> > Regards
> > >> > Bhanu
> > >> >
> > >>
> > >
> > >
> >
>

Re: [VOTE] 1.0.0 RC1

[Thomas Crayford]

Hi Ghouzang,

We have indeed started our performance testing at Heroku for RC1. However,
we are more than happy to retest once RC2 is available, especially given
larger amounts of time to do so.

Thanks

Tom Crayford
Heroku Kafka

On Tue, Oct 17, 2017 at 2:50 AM, Ismael Juma  wrote:

> If you don't use the default Scala version, you have to set the
> SCALA_VERSION environment variable for the bin scripts to work.
>
> Ismael
>
> On 17 Oct 2017 1:30 am, "Vahid S Hashemian" 
> wrote:
>
> Hi Guozhang,
>
> I'm not sure if this should be covered by "Java 9 support" in the RC note,
> but when I try to build jars from source using Java 9 (./gradlew
> -PscalaVersion=2.12 jar) even though the build reports as succeeded, it
> doesn't seem to have been successful:
>
> $ bin/zookeeper-server-start.sh config/zookeeper.properties
> Error: Could not find or load main class
> org.apache.zookeeper.server.quorum.QuorumPeerMain
> Caused by: java.lang.ClassNotFoundException:
> org.apache.zookeeper.server.quorum.QuorumPeerMain
>
> Please advise if I'm missing something.
>
> Thanks.
> --Vahid
>
>
>
>
> From:   Guozhang Wang 
> To: "d...@kafka.apache.org" ,
> "users@kafka.apache.org" , kafka-clients
> 
> Date:   10/13/2017 01:12 PM
> Subject:[VOTE] 1.0.0 RC1
>
>
>
> Hello Kafka users, developers and client-developers,
>
> This is the second candidate for release of Apache Kafka 1.0.0.
>
> It's worth noting that starting in this version we are using a different
> version protocol with three digits: *major.minor.bug-fix*
>
> Any and all testing is welcome, but the following areas are worth
> highlighting:
>
> 1. Client developers should verify that their clients can produce/consume
> to/from 1.0.0 brokers (ideally with compressed and uncompressed data).
> 2. Performance and stress testing. Heroku and LinkedIn have helped with
> this in the past (and issues have been found and fixed).
> 3. End users can verify that their apps work correctly with the new
> release.
>
> This is a major version release of Apache Kafka. It includes 29 new KIPs.
> See the release notes and release plan
> (*https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_
> confluence_pages_viewpage.action-3FpageId-3D71764913&d=
> DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=Q_itwloTQj3_xUKl7Nzswo6KE4Nj-
> kjJc7uSVcviKUc&m=VyLkHrCpgoKOD8nDthZgGw_OWk2y2QfKYsXitTyAHHM&s=
> tT9k0x5RvXtHEtLzp03BA1Y8DAgHzgCXD7UjqP7oiKE&e=
> <
> https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.
> apache.org_confluence_pages_viewpage.action-3FpageId-
> 3D71764913&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=Q_
> itwloTQj3_xUKl7Nzswo6KE4Nj-
> kjJc7uSVcviKUc&m=VyLkHrCpgoKOD8nDthZgGw_OWk2y2QfKYsXitTyAHHM&s=
> tT9k0x5RvXtHEtLzp03BA1Y8DAgHzgCXD7UjqP7oiKE&e=
> >*)
> for more details. A few feature highlights:
>
> * Java 9 support with significantly faster TLS and CRC32C implementations
> (KIP)
> * JBOD improvements: disk failure only disables failed disk but not the
> broker (KIP-112/KIP-113)
> * Newly added metrics across all the modules (KIP-164, KIP-168, KIP-187,
> KIP-188, KIP-196)
> * Kafka Streams API improvements (KIP-120 / 130 / 138 / 150 / 160 / 161),
> and drop compatibility "Evolving" annotations
>
> Release notes for the 1.0.0 release:
> *https://urldefense.proofpoint.com/v2/url?u=http-3A__home.apache.org_-
> 7Eguozhang_kafka-2D1.0.0-2Drc1_RELEASE-5FNOTES.html&d=
> DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=Q_itwloTQj3_xUKl7Nzswo6KE4Nj-
> kjJc7uSVcviKUc&m=VyLkHrCpgoKOD8nDthZgGw_OWk2y2QfKYsXitTyAHHM&s=
> xopSUD2TETEI5y8kxHM4P-jUdUKUIiUig2xVwabgDq8&e=
> <
> https://urldefense.proofpoint.com/v2/url?u=http-3A__home.
> apache.org_-7Eguozhang_kafka-2D1.0.0-2Drc1_RELEASE-5FNOTES.
> html&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=Q_itwloTQj3_xUKl7Nzswo6KE4Nj-
> kjJc7uSVcviKUc&m=VyLkHrCpgoKOD8nDthZgGw_OWk2y2QfKYsXitTyAHHM&s=
> xopSUD2TETEI5y8kxHM4P-jUdUKUIiUig2xVwabgDq8&e=
> >*
>
>
>
> *** Please download, test and vote by Tuesday, October 13, 8pm PT
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__kafka.
> apache.org_KEYS&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=Q_
> itwloTQj3_xUKl7Nzswo6KE4Nj-kjJc7uSVcviKUc&m=VyLkHrCpgoKOD8nDthZgGw_
> OWk2y2QfKYsXitTyAHHM&s=FfLcWlN8ODpZ2m1KliMfp35duIxif3FNnptY5-9JKWU&e=
>
>
> * Release artifacts to be voted upon (source and binary):
> *https://urldefense.proofpoint.com/v2/url?u=http-3A__home.apache.org_-
> 7Eguozhang_kafka-2D1.0.0-2Drc1_&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=Q_
> itwloTQj3_xUKl7Nzswo6KE4Nj-kjJc7uSVcviKUc&m=VyLkHrCpgoKOD8nDthZgGw_
> OWk2y2QfKYsXitTyAHHM&s=bcWIqj27_tkoj-fnEzcLdP8uGXyAt6gS9KUy12WF1FE&e=
> <
> https://urldefense.proofpoint.com/v2/url?u=http-3A__home.
> apache.org_-7Eguozhang_kafka-2D1.0.0-2Drc1_&d=DwIBaQ&c=jf_
> iaSHvJObTbx-siA1ZOg&r=Q_itwloTQj3_xUKl7Nzswo6KE4Nj-kjJc7uSVcviKUc&m=
> VyLkHrCpgoKOD8nDthZgGw_OWk2y2QfKYsXitTyAHHM&s=bcWIqj27_tkoj-
> fnEzcLdP8uGXyAt6gS9KUy12WF1FE&e=
> >*
>
> * Maven artifacts to be voted upon:
> https://urldefense.proofpoint.com/v2/

Re: [VOTE] 1.0.0 RC1

[Thomas Crayford]

Hi Guozhang,

This says the due date on the testing is October 13th, which was the day
this email was sent. Is that accurate, or is it meant to read October 17th,
which is next Tuesday?

I feel like this short a testing window for a 1.0 RC is a little low, as
1.0 is clearly a big announcement of stability, and folk should be given
enough time to do thorough testing.

Thanks

Tom

On Fri, Oct 13, 2017 at 9:12 PM, Guozhang Wang  wrote:

> Hello Kafka users, developers and client-developers,
>
> This is the second candidate for release of Apache Kafka 1.0.0.
>
> It's worth noting that starting in this version we are using a different
> version protocol with three digits: *major.minor.bug-fix*
>
> Any and all testing is welcome, but the following areas are worth
> highlighting:
>
> 1. Client developers should verify that their clients can produce/consume
> to/from 1.0.0 brokers (ideally with compressed and uncompressed data).
> 2. Performance and stress testing. Heroku and LinkedIn have helped with
> this in the past (and issues have been found and fixed).
> 3. End users can verify that their apps work correctly with the new
> release.
>
> This is a major version release of Apache Kafka. It includes 29 new KIPs.
> See the release notes and release plan
> (*https://cwiki.apache.org/confluence/pages/viewpage.
> action?pageId=71764913
>  >*)
> for more details. A few feature highlights:
>
> * Java 9 support with significantly faster TLS and CRC32C implementations
> (KIP)
> * JBOD improvements: disk failure only disables failed disk but not the
> broker (KIP-112/KIP-113)
> * Newly added metrics across all the modules (KIP-164, KIP-168, KIP-187,
> KIP-188, KIP-196)
> * Kafka Streams API improvements (KIP-120 / 130 / 138 / 150 / 160 / 161),
> and drop compatibility "Evolving" annotations
>
> Release notes for the 1.0.0 release:
> *http://home.apache.org/~guozhang/kafka-1.0.0-rc1/RELEASE_NOTES.html
> *
>
>
>
> *** Please download, test and vote by Tuesday, October 13, 8pm PT
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> http://kafka.apache.org/KEYS
>
> * Release artifacts to be voted upon (source and binary):
> *http://home.apache.org/~guozhang/kafka-1.0.0-rc1/
> *
>
> * Maven artifacts to be voted upon:
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
>
> * Javadoc:
> *http://home.apache.org/~guozhang/kafka-1.0.0-rc1/javadoc/
> *
>
> * Tag to be voted upon (off 1.0 branch) is the 1.0.0-rc1 tag:
>
> https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=tag;h=
> 9424d29dbf0a3c538215b0b98b1e6b956481e4d5
>
> * Documentation:
> Note the documentation can't be pushed live due to changes that will not go
> live until the release. You can manually verify by downloading
> http://home.apache.org/~guozhang/kafka-1.0.0-rc1/
> kafka_2.11-1.0.0-site-docs.tgz
>
> * Successful Jenkins builds for the 1.0.0 branch:
> Unit/integration tests: https://builds.apache.org/job/kafka-1.0-jdk7/31/
> System test: https://jenkins.confluent.io/job/system-test-kafka-1.0/1/
>
>
> /**
>
>
> Thanks,
> -- Guozhang
>

Re: Kafka 0.11.0.0

[Thomas Crayford]

0.11.0.0 is a brand new release, with a very large number of changes
compared to the previous stable release (0.10.2.1). As a thing that stores
data, I would not recommend you switch to it without a very large amount of
testing and validation, probably involving running a shadow setup of your
production alongside.

On Mon, Aug 14, 2017 at 5:15 AM, Srikanth Sampath  wrote:

> Hi,
> We are currently on 0.8.2.2 in production and are planning on moving to the
> latest stable release which currently is 0.11.0.0.  Have a few questions:
>
> * Folks who are on 0.11.0.0 in production - can you comment on how stable
> is it?  Any problems?
>
> * Usually, I look for a maintenance release, is one planned for 0.11.x?  If
> so, is 0.11.0.1 or such planned - and when?
>
> * How is 0.10.2.1 in comparison?   Why would you recommend me or not to
> move to 0.11.0.0 on a practical note?
>
> Thanks a bunch in advance.
> -Srikanth
>