[jira] [Comment Edited] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319273#comment-15319273 ] Maysam Yabandeh edited comment on KAFKA-3693 at 6/10/16 4:00 AM: -

[jira] [Comment Edited] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15316991#comment-15316991 ] Maysam Yabandeh edited comment on KAFKA-3693 at 6/10/16 3:57 AM: -

[jira] [Comment Edited] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15315055#comment-15315055 ] Maysam Yabandeh edited comment on KAFKA-3693 at 6/10/16 3:54 AM: -

[jira] [Commented] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323801#comment-15323801 ] Maysam Yabandeh commented on KAFKA-3693: [~junrao] Yes, you seem to be right. The controller

[jira] [Commented] (KAFKA-3821) Allow Kafka Connect source tasks to produce offset without writing to topics

[ https://issues.apache.org/jira/browse/KAFKA-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323726#comment-15323726 ] Randall Hauch commented on KAFKA-3821: -- [~ewencp], I'm not sure a {{data}} field is that much

[jira] [Commented] (KAFKA-2934) Offset storage file configuration in Connect standalone mode is not included in StandaloneConfig

[ https://issues.apache.org/jira/browse/KAFKA-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323719#comment-15323719 ] Ewen Cheslack-Postava commented on KAFKA-2934: -- [~davispw] How are you doing that without

[jira] [Commented] (KAFKA-3801) Provide static serialize() and deserialize() for use as method references

[ https://issues.apache.org/jira/browse/KAFKA-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323718#comment-15323718 ] Jeff Klukas commented on KAFKA-3801: Let me give more context for the example. We have an application

[jira] [Commented] (KAFKA-2934) Offset storage file configuration in Connect standalone mode is not included in StandaloneConfig

[ https://issues.apache.org/jira/browse/KAFKA-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323697#comment-15323697 ] Peter Davis commented on KAFKA-2934: After upgrading to 0.10, discovered that this fix causes

[jira] [Comment Edited] (KAFKA-3816) Provide more context in Kafka Connect log messages

[ https://issues.apache.org/jira/browse/KAFKA-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323684#comment-15323684 ] Randall Hauch edited comment on KAFKA-3816 at 6/10/16 1:11 AM: --- {quote} One

[jira] [Comment Edited] (KAFKA-3816) Provide more context in Kafka Connect log messages

[ https://issues.apache.org/jira/browse/KAFKA-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323684#comment-15323684 ] Randall Hauch edited comment on KAFKA-3816 at 6/10/16 1:07 AM: --- {quote} One

[jira] [Commented] (KAFKA-3816) Provide more context in Kafka Connect log messages

[ https://issues.apache.org/jira/browse/KAFKA-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323684#comment-15323684 ] Randall Hauch commented on KAFKA-3816: -- {quote} One thing we might want to do in conjunction with

[jira] [Commented] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323675#comment-15323675 ] Jun Rao commented on KAFKA-3693: [~maysamyabandeh], the controller detects broker failure through ZK

[jira] [Commented] (KAFKA-3816) Provide more context in Kafka Connect log messages

[ https://issues.apache.org/jira/browse/KAFKA-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323651#comment-15323651 ] Ewen Cheslack-Postava commented on KAFKA-3816: -- This would be awesome, and I'm hoping this

[jira] [Commented] (KAFKA-3821) Allow Kafka Connect source tasks to produce offset without writing to topics

[ https://issues.apache.org/jira/browse/KAFKA-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323648#comment-15323648 ] Ewen Cheslack-Postava commented on KAFKA-3821: -- I was thinking about this a bit more, along

[jira] [Commented] (KAFKA-3811) Introduce Kafka Streams metrics recording levels

[ https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323616#comment-15323616 ] Guozhang Wang commented on KAFKA-3811: -- Yeah I think they are related. Feel free to re-assign to

[jira] [Assigned] (KAFKA-3820) Provide utilities for tracking source offsets

[ https://issues.apache.org/jira/browse/KAFKA-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reassigned KAFKA-3820: - Assignee: Liquan Pei (was: Ewen Cheslack-Postava) > Provide utilities for tracking source

[jira] [Commented] (KAFKA-3234) Minor documentation edits: clarify minISR; some topic-level configs are missing

[ https://issues.apache.org/jira/browse/KAFKA-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323554#comment-15323554 ] James Cheng commented on KAFKA-3234: Hi, what's the status on this JIRA? I didn't realize that this

[jira] [Commented] (KAFKA-3801) Provide static serialize() and deserialize() for use as method references

[ https://issues.apache.org/jira/browse/KAFKA-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323561#comment-15323561 ] Guozhang Wang commented on KAFKA-3801: -- Hello [~jeff.klu...@gmail.com] could you present a concrete

[jira] [Commented] (KAFKA-3809) Auto-generate documentation for topic-level configuration

[ https://issues.apache.org/jira/browse/KAFKA-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323557#comment-15323557 ] Ismael Juma commented on KAFKA-3809: I think there is benefit in doing it in two parts as the

[jira] [Commented] (KAFKA-3817) KTableRepartitionMap should handle null inputs

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

[GitHub] kafka pull request #1488: KAFKA-3817: handle null keys in KTableRepartitionM...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1488 KAFKA-3817: handle null keys in KTableRepartitionMap You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka

[jira] [Commented] (KAFKA-3806) Adjust default values of log.retention.hours and offsets.retention.minutes

[ https://issues.apache.org/jira/browse/KAFKA-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323527#comment-15323527 ] James Cheng commented on KAFKA-3806: One impact, which I don't know if it's a large issue, is that the

[jira] [Commented] (KAFKA-3806) Adjust default values of log.retention.hours and offsets.retention.minutes

[ https://issues.apache.org/jira/browse/KAFKA-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323521#comment-15323521 ] Jun Rao commented on KAFKA-3806: [~dwatzke], I think the original intention is that consumers in Kafka are

[jira] [Assigned] (KAFKA-3818) Change Mirror Maker default assignment strategy to round robin

[ https://issues.apache.org/jira/browse/KAFKA-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-3818: -- Assignee: Vahid Hashemian > Change Mirror Maker default assignment strategy to round

Question on Kafka Consumer

Hello All, I am working on building an application on cloud and below are the high level requirements. - Ingest data into Kafka with say 100 partitions (Incoming rate - 100,000 msgs/sec) - Read data from Kafka and process each data (Do some computation, compare with old data, find location etc)

[jira] [Commented] (KAFKA-3821) Allow Kafka Connect source tasks to produce offset without writing to topics

[ https://issues.apache.org/jira/browse/KAFKA-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323429#comment-15323429 ] Randall Hauch commented on KAFKA-3821: -- Source tasks produce records by returning them from their

[jira] [Created] (KAFKA-3821) Allow Kafka Connect source tasks to produce offset without writing to topics

Randall Hauch created KAFKA-3821: Summary: Allow Kafka Connect source tasks to produce offset without writing to topics Key: KAFKA-3821 URL: https://issues.apache.org/jira/browse/KAFKA-3821 Project:

[jira] [Resolved] (KAFKA-3814) Connectors should be able to know their name

[ https://issues.apache.org/jira/browse/KAFKA-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-3814. -- Resolution: Invalid Apologies. There is a {{name}} property. Not sure what I was thinking. >

[jira] [Commented] (KAFKA-3814) Connectors should be able to know their name

[ https://issues.apache.org/jira/browse/KAFKA-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323385#comment-15323385 ] Ewen Cheslack-Postava commented on KAFKA-3814: -- [~rhauch] Is this true? I would think you

[jira] [Commented] (KAFKA-3811) Introduce Kafka Streams metrics recording levels

[ https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323347#comment-15323347 ] aarti gupta commented on KAFKA-3811: Wondering how this relates to

[jira] [Created] (KAFKA-3820) Provide utilities for tracking source offsets

Ewen Cheslack-Postava created KAFKA-3820: Summary: Provide utilities for tracking source offsets Key: KAFKA-3820 URL: https://issues.apache.org/jira/browse/KAFKA-3820 Project: Kafka

[jira] [Commented] (KAFKA-3753) Add size() to the StateStore interface for metrics reporting

[ https://issues.apache.org/jira/browse/KAFKA-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323342#comment-15323342 ] Jeff Klukas commented on KAFKA-3753: I agree that {{size}} is a bit ambiguous. I'd expect many folks

[jira] [Created] (KAFKA-3819) Provide utilities for polling source connectors

Ewen Cheslack-Postava created KAFKA-3819: Summary: Provide utilities for polling source connectors Key: KAFKA-3819 URL: https://issues.apache.org/jira/browse/KAFKA-3819 Project: Kafka

[jira] [Updated] (KAFKA-3819) Provide utilities for polling source connectors

[ https://issues.apache.org/jira/browse/KAFKA-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3819: - Issue Type: New Feature (was: Bug) > Provide utilities for polling source

[jira] [Created] (KAFKA-3818) Change Mirror Maker default assignment strategy to round robin

Jason Gustafson created KAFKA-3818: -- Summary: Change Mirror Maker default assignment strategy to round robin Key: KAFKA-3818 URL: https://issues.apache.org/jira/browse/KAFKA-3818 Project: Kafka

[jira] [Commented] (KAFKA-3753) Add size() to the StateStore interface for metrics reporting

[ https://issues.apache.org/jira/browse/KAFKA-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323324#comment-15323324 ] Jay Kreps commented on KAFKA-3753: -- I think size is a bit ambiguous, it could mean the number of bytes

[jira] [Created] (KAFKA-3817) KTableRepartitionMap should handle null inputs

Jeff Klukas created KAFKA-3817: -- Summary: KTableRepartitionMap should handle null inputs Key: KAFKA-3817 URL: https://issues.apache.org/jira/browse/KAFKA-3817 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-3802) log mtimes reset on broker restart

[ https://issues.apache.org/jira/browse/KAFKA-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3802: --- Fix Version/s: 0.10.0.1 > log mtimes reset on broker restart > -- > >

[jira] [Commented] (KAFKA-2082) Kafka Replication ends up in a bad state

[ https://issues.apache.org/jira/browse/KAFKA-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323299#comment-15323299 ] Evan Huus commented on KAFKA-2082: -- This issue has been "In Progress" since April 2015, any actual

Re: [VOTE] KIP-55: Secure quotas for authenticated users

Super sorry to come in late on this one. Rajini, I had two quick questions I think we should be able to answer: 1. Do client ids make sense in a world which has users? If not should we unify them the way Hadoop did (without auth the user is a kind of best effort honor system identity).

[jira] [Commented] (KAFKA-3816) Provide more context in Kafka Connect log messages

[ https://issues.apache.org/jira/browse/KAFKA-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323179#comment-15323179 ] Randall Hauch commented on KAFKA-3816: -- One example of a set of 3 parameters would work for

[jira] [Created] (KAFKA-3815) Support command line arguments in Kafka Connect distribute worker

Randall Hauch created KAFKA-3815: Summary: Support command line arguments in Kafka Connect distribute worker Key: KAFKA-3815 URL: https://issues.apache.org/jira/browse/KAFKA-3815 Project: Kafka

[jira] [Updated] (KAFKA-3753) Add size() to the StateStore interface for metrics reporting

[ https://issues.apache.org/jira/browse/KAFKA-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3753: - Summary: Add size() to the StateStore interface for metrics reporting (was: Metrics for

[jira] [Created] (KAFKA-3814) Connectors should be able to know their name

Randall Hauch created KAFKA-3814: Summary: Connectors should be able to know their name Key: KAFKA-3814 URL: https://issues.apache.org/jira/browse/KAFKA-3814 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3813) Let SourceConnector implementations access the offset reader

[ https://issues.apache.org/jira/browse/KAFKA-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323112#comment-15323112 ] Randall Hauch commented on KAFKA-3813: -- The current API defines {{ConnectorContext}} interface and

[jira] [Created] (KAFKA-3813) Let SourceConnector implementations access the offset reader

Randall Hauch created KAFKA-3813: Summary: Let SourceConnector implementations access the offset reader Key: KAFKA-3813 URL: https://issues.apache.org/jira/browse/KAFKA-3813 Project: Kafka

[jira] [Commented] (KAFKA-3805) Running multiple instances of a Streams app on the same machine results in Java_org_rocksdb_RocksDB_write error

[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323070#comment-15323070 ] Andres Gomez Ferrer commented on KAFKA-3805: ok, thanks!! > Running multiple instances of a

[jira] [Commented] (KAFKA-3805) Running multiple instances of a Streams app on the same machine results in Java_org_rocksdb_RocksDB_write error

[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323059#comment-15323059 ] Eno Thereska commented on KAFKA-3805: - [~agomez] I created another JIRA for the case when one uses the

[jira] [Created] (KAFKA-3812) State store locking is incorrect

Eno Thereska created KAFKA-3812: --- Summary: State store locking is incorrect Key: KAFKA-3812 URL: https://issues.apache.org/jira/browse/KAFKA-3812 Project: Kafka Issue Type: Bug

Re: [VOTE] KIP-55: Secure quotas for authenticated users

+1 (non-binding) On Wed, Jun 8, 2016 at 8:56 PM, Rajini Sivaram wrote: > I would like to initiate the vote for KIP-55. > > The KIP details are here: KIP-55: Secure quotas for authenticated users > < >

[jira] [Work started] (KAFKA-3805) Running multiple instances of a Streams app on the same machine results in Java_org_rocksdb_RocksDB_write error

[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3805 started by Eno Thereska. --- > Running multiple instances of a Streams app on the same machine results in >

Re: [DISCUSS] scalability limits in the coordinator

I think the value of adding a "offsets.replica.fetch.max.bytes" config is that we don't break/change the meaning of "replica.fetch.max.bytes". We can also set "offsets.replica.fetch.max.bytes" to be a value safely larger than what we expect to ever allow the __consumer_offsets topic max message

[jira] [Created] (KAFKA-3811) Introduce KStream metrics recording levels

Greg Fodor created KAFKA-3811: - Summary: Introduce KStream metrics recording levels Key: KAFKA-3811 URL: https://issues.apache.org/jira/browse/KAFKA-3811 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-3811) Introduce Kafka Streams metrics recording levels

[ https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Fodor updated KAFKA-3811: -- Summary: Introduce Kafka Streams metrics recording levels (was: Introduce KStream metrics recording

Re: [DISCUSS] scalability limits in the coordinator

I think taking bigger one of the fetch size and message size limit is probably good enough. If we have a separate "offset.replica.fetch.max.bytes", I guess the value will always be set to max message size of the __consumer_offsets topic, which does not seem to have much value. On Thu, Jun 9, 2016

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

Jun & Ismael, Unfortunately I couldn't attend the KIP meeting when delegation tokens discussed. Appreciate if you can update the thread if you have any further questions. Thanks, Harsha On Tue, May

[jira] [Commented] (KAFKA-3805) Running multiple instances of a Streams app on the same machine results in Java_org_rocksdb_RocksDB_write error

[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322738#comment-15322738 ] Andres Gomez Ferrer commented on KAFKA-3805: Hey [~enothereska] the PR works fine! Thanks :)

[jira] [Commented] (KAFKA-3753) Metrics for StateStores

[ https://issues.apache.org/jira/browse/KAFKA-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322683#comment-15322683 ] Jeff Klukas commented on KAFKA-3753: Since there's refactoring going on right now with the metrics

[GitHub] kafka pull request #1487: kafka-run-class.sh now runs under Cygwin.

GitHub user deragon opened a pull request: https://github.com/apache/kafka/pull/1487 kafka-run-class.sh now runs under Cygwin. kafka-run-class.sh now runs under Cygwin; paths and classpath are set up properly. **WARNING:** The script was not tested on a Linux machine,

[jira] [Commented] (KAFKA-3753) Metrics for StateStores

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

[GitHub] kafka pull request #1486: KAFKA-3753: Add size() method to KeyValueStore int...

GitHub user jklukas opened a pull request: https://github.com/apache/kafka/pull/1486 KAFKA-3753: Add size() method to KeyValueStore interface See https://issues.apache.org/jira/browse/KAFKA-3753 This contribution is my original work and I license the work to the project

[jira] [Commented] (KAFKA-3805) Running multiple instances of a Streams app on the same machine results in Java_org_rocksdb_RocksDB_write error

[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322641#comment-15322641 ] Eno Thereska commented on KAFKA-3805: - Thanks [~agomez]. If you get a chance, could you please try the

[jira] [Commented] (KAFKA-3805) Running multiple instances of a Streams app on the same machine results in Java_org_rocksdb_RocksDB_write error

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

[GitHub] kafka pull request #1485: KAFKA-3805: Check if DB is null. Do not release lo...

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/1485 KAFKA-3805: Check if DB is null. Do not release locked resources You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka

[jira] [Comment Edited] (KAFKA-3805) Running multiple instances of a Streams app on the same machine results in Java_org_rocksdb_RocksDB_write error

[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322302#comment-15322302 ] Andres Gomez Ferrer edited comment on KAFKA-3805 at 6/9/16 11:48 AM: -

[jira] [Comment Edited] (KAFKA-3805) Running multiple instances of a Streams app on the same machine results in Java_org_rocksdb_RocksDB_write error

[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322302#comment-15322302 ] Andres Gomez Ferrer edited comment on KAFKA-3805 at 6/9/16 10:18 AM: -

[jira] [Commented] (KAFKA-3805) Running multiple instances of a Streams app on the same machine results in Java_org_rocksdb_RocksDB_write error

[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322302#comment-15322302 ] Andres Gomez Ferrer commented on KAFKA-3805: [~enothereska] Yes sure, I attached the Kafka

Re: [DISCUSS] scalability limits in the coordinator

Maybe another approach can be to add a new "offsets.replica.fetch.max.bytes" config on the brokers. On Thu, Jun 9, 2016 at 3:03 AM, Onur Karaman wrote: > I made a PR with a tweak to Jun's/Becket's proposal: > https://github.com/apache/kafka/pull/1484 > > It just tweaks

[jira] [Updated] (KAFKA-3805) Running multiple instances of a Streams app on the same machine results in Java_org_rocksdb_RocksDB_write error

[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres Gomez Ferrer updated KAFKA-3805: --- Attachment: kafka-streams-testing.zip > Running multiple instances of a Streams app

Re: [DISCUSS] scalability limits in the coordinator

I made a PR with a tweak to Jun's/Becket's proposal: https://github.com/apache/kafka/pull/1484 It just tweaks the fetch behavior specifically for replicas fetching from the __consumer_offsets topic when the fetcher's "replica.fetch.max.bytes" is less than the __consumer_offset leader's

[jira] [Commented] (KAFKA-3810) replication of internal topics should not be limited by replica.fetch.max.bytes

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

[GitHub] kafka pull request #1484: KAFKA-3810: replication of internal topics should ...

GitHub user onurkaraman opened a pull request: https://github.com/apache/kafka/pull/1484 KAFKA-3810: replication of internal topics should not be limited by replica.fetch.max.bytes From the kafka-dev mailing list discussion: [DISCUSS] scalability limits in the coordinator

[jira] [Commented] (KAFKA-3805) Running multiple instances of a Streams app on the same machine results in Java_org_rocksdb_RocksDB_write error

[ https://issues.apache.org/jira/browse/KAFKA-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322261#comment-15322261 ] Eno Thereska commented on KAFKA-3805: - [~agomez] I cannot reproduce problem when using two different

[jira] [Commented] (KAFKA-3775) Throttle maximum number of tasks assigned to a single KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322254#comment-15322254 ] Matthias J. Sax commented on KAFKA-3775: I want to push this discussion further. As [~guozhang]

[jira] [Created] (KAFKA-3810) replication of internal topics should not be limited by replica.fetch.max.bytes

Onur Karaman created KAFKA-3810: --- Summary: replication of internal topics should not be limited by replica.fetch.max.bytes Key: KAFKA-3810 URL: https://issues.apache.org/jira/browse/KAFKA-3810 Project:

[jira] [Updated] (KAFKA-3799) Turn on endpoint validation in SSL system tests

[ https://issues.apache.org/jira/browse/KAFKA-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3799: -- Affects Version/s: 0.10.0.0 Status: Patch Available (was: Open) > Turn on

[jira] [Updated] (KAFKA-3562) Null Pointer Exception Found when delete topic and Using New Producer

[ https://issues.apache.org/jira/browse/KAFKA-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3562: -- Status: Patch Available (was: Open) > Null Pointer Exception Found when delete topic and Using

[jira] [Resolved] (KAFKA-3788) Potential message lost when switching to new segment

[ https://issues.apache.org/jira/browse/KAFKA-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arkadiusz Firus resolved KAFKA-3788. Resolution: Not A Problem > Potential message lost when switching to new segment >

[jira] [Commented] (KAFKA-3788) Potential message lost when switching to new segment

[ https://issues.apache.org/jira/browse/KAFKA-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322105#comment-15322105 ] Arkadiusz Firus commented on KAFKA-3788: Thank you very much for the explanation. I should have

[jira] [Commented] (KAFKA-3806) Adjust default values of log.retention.hours and offsets.retention.minutes

[ https://issues.apache.org/jira/browse/KAFKA-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322097#comment-15322097 ] Michal Turek commented on KAFKA-3806: - Hi Jun and James, I probably don't see all the assumptions and

[jira] [Commented] (KAFKA-3806) Adjust default values of log.retention.hours and offsets.retention.minutes

[ https://issues.apache.org/jira/browse/KAFKA-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15322076#comment-15322076 ] David Watzke commented on KAFKA-3806: - [~junrao] I understand the need for the automatic consumer

[jira] [Commented] (KAFKA-3799) Turn on endpoint validation in SSL system tests

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

[GitHub] kafka pull request #1483: KAFKA-3799: Enable SSL endpoint validation in syst...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/1483 KAFKA-3799: Enable SSL endpoint validation in system tests Generate certificates with hostname in SubjectAlternativeName and enable hostname validation. You can merge this pull request into

[GitHub] kafka pull request #1482: MINOR: Fix a variable name semantically correct.

GitHub user uchan-nos opened a pull request: https://github.com/apache/kafka/pull/1482 MINOR: Fix a variable name semantically correct. Hi all, This is my first commit to Kafka. "msec / 1000" turns into sec, isn't it? I just have fixed a variable name. @granders