Re: [VOTE] 0.10.2.1 RC1

+1 (non-binding) Built sources, ran all unit and integration tests, checked new documentation, esp with an eye on the streams library. Thanks Gwen Eno > On 12 Apr 2017, at 17:25, Gwen Shapira wrote: > > Hello Kafka users, developers, client-developers, friends, romans, >

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968209#comment-15968209 ] Jun Rao commented on KAFKA-5062: One far fetched scenario is the following. A bad application sent the

[DISCUSS] ACL operations

Hi all, KIP-4 described some RPCs for implementing centralized administrative operations for Kafka. Now that the adminclient work is going forward, I'd like to re-open the discussion about the ACL-related RPCs. This is a continuation of the email thread Grant Henke started while back. (See

[jira] [Commented] (KAFKA-4346) Add foreachValue method to KStream

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

[GitHub] kafka pull request #2063: KAFKA-4346: Add foreachValue method to KStream

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

[GitHub] kafka pull request #2849: KAFKA-5059: Implement Transactional Coordinator

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2849 KAFKA-5059: Implement Transactional Coordinator You can merge this pull request into a Git repository by running: $ git pull https://github.com/confluentinc/kafka exactly-once-tc Alternatively

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967368#comment-15967368 ] Ismael Juma commented on KAFKA-5062: [~rsivaram], yes, it was on PLAINTEXT. The weird thing is that

Re: Invoking KafkaConsumer#seek for the same partition

Sounds to me the comment is imprecisely phrased but was meant to indicate the behaviour you are describing. Perhaps instead of "the latest offset", it should say, "the offset used in the latest seek" to make it super-clear. Cheers, Michal On 13/04/17 08:28, Hu Xi wrote: Hi guys, The

答复: Invoking KafkaConsumer#seek for the same partition

Oh My! yes, you are right. I would have been thinking it that way Thank you. 发件人: Michal Borowiecki 发送时间: 2017年4月13日 17:02 收件人: dev@kafka.apache.org 主题: Re: Invoking KafkaConsumer#seek for the same partition Sounds to me the

[jira] [Created] (KAFKA-5064) Kafka service crashes with SIGSEGV

Jothikanth created KAFKA-5064: - Summary: Kafka service crashes with SIGSEGV Key: KAFKA-5064 URL: https://issues.apache.org/jira/browse/KAFKA-5064 Project: Kafka Issue Type: Bug

Re: 答复: Invoking KafkaConsumer#seek for the same partition

But I totally agree, the comment is ambiguous. The way it's phrased now "latest offset" can easily be taken for "the highest(=latest) of the offsets" rather than "the offset last-used". Cheers, Michal On 13/04/17 10:07, Hu Xi wrote: Oh My! yes, you are right. I would have been thinking it

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967357#comment-15967357 ] Rajini Sivaram commented on KAFKA-5062: --- [~apurva] Is this on a PLAINTEXT port? Also, do you have

Invoking KafkaConsumer#seek for the same partition

Hi guys, The comments for KafkaConsumer#seek says “If this API is invoked for the same partition more than once, the latest offset will be used on the next poll()”. However, I tried a couple of times, and it turned out that the next poll could always read records from the offset which was

[jira] [Commented] (KAFKA-5059) Implement Transactional Coordinator

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

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968257#comment-15968257 ] James Cheng commented on KAFKA-5062: I agree with Jun about how to try to reproduce it. According to

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968268#comment-15968268 ] James Cheng commented on KAFKA-5062: Ah, gotcha. I missed that part. > Kafka brokers can accept

Re: Kafka-Streams: Cogroup

Hi Kyle, (cc-ing user list as well) This could be an interesting scenario. Two things to help us think through it some more: 1) it seems you attached a figure, but I cannot seem to open it. 2) what about using the low level processor API instead of the DSL as approach 3? Do you have any

Re: [DISCUSS] ACL operations

Based on the initial discussion here, and the draft KIP-133, it sounds like the plan is to have AdminClient APIs like: addAcls, removeAcls, listAcls, listConfig, changeConfig (roughly speaking). However, just to play devil's advocate here a bit, wouldn't AdminClient users find it more natural to

[jira] [Created] (KAFKA-5069) add controller integration tests

Onur Karaman created KAFKA-5069: --- Summary: add controller integration tests Key: KAFKA-5069 URL: https://issues.apache.org/jira/browse/KAFKA-5069 Project: Kafka Issue Type: Sub-task

[GitHub] kafka pull request #2851: MINOR: Clarify wording

GitHub user jeffwidman opened a pull request: https://github.com/apache/kafka/pull/2851 MINOR: Clarify wording You can merge this pull request into a Git repository by running: $ git pull https://github.com/jeffwidman/kafka patch-3 Alternatively you can review and apply

[GitHub] kafka pull request #2852: MINOR: Fix some re-raising of exceptions in system...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/2852 MINOR: Fix some re-raising of exceptions in system tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka minor-re-raise-exceptions

Re: [DISCUSS] ACL operations

Hi Colin, Thanks for coordinating with Grant and reviving this. I agree that having a separate delete request makes sense. This also came up in the original discussion thread and I think people were in favour. Ismael On 13 Apr 2017 10:21 pm, "Colin McCabe" wrote: > Hi all,

[jira] [Comment Edited] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968265#comment-15968265 ] Ismael Juma edited comment on KAFKA-5062 at 4/13/17 9:48 PM: - James, as stated

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968265#comment-15968265 ] Ismael Juma commented on KAFKA-5062: James, as stated previously, we check if the size is above the

[GitHub] kafka pull request #2853: KAFKA-5069: add controller integration tests

GitHub user onurkaraman opened a pull request: https://github.com/apache/kafka/pull/2853 KAFKA-5069: add controller integration tests Test the various controller protocols by observing zookeeper and broker state. You can merge this pull request into a Git repository by running:

Kafka-Streams: Cogroup

Hello, I am wondering if there is any way to aggregate together many streams at once to build a larger object. Example (Healthcare Domain): I have streams of Medical, Pharmacy, and Lab claims. Key is PatientId, Value is a different Avro Record for each stream. I was hoping there was a way to

[jira] [Commented] (KAFKA-5028) convert kafka controller to a single-threaded event queue model

[ https://issues.apache.org/jira/browse/KAFKA-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967653#comment-15967653 ] Balint Molnar commented on KAFKA-5028: -- [~onurkaraman] I am so exited about this. Is there anything I

[jira] [Created] (KAFKA-5066) KafkaMetricsConfig properties and description notably missing from documentation

Ryan P created KAFKA-5066: - Summary: KafkaMetricsConfig properties and description notably missing from documentation Key: KAFKA-5066 URL: https://issues.apache.org/jira/browse/KAFKA-5066 Project: Kafka

Re: [DISCUSS] KIP-138: Change punctuate semantics

Hi, I would like to push this discussion further. Thanks Michael for your email (it was longer than expected, even after your "sorry for the long email" warning... :P). But I'll go ahead an follow your example: it's a long read. :) I think it's really important to put all this in a larger scope

[jira] [Commented] (KAFKA-5049) Chroot check should be done for each ZkUtils instance

[ https://issues.apache.org/jira/browse/KAFKA-5049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968624#comment-15968624 ] Umesh Chaudhary commented on KAFKA-5049: Thanks [~junrao] for the pointers. While I was looking at

Re: [DISCUSS] KIP 130: Expose states of active tasks to KafkaStreams public API

Florian, >>> What about KafkaStreams#toString() method? >>> >>> I think, we want to deprecate it as with KIP-120 and the changes of this >>> KIP, is gets obsolete. Any thoughts about this? For me, this is the last open point to discuss (or what should be reflected in the KIP in case you agree)

[jira] [Commented] (KAFKA-5069) add controller integration tests

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

[jira] [Work started] (KAFKA-5069) add controller integration tests

[ https://issues.apache.org/jira/browse/KAFKA-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5069 started by Onur Karaman. --- > add controller integration tests > > >

[jira] [Updated] (KAFKA-5005) JoinIntegrationTest.testLeftKStreamKStream() fails occasionally

[ https://issues.apache.org/jira/browse/KAFKA-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5005: --- Description: testLeftKStreamKStream: {noformat} java.lang.AssertionError: Condition not met

[jira] [Updated] (KAFKA-5005) JoinIntegrationTest fails occasionally

[ https://issues.apache.org/jira/browse/KAFKA-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5005: --- Summary: JoinIntegrationTest fails occasionally (was:

[jira] [Commented] (KAFKA-5057) "Big Message Log"

[ https://issues.apache.org/jira/browse/KAFKA-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968580#comment-15968580 ] Umesh Chaudhary commented on KAFKA-5057: Understood and yes this is a good idea to capture the

[jira] [Commented] (KAFKA-5065) AbstractCoordinator.ensureCoordinatorReady() stuck in loop if absent any bootstrap servers

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

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967479#comment-15967479 ] Ismael Juma commented on KAFKA-5062: Kafka version was 0.10.1.1, so I don't think BlockingChannel was

[jira] [Created] (KAFKA-5065) AbstractCoordinator.ensureCoordinatorReady() stuck in loop if absent any bootstrap servers

Vladimir Porshkevich created KAFKA-5065: --- Summary: AbstractCoordinator.ensureCoordinatorReady() stuck in loop if absent any bootstrap servers Key: KAFKA-5065 URL:

[GitHub] kafka pull request #2850: KAFKA-5065; AbstractCoordinator.ensureCoordinatorR...

GitHub user porshkevich opened a pull request: https://github.com/apache/kafka/pull/2850 KAFKA-5065; AbstractCoordinator.ensureCoordinatorReady() stuck in loop if absent any bootstrap servers add a consumer config: "max.block.ms" default to 6 ms; when specified, the

[jira] [Commented] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967450#comment-15967450 ] Rajini Sivaram commented on KAFKA-5062: --- [~ijuma] Was it an application writing bad data - not a

[GitHub] kafka pull request #2237: support scala 2.12 build

Github user pjfanning closed the pull request at: https://github.com/apache/kafka/pull/2237 --- 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] [Comment Edited] (KAFKA-5062) Kafka brokers can accept malformed requests which allocate gigabytes of memory

[ https://issues.apache.org/jira/browse/KAFKA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967450#comment-15967450 ] Rajini Sivaram edited comment on KAFKA-5062 at 4/13/17 11:37 AM: - [~ijuma]

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967705#comment-15967705 ] Jun Rao commented on KAFKA-2729: Thanks for the additional info. In both [~Ronghua Lin] and

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967735#comment-15967735 ] Edoardo Comar commented on KAFKA-2729: -- FWIW - we saw the same message {{ Cached zkVersion [66] not

[jira] [Created] (KAFKA-5067) java.sql.SQLDataException on TimeStamp column when using AWS Redshift as a JDBC source

Curtis Wilde created KAFKA-5067: --- Summary: java.sql.SQLDataException on TimeStamp column when using AWS Redshift as a JDBC source Key: KAFKA-5067 URL: https://issues.apache.org/jira/browse/KAFKA-5067

[jira] [Updated] (KAFKA-5067) java.sql.SQLDataException on TimeStamp column when using AWS Redshift as a JDBC source

[ https://issues.apache.org/jira/browse/KAFKA-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Curtis Wilde updated KAFKA-5067: Description: Kafka Connect throws java.sql.SQLDataException when attempting to use Redshift as a

[jira] [Commented] (KAFKA-5037) Infinite loop if all input topics are unknown at startup

[ https://issues.apache.org/jira/browse/KAFKA-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967817#comment-15967817 ] Matthias J. Sax commented on KAFKA-5037: A similar issue got reported here:

[jira] [Commented] (KAFKA-5057) "Big Message Log"

[ https://issues.apache.org/jira/browse/KAFKA-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967819#comment-15967819 ] Gwen Shapira commented on KAFKA-5057: - I thought of a new configuration (which made me realize this

[jira] [Resolved] (KAFKA-5001) RocksDBSessionStoreSupplierTest#shouldNotBeLoggingEnabledStoreWhenLoggingNotEnabled

[ https://issues.apache.org/jira/browse/KAFKA-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-5001. Resolution: Duplicate >

[jira] [Created] (KAFKA-5068) Optionally print out metrics after running the perf tests

Jun Rao created KAFKA-5068: -- Summary: Optionally print out metrics after running the perf tests Key: KAFKA-5068 URL: https://issues.apache.org/jira/browse/KAFKA-5068 Project: Kafka Issue Type: