[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803893#comment-15803893 ] Michael Andre Pearce (IG) commented on KAFKA-4497: -- we are going to md5 checksum check

[jira] [Updated] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4595: --- Priority: Critical (was: Major) > Controller send thread can't stop when broker change listener

[jira] [Updated] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4595: --- Labels: reliability (was: ) > Controller send thread can't stop when broker change listener event

[jira] [Issue Comment Deleted] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Andre Pearce (IG) updated KAFKA-4497: - Comment: was deleted (was: [~junrao] We are 99.9% jars are good, see

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803829#comment-15803829 ] Michael Andre Pearce (IG) commented on KAFKA-4497: -- [~junrao] We are 99.9% jars are good,

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803830#comment-15803830 ] Michael Andre Pearce (IG) commented on KAFKA-4497: -- [~junrao] We are 99.9% jars are good,

[jira] [Commented] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803816#comment-15803816 ] Pengwei commented on KAFKA-4595: [~huxi_2b] > Controller send thread can't stop when broker change

[jira] [Commented] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803812#comment-15803812 ] Pengwei commented on KAFKA-4595: Yes, you are right. > Controller send thread can't stop when broker

[jira] [Commented] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803804#comment-15803804 ] huxi commented on KAFKA-4595: - Yes, seems that the process might look like this: 1. At some point of time,

Re: Wiki permissions

Thanks Wang, I completed to submit my KIP because of you. Regards, Dongjin On Fri, Jan 6, 2017 at 2:52 AM, Guozhang Wang wrote: > Dongjin > > I have granted you the permission under apache id dongjin > > > Guozhang > > > On Wed, Jan 4, 2017 at 11:51 PM, Dongjin Lee

Re: [DISCUSS] KIP-109: Old Consumer Deprecation

One thing that probably needs some clarification is what is implied by "deprecated" in the Kafka project. I googled it a bit and it doesn't seem that deprecation conventionally implies termination of support (or anything that could negatively impact existing users). That's my interpretation

[jira] [Commented] (KAFKA-4603) argument error,and command parsed error

[ https://issues.apache.org/jira/browse/KAFKA-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803365#comment-15803365 ] Xin commented on KAFKA-4603: In Kafka, all the OptionParser constructor has no allowAbbreviations argument

[jira] [Commented] (KAFKA-4603) argument error,and command parsed error

[ https://issues.apache.org/jira/browse/KAFKA-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803353#comment-15803353 ] Xin commented on KAFKA-4603: Changed OptionParser constructor, ZkSecurityMigrator.scala: var jaasFile =

[jira] [Commented] (KAFKA-4400) Prefix for sink task consumer groups should be configurable

[ https://issues.apache.org/jira/browse/KAFKA-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803350#comment-15803350 ] Ewen Cheslack-Postava commented on KAFKA-4400: -- [~skyahead] Did you see the comments on the

[jira] [Commented] (KAFKA-4603) argument error,and command parsed error

[ https://issues.apache.org/jira/browse/KAFKA-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803345#comment-15803345 ] Xin commented on KAFKA-4603: I think that new OptionParser() not suitable for kafka command in kafka has

[jira] [Created] (KAFKA-4603) argument error,and command parsed error

Xin created KAFKA-4603: -- Summary: argument error,and command parsed error Key: KAFKA-4603 URL: https://issues.apache.org/jira/browse/KAFKA-4603 Project: Kafka Issue Type: Bug Components:

Re: [DISCUSS] KIP-109: Old Consumer Deprecation

While I realize this only marks the old consumer as deprecated and not a complete removal, I agree that it is somewhat premature to do this prior to having a migration process implemented. Onur has described this in detail in the earlier thread: http://markmail.org/message/ekv352zy7xttco5s and I'm

[jira] [Commented] (KAFKA-4599) KafkaConsumer encounters SchemaException when Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803315#comment-15803315 ] huxi commented on KAFKA-4599: - What kind of Storm-supplied kafka client do you use? storm-kafka or

Re: [VOTE] KIP-102 - Add close with timeout for consumers

Hey Gwen, I'm not super strong on this, but I think the case for a longer timeout as the default behavior is weaker for the consumer. For the producer, it means we might lose messages that the application tried to send. For the consumer, it means we might lose offset commits, which means

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

Hi all, I've just posted a new KIP "KIP-110: Add Codec for ZStandard Compression" for discussion: https://cwiki.apache.org/confluence/display/KAFKA/KIP-110%3A+Add+Codec+for+ZStandard+Compression Please have a look when you are free. Best, Dongjin -- *Dongjin Lee* *Software developer in

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

(adding the dev list back - as it seems to have gotten dropped earlier in this thread) On Thu, Jan 5, 2017 at 6:36 PM, Joel Koshy wrote: > +1 > > This is a very well-written KIP! > Minor: there is still a mix of terms in the doc that references the > earlier

Re: [VOTE] KIP-88: OffsetFetch Protocol Update

+1 On Thu, Jan 5, 2017 at 1:30 PM, Ismael Juma wrote: > Thanks for the updates, +1 > > Ismael > > On Thu, Jan 5, 2017 at 6:14 PM, Vahid S Hashemian < > vahidhashem...@us.ibm.com > > wrote: > > > I'd like to start another round of voting on KIP-88 after recent changes > > to

Re: [VOTE] KIP-102 - Add close with timeout for consumers

For 0.10.2.0, this can absolutely make it in if we get the reviews done quickly enough. The cutoff for getting a new feature in would be the feature freeze on Jan 13 (when we generate the release branch and start having to cherry-pick commits, so we want to limit to stabilization and important bug

Re: [VOTE] KIP-102 - Add close with timeout for consumers

+1 On Thu, Jan 5, 2017 at 6:30 PM, Ewen Cheslack-Postava wrote: > +1 > > -Ewen > > On Thu, Jan 5, 2017 at 5:48 PM, Neha Narkhede wrote: > > > +1 (binding) > > > > On Thu, Jan 5, 2017 at 2:07 PM Rajini Sivaram > > wrote: > > > > >

Re: [VOTE] KIP-102 - Add close with timeout for consumers

+1 -Ewen On Thu, Jan 5, 2017 at 5:48 PM, Neha Narkhede wrote: > +1 (binding) > > On Thu, Jan 5, 2017 at 2:07 PM Rajini Sivaram > wrote: > > > Hi all, > > > > > > I would like to start the voting process for *KIP-102 - Add close with > > timeout for

Re: [VOTE] KIP-72 - Allow putting a bound on memory consumed by Incoming requests

Hi, Radai, The new metrics look good. +1 on the KIP. Thanks, Jun On Fri, Dec 16, 2016 at 4:46 PM, radai wrote: > I've added the 3 new metrics/sensors i've implemented to the KIP. > > at this point I would need to re-validate the functionality (which i expect > to

Re: [VOTE] KIP-102 - Add close with timeout for consumers

+1 (binding) On Thu, Jan 5, 2017 at 2:07 PM Rajini Sivaram wrote: > Hi all, > > > I would like to start the voting process for *KIP-102 - Add close with > timeout for consumers*: > > > >

Re: [VOTE] KIP-66: Single Message Transforms for Kafka Connect

+1 (binding) On Wed, Jan 4, 2017 at 2:36 PM Shikhar Bhushan wrote: > I do plan on introducing a new `connect:transforms` module (which > `connect:runtime` will depend on), so they will live in a separate module > in the source tree and output. > > (

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803184#comment-15803184 ] Jun Rao commented on KAFKA-4497: [~michael.andre.pearce], I did the following test. (1) Run Kafka 0.10.1.1

[jira] [Commented] (KAFKA-1817) AdminUtils.createTopic vs kafka-topics.sh --create with partitions

[ https://issues.apache.org/jira/browse/KAFKA-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803174#comment-15803174 ] Jeff Widman commented on KAFKA-1817: So can this be closed? > AdminUtils.createTopic vs

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

See Changes: [me] KAFKA-4575: ensure topic created before starting sink for -- [...truncated 7963 lines...] kafka.integration.SaslPlaintextTopicMetadataTest >

[GitHub] kafka pull request #2321: MINOR: update JavaDoc for simple helper interfaces...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2321 MINOR: update JavaDoc for simple helper interfaces of KStream and KTable operators You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka

Re: [DISCUSS] KIP-109: Old Consumer Deprecation

I cant speak for anyone else, but a rolling upgrade is definitely how we (LinkedIn) will do the migration. On Thu, Jan 5, 2017 at 4:28 PM, Gwen Shapira wrote: > it sounds good to have > it, but that's probably not how people will end up migrati >

Re: [DISCUSS] KIP-109: Old Consumer Deprecation

Since the APIs are super different, I expect migrating from the old to the new consumer will involve some re-write of the app that does the consuming. In most such cases, the upgrade path involves running both versions side-by-side for a while, validating results and then retiring the old version.

[jira] [Created] (KAFKA-4602) KIP-72 Allow putting a bound on memory consumed by Incoming requests

radai rosenblatt created KAFKA-4602: --- Summary: KIP-72 Allow putting a bound on memory consumed by Incoming requests Key: KAFKA-4602 URL: https://issues.apache.org/jira/browse/KAFKA-4602 Project:

[jira] [Commented] (KAFKA-4601) Avoid duplicated repartitioning in KStream DSL

[ https://issues.apache.org/jira/browse/KAFKA-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802932#comment-15802932 ] Bill Bejeck commented on KAFKA-4601: Thanks for the explanation. Avoiding duplicated partitioning

[jira] [Updated] (KAFKA-4601) Avoid duplicated repartitioning in KStream DSL

[ https://issues.apache.org/jira/browse/KAFKA-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-4601: --- Assignee: (was: Bill Bejeck) > Avoid duplicated repartitioning in KStream DSL >

[jira] [Commented] (KAFKA-4601) Avoid duplicated repartitioning in KStream DSL

[ https://issues.apache.org/jira/browse/KAFKA-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802904#comment-15802904 ] Guozhang Wang commented on KAFKA-4601: -- [~bbejeck] Note that it may be more complex than it sounds:

Re: [DISCUSS] KIP-109: Old Consumer Deprecation

im all for (working towards) getting rid of old code, but there's still no solid migration path - you'll be "stranding" users on deprecated, no longer maintained code with no "safe" way out that does not involve downtime (specifically old and new consumers cannot correctly divide up partitions

[GitHub] kafka pull request #2320: MINOR: Maybe decorate inner topics for SourceNode

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/2320 MINOR: Maybe decorate inner topics for SourceNode When creating the source node in TopologyBuilder, we need to decorate its input topics if they are inner (i.e. repartition) topics with the

[jira] [Commented] (KAFKA-4601) Avoid duplicated repartitioning in KStream DSL

[ https://issues.apache.org/jira/browse/KAFKA-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802878#comment-15802878 ] Bill Bejeck commented on KAFKA-4601: If it's ok, picking this one up. > Avoid duplicated

[jira] [Assigned] (KAFKA-4601) Avoid duplicated repartitioning in KStream DSL

[ https://issues.apache.org/jira/browse/KAFKA-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck reassigned KAFKA-4601: -- Assignee: Bill Bejeck > Avoid duplicated repartitioning in KStream DSL >

[jira] [Created] (KAFKA-4601) Avoid duplicated repartitioning in KStream DSL

Guozhang Wang created KAFKA-4601: Summary: Avoid duplicated repartitioning in KStream DSL Key: KAFKA-4601 URL: https://issues.apache.org/jira/browse/KAFKA-4601 Project: Kafka Issue Type: Bug

[jira] [Work stopped] (KAFKA-4468) Correctly calculate the window end timestamp after read from state stores

[ https://issues.apache.org/jira/browse/KAFKA-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4468 stopped by Bill Bejeck. -- > Correctly calculate the window end timestamp after read from state stores >

[jira] [Updated] (KAFKA-4468) Correctly calculate the window end timestamp after read from state stores

[ https://issues.apache.org/jira/browse/KAFKA-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-4468: --- Assignee: (was: Bill Bejeck) > Correctly calculate the window end timestamp after read from state

[jira] [Commented] (KAFKA-4575) Transient failure in ConnectDistributedTest.test_pause_and_resume_sink in consuming messages after resuming sink connector

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

[jira] [Resolved] (KAFKA-4575) Transient failure in ConnectDistributedTest.test_pause_and_resume_sink in consuming messages after resuming sink connector

[ https://issues.apache.org/jira/browse/KAFKA-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4575. -- Resolution: Fixed Fix Version/s: 0.10.2.0 Issue resolved by pull request

[GitHub] kafka pull request #2313: KAFKA-4575: ensure topic created before starting s...

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

Very strong support from me too :) On Thu, Jan 5, 2017 at 12:09 PM, Vahid S Hashemian wrote: > Hi all, > > There was some discussion recently on deprecating the old consumer ( > https://www.mail-archive.com/dev@kafka.apache.org/msg59084.html). > Ismael suggested to

Re: [VOTE] KIP-102 - Add close with timeout for consumers

I hate going back and forth on this, but KafkaProducer.close() (with no timeout) is equivalent to close(Long.MAX_VALUE, TimeUnit.MILLISECONDS), while the KafkaConsumer.close() is equivalent to close(30*1000,TimeUnit.MILLISECONDS). Isn't this kind of inconsistency best to avoid? On Thu, Jan 5,

[jira] [Commented] (KAFKA-4588) QueryableStateIntegrationTest.shouldNotMakeStoreAvailableUntilAllStoresAvailable is occasionally failing on jenkins

[ https://issues.apache.org/jira/browse/KAFKA-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802744#comment-15802744 ] Matthias J. Sax commented on KAFKA-4588: One more instance:

[jira] [Commented] (KAFKA-4222) Transient failure in QueryableStateIntegrationTest.queryOnRebalance

[ https://issues.apache.org/jira/browse/KAFKA-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802735#comment-15802735 ] Matthias J. Sax commented on KAFKA-4222: One more instance:

Re: [DISCUSS] KIP-105: Addition of Record Level for Sensors

Thanks Jay, will fix the motivation. We have a microbenchmark and perf graph in the PR: https://github.com/apache/kafka/pull/1446#issuecomment-268106260 I'll need to think some more about point 3. Thanks Eno > On 5 Jan 2017,

Re: [DISCUSS] KIP-105: Addition of Record Level for Sensors

Guozhang, I was thinking to do this in Sensor.java, and not touch the MetricsReporter interface. Basically I'd go for not adding a KafkaMetric at all with this approach. But perhaps I'm missing something. Thanks Eno > On 5 Jan 2017, at 17:59, Guozhang Wang wrote: > > I

Re: [VOTE] KIP-102 - Add close with timeout for consumers

Thank you, Ismael. I have sent another one. Hopefully that will appear in its own thread. Rajini On Thu, Jan 5, 2017 at 9:30 PM, Ismael Juma wrote: > Thanks Rajini. This seems to be happening a lot lately: Gmail is showing > the vote message in the discuss thread. > > Ismael

[VOTE] KIP-102 - Add close with timeout for consumers

Hi all, I would like to start the voting process for *KIP-102 - Add close with timeout for consumers*: https://cwiki.apache.org/confluence/display/KAFKA/KIP-102+-+Add+close+with+timeout+for+consumers This KIP adds a new close method with a timeout for consumers similar to the close method

Re: [jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

> On Jan 5, 2017, at 3:47 AM, Edoardo Comar wrote: > > "Jiangjie Qin (JIRA)" wrote on 05/01/2017 08:06:58: > >>[ https://issues.apache.org/jira/browse/KAFKA-4497? >> page=com.atlassian.jira.plugin.system.issuetabpanels:comment- >>

Re: [DISCUSS] KIP-108: Create Topic Policy

Yeah, I agree... having a validation mode would be nice. We should be explicit that passing validation doesn't 100% guarantee that a subsequent call to create the topic will succeed, though. There is an obvious race condition there-- for example, with a plugin which consults some external

Re: [DISCUSS] KIP-108: Create Topic Policy

it would be nice to have a dry-run or validate ability added to this kip. since we are offloading validation to a 3rd party implementor a random user can't know a priori (based solely on kafka configs) whether a call should succeed without actually creating the topic. a similar case is in connect

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

See Changes: [wangguoz] MINOR: Update JavaDoc for KTable helper interfaces -- [...truncated 7970 lines...] kafka.integration.SaslPlaintextTopicMetadataTest >

Re: [VOTE] KIP-102 - Add close with timeout for consumers

Thanks Rajini. This seems to be happening a lot lately: Gmail is showing the vote message in the discuss thread. Ismael On Thu, Jan 5, 2017 at 9:23 PM, Rajini Sivaram wrote: > Hi all, > > I would like to start the voting process for *KIP-102 - Add close with > timeout

Re: [VOTE] KIP-88: OffsetFetch Protocol Update

Thanks for the updates, +1 Ismael On Thu, Jan 5, 2017 at 6:14 PM, Vahid S Hashemian wrote: > I'd like to start another round of voting on KIP-88 after recent changes > to the KIP ( > https://cwiki.apache.org/confluence/display/KAFKA/KIP- >

[jira] [Created] (KAFKA-4600) Consumer proceeds on when ConsumerRebalanceListener fails

Braedon Vickers created KAFKA-4600: -- Summary: Consumer proceeds on when ConsumerRebalanceListener fails Key: KAFKA-4600 URL: https://issues.apache.org/jira/browse/KAFKA-4600 Project: Kafka

Re: [VOTE] KIP-88: OffsetFetch Protocol Update

Thanks for the updates. +1 On Thu, Jan 5, 2017 at 11:42 AM, Gwen Shapira wrote: > +1 > > On Thu, Jan 5, 2017 at 10:14 AM, Vahid S Hashemian > wrote: > > I'd like to start another round of voting on KIP-88 after recent changes > > to the KIP ( > >

[VOTE] KIP-102 - Add close with timeout for consumers

Hi all, I would like to start the voting process for *KIP-102 - Add close with timeout for consumers:* https://cwiki.apache.org/confluence/display/KAFKA/KIP-102+-+Add+close+with+timeout+for+consumers This KIP adds a new close method with a timeout for consumers similar to the close method in

Re: [DISCUSS] KIP-102 - Add close with timeout for consumers

Thank you, Jason. I will start the vote. On Thu, Jan 5, 2017 at 5:52 PM, Jason Gustafson wrote: > Yeah, if you start a vote soon, I think it has a chance to get into 0.10.2. > I guess it's up to Ewen, but I'm happy to help review. > > -Jason > > On Wed, Jan 4, 2017 at 11:42

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

Hello all, I updated the KIP document with the changes discussed here. In particular: 1. The consumer config was renamed from 'fetch.mode' to 'isolation.level'. The values were changed appropriately as well. 2. Clarified the transactional guarantees for the consumer. 3. Added a

Re: [DISCUSS] KIP-109: Old Consumer Deprecation

It's not time for voting, but a huge +1 from me. On Thu, Jan 5, 2017 at 8:25 PM, Vahid S Hashemian wrote: > Thanks Ismael. I added that to the KIP. > > > > > From: Ismael Juma > To: dev@kafka.apache.org > Date: 01/05/2017 12:16 PM >

Re: [DISCUSS] KIP-109: Old Consumer Deprecation

Thanks Ismael. I added that to the KIP. From: Ismael Juma To: dev@kafka.apache.org Date: 01/05/2017 12:16 PM Subject:Re: [DISCUSS] KIP-109: Old Consumer Deprecation Sent by:isma...@gmail.com Thanks Vahid, +1 (predictably). Worth mentioning in the

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802412#comment-15802412 ] Michael Andre Pearce (IG) commented on KAFKA-4497: -- confirming class path via the

Re: [DISCUSS] KIP-109: Old Consumer Deprecation

Thanks Vahid, +1 (predictably). Worth mentioning in the KIP that compatibility with older brokers (0.10.0 and later) is another feature that will only be supported by the Java consumer. Ismael On 5 Jan 2017 8:10 pm, "Vahid S Hashemian" wrote: > Hi all, > > There was

[jira] [Commented] (KAFKA-3264) Mark the old Scala consumer and related classes as deprecated

[ https://issues.apache.org/jira/browse/KAFKA-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802401#comment-15802401 ] Ismael Juma commented on KAFKA-3264: Excellent, thanks! > Mark the old Scala consumer and related

[DISCUSS] KIP-109: Old Consumer Deprecation

Hi all, There was some discussion recently on deprecating the old consumer ( https://www.mail-archive.com/dev@kafka.apache.org/msg59084.html). Ismael suggested to cover the discussion and voting of major deprecations like this under a KIP. So I started KIP-109 (

[jira] [Commented] (KAFKA-3264) Mark the old Scala consumer and related classes as deprecated

[ https://issues.apache.org/jira/browse/KAFKA-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802393#comment-15802393 ] Vahid Hashemian commented on KAFKA-3264: That's what I thought. The discussion link you sent does

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802394#comment-15802394 ] Michael Andre Pearce (IG) commented on KAFKA-4497: -- [~junrao] [~becket_qin] anything else

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802390#comment-15802390 ] Michael Andre Pearce (IG) commented on KAFKA-4497: -- log4j log-cleaner.log with TRACE,

[jira] [Updated] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Andre Pearce (IG) updated KAFKA-4497: - Attachment: log-cleaner.log.1.zip logcleaner log for error on 0.10.1.1

[jira] [Commented] (KAFKA-3264) Mark the old Scala consumer and related classes as deprecated

[ https://issues.apache.org/jira/browse/KAFKA-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802373#comment-15802373 ] Ismael Juma commented on KAFKA-3264: I think it's fine to do that later. We'll have to decide if it's

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802365#comment-15802365 ] Michael Andre Pearce (IG) commented on KAFKA-4497: --

[jira] [Updated] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Andre Pearce (IG) updated KAFKA-4497: - Attachment: com_ig_trade_v1_position_event--demo--compacted-14.tar.gz

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802326#comment-15802326 ] Michael Andre Pearce (IG) commented on KAFKA-4497: -- [2017-01-05 19:37:07,137] TRACE

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802319#comment-15802319 ] Michael Andre Pearce (IG) commented on KAFKA-4497: -- Perfect, that triggered it to run,

Re: [VOTE] KIP-88: OffsetFetch Protocol Update

+1 On Thu, Jan 5, 2017 at 10:14 AM, Vahid S Hashemian wrote: > I'd like to start another round of voting on KIP-88 after recent changes > to the KIP ( > https://cwiki.apache.org/confluence/display/KAFKA/KIP-88%3A+OffsetFetch+Protocol+Update > > ). > > The discussion

[jira] [Commented] (KAFKA-4599) KafkaConsumer encounters SchemaException when Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802307#comment-15802307 ] Andrew Olson commented on KAFKA-4599: - Another recent similar reported occurrence from the mailing

[jira] [Commented] (KAFKA-4551) StreamsSmokeTest.test_streams intermittent failure

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

[GitHub] kafka pull request #2319: KAFKA-4551: StreamsSmokeTest.test_streams intermit...

Github user dguy closed the pull request at: https://github.com/apache/kafka/pull/2319 --- 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 #2315: MINOR: Update JavaDoc for KTable helper interfaces

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2315 --- 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] [Commented] (KAFKA-4551) StreamsSmokeTest.test_streams intermittent failure

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

[GitHub] kafka pull request #2319: KAFKA-4551: StreamsSmokeTest.test_streams intermit...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2319 KAFKA-4551: StreamsSmokeTest.test_streams intermittent failure Remove use of TestTimestampExtractor as it causes the logs to roll and segments get deleted. Remove the wcnt example as it is

Re: [DISCUSS] KIP-105: Addition of Record Level for Sensors

This is great! A couple of quick comments: 1. It'd be good to make the motivation a bit more clear. I think the motivation is "We want to have lots of partition/task/etc metrics but we're concerned about the performance impact so we want to disable them by default." Currently the

[jira] [Comment Edited] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802233#comment-15802233 ] Michael Andre Pearce (IG) edited comment on KAFKA-4497 at 1/5/17 7:14 PM:

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802233#comment-15802233 ] Michael Andre Pearce (IG) commented on KAFKA-4497: -- [~junrao] , we took it from the

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

Hi Jun Thanks for raising these points. Thorough as ever! 1) Changes made as requested. 2) Done. 3) My plan for handing returning leaders is to simply to force the Leader Epoch to increment if a leader returns. I don't plan to fix KAFKA-1120 as part of this KIP. It is really a separate issue

Re: [DISCUSS] KIP-98: Exactly Once Delivery and Transactional Messaging

Hi Jun, Let me start picking off a some of your questions (we're giving the shadow log suggestion a bit more thought before responding). 100. Security: It seems that if an app is mistakenly configured with the > appId of an existing producer, it can take over the pid and prevent the > existing

[jira] [Created] (KAFKA-4599) KafkaConsumer encounters SchemaException when Kafka broker stopped

Andrew Olson created KAFKA-4599: --- Summary: KafkaConsumer encounters SchemaException when Kafka broker stopped Key: KAFKA-4599 URL: https://issues.apache.org/jira/browse/KAFKA-4599 Project: Kafka

[jira] [Commented] (KAFKA-4497) log cleaner breaks on timeindex

[ https://issues.apache.org/jira/browse/KAFKA-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802131#comment-15802131 ] Jun Rao commented on KAFKA-4497: [~michael.andre.pearce], thanks for the update. Did you get the 0.10.1.1

[jira] [Commented] (KAFKA-4598) Create new SourceTask commit callback method that takes offsets param

[ https://issues.apache.org/jira/browse/KAFKA-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802110#comment-15802110 ] Shikhar Bhushan commented on KAFKA-4598: In the meantime the workaround is to use

[jira] [Created] (KAFKA-4598) Create new SourceTask commit callback method that takes offsets param

Shikhar Bhushan created KAFKA-4598: -- Summary: Create new SourceTask commit callback method that takes offsets param Key: KAFKA-4598 URL: https://issues.apache.org/jira/browse/KAFKA-4598 Project:

[VOTE] KIP-88: OffsetFetch Protocol Update

I'd like to start another round of voting on KIP-88 after recent changes to the KIP ( https://cwiki.apache.org/confluence/display/KAFKA/KIP-88%3A+OffsetFetch+Protocol+Update ). The discussion thread can be found here: https://www.mail-archive.com/dev@kafka.apache.org/msg59608.html The

Re: KafkaConnect SinkTask::put

Hi David, You can override the underlying consumer's `max.poll.records` setting for this. E.g. consumer.max.poll.records=500 Best, Shikhar On Thu, Jan 5, 2017 at 3:59 AM wrote: > Is there any way of limiting the number of events that are passed into the > call to

  1   2   >