[jira] [Resolved] (KAFKA-4076) Kafka broker shuts down due to irrecoverable IO error

[ https://issues.apache.org/jira/browse/KAFKA-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-4076. Resolution: Invalid Pl reopen the issue, if still exists. > Kafka broker shuts down due

[jira] [Commented] (KAFKA-4716) Fix logic for re-checking if internal topic is ready

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

[GitHub] kafka pull request #2526: KAFKA-4716: Fix case when controller cannot be rea...

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

[jira] [Commented] (KAFKA-4753) KafkaConsumer susceptible to FetchResponse starvation

[ https://issues.apache.org/jira/browse/KAFKA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860872#comment-15860872 ] Onur Karaman commented on KAFKA-4753: - It might mitigate users whose consumers participate in group

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

It sounds like producers will now be idempotent by default. I.e. - if we upgrade and do nothing different, we have idempotent producer? and absolutely no way to get the old behavior back? I don't think anyone needs non-idempotent producer, just want to clarify :) On Tue, Feb 7, 2017 at 3:10 PM,

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

i'm concerned about transactional.id uniqueness in real-world conditions. When users were forced to manually define unique broker ids, we saw lots of errors with "duplicate broker id" on startup show up on the mailing list. When we added a persistent (to filesystem) auto-generated broker ID, the

[jira] [Assigned] (KAFKA-2260) Allow specifying expected offset on produce

[ https://issues.apache.org/jira/browse/KAFKA-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-2260: Assignee: (was: Ewen Cheslack-Postava) > Allow specifying expected

[jira] [Commented] (KAFKA-4753) KafkaConsumer susceptible to FetchResponse starvation

[ https://issues.apache.org/jira/browse/KAFKA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860815#comment-15860815 ] Jason Gustafson commented on KAFKA-4753: Could scenario 1 be mitigated with a new partition

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

I not sure I'm clear on the expected behavior of READ_COMMITTED in some interleaved cases: * If a transaction starts, sends few messages and someone writes non-transactional event into the same topic/partition, few more events from that transaction and then a commit. I think the producer will

[jira] [Comment Edited] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860768#comment-15860768 ] Jason Gustafson edited comment on KAFKA-4739 at 2/10/17 5:48 AM: -

[jira] [Commented] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860768#comment-15860768 ] Jason Gustafson commented on KAFKA-4739: [~neoeahit] Thanks for the update. These logs look much

[GitHub] kafka pull request #2475: MINOR: Use an explicit `Errors` object when possib...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2475 --- 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-2143) Replicas get ahead of leader and fail

[ https://issues.apache.org/jira/browse/KAFKA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860712#comment-15860712 ] Mathieu Filotto edited comment on KAFKA-2143 at 2/10/17 5:02 AM: - Is the

[jira] [Commented] (KAFKA-2143) Replicas get ahead of leader and fail

[ https://issues.apache.org/jira/browse/KAFKA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860712#comment-15860712 ] Mathieu Filotto commented on KAFKA-2143: Is the upgrade the only option ? Is 0.10 upgrade is

[jira] [Commented] (KAFKA-2292) failed fetch request logging doesn't indicate source of request

[ https://issues.apache.org/jira/browse/KAFKA-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860708#comment-15860708 ] Mathieu Filotto commented on KAFKA-2292: [~ted.m] any feed back on this one ? Thanks > failed

[jira] [Updated] (KAFKA-4506) Refactor AbstractRequest to contain version information

[ https://issues.apache.org/jira/browse/KAFKA-4506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4506: - Fix Version/s: (was: 0.10.2.0) > Refactor AbstractRequest to contain version

[jira] [Assigned] (KAFKA-4731) Add event-based session windows

[ https://issues.apache.org/jira/browse/KAFKA-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck reassigned KAFKA-4731: -- Assignee: Bill Bejeck > Add event-based session windows > --- > >

[jira] [Updated] (KAFKA-4754) Correctly parse '=' characters in command line overrides

[ https://issues.apache.org/jira/browse/KAFKA-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-4754: --- Status: Patch Available (was: Open) > Correctly parse '=' characters in command line overrides >

[GitHub] kafka pull request #2529: KAFKA-4754: Correctly parse '=' characters in comm...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/2529 KAFKA-4754: Correctly parse '=' characters in command line overrides You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka

[jira] [Commented] (KAFKA-4754) Correctly parse '=' characters in command line overrides

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

[GitHub] kafka pull request #2488: MINOR: add architecture section and configure / ex...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2488 --- 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-4754) Correctly parse '=' characters in command line overrides

[ https://issues.apache.org/jira/browse/KAFKA-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860597#comment-15860597 ] Grant Henke commented on KAFKA-4754: Its worth noting, it was also possible to echo out passwords on

[jira] [Commented] (KAFKA-4525) Kafka should not require SSL trust store password

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

[GitHub] kafka pull request #2246: KAFKA-4525: Kafka should not require SSL trust sto...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2246 --- 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 #2382: KAFKA-4617: Generate core project with correct sou...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2382 --- 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] [Updated] (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:all-tabpanel ] Ismael Juma updated KAFKA-4617: --- Resolution: Fixed Fix Version/s: 0.10.3.0 Status: Resolved (was: Patch Available)

[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=15860582#comment-15860582 ] ASF GitHub Bot commented on KAFKA-4617: --- Github user asfgit closed the pull request at:

[jira] [Created] (KAFKA-4754) Correctly parse '=' characters in command line overrides

Grant Henke created KAFKA-4754: -- Summary: Correctly parse '=' characters in command line overrides Key: KAFKA-4754 URL: https://issues.apache.org/jira/browse/KAFKA-4754 Project: Kafka Issue

Jenkins build is back to normal : kafka-trunk-jdk8 #1265

See

[jira] [Commented] (KAFKA-4654) Improve test coverage MemoryLRUCache

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

[GitHub] kafka pull request #2500: KAFKA-4654 improve test coverage for MemoryLRUCach...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2500 --- 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] [Updated] (KAFKA-4654) Improve test coverage MemoryLRUCache

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

[GitHub] kafka-site issue #46: Fix routing bugs

Github user guozhangwang commented on the issue: https://github.com/apache/kafka-site/pull/46 Could you close this PR? @derrickdoo --- 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

[GitHub] kafka-site issue #46: Fix routing bugs

Github user guozhangwang commented on the issue: https://github.com/apache/kafka-site/pull/46 It has been merge in https://github.com/apache/kafka-site/pull/45 --- 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

[GitHub] kafka-site issue #44: 0102 fixes

Github user guozhangwang commented on the issue: https://github.com/apache/kafka-site/pull/44 @derrickdoo Could you close this? --- 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

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

On Thu, Feb 9, 2017 at 3:37 PM, Colin McCabe wrote: > On Thu, Feb 9, 2017, at 11:40, Dong Lin wrote: > > Thanks for all the comments Colin! > > > > To answer your questions: > > - Yes, a broker will shutdown if all its log directories are bad. > > That makes sense. Can you

[jira] [Commented] (KAFKA-4564) When the destination brokers are down or misconfigured in config, Streams should fail fast

[ https://issues.apache.org/jira/browse/KAFKA-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860430#comment-15860430 ] Matthias J. Sax commented on KAFKA-4564: [~umesh9...@gmail.com] It would be nice if you could add

[GitHub] kafka-site issue #46: Fix routing bugs

Github user derrickdoo commented on the issue: https://github.com/apache/kafka-site/pull/46 @guozhangwang I think this will fix the routing issues you mentioned. --- 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

[GitHub] kafka-site pull request #46: Fix routing bugs

GitHub user derrickdoo opened a pull request: https://github.com/apache/kafka-site/pull/46 Fix routing bugs - Update fronted JS redirect logic to handle legacy anchor links - Add documentation sub directories to avoid 404's You can merge this pull request into a Git repository

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

On Thu, Feb 9, 2017, at 11:40, Dong Lin wrote: > Thanks for all the comments Colin! > > To answer your questions: > - Yes, a broker will shutdown if all its log directories are bad. That makes sense. Can you add this to the writeup? > - I updated the KIP to explicitly state that a log

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

See Changes: [ismael] HOTFIX: Add missing default arguments to __init__ -- [...truncated 19917 lines...] org.apache.kafka.streams.KafkaStreamsTest > testCannotCleanupWhileRunning PASSED

documentation feedback

@apachekafka suggested addition to http://kafka.apache.org/documentation/#security - section 5 - Examples using console-producer and console-consumer: echo "ssl" | /usr/hdp/current/kafka-broker/bin/kafka-console-producer.sh --broker-list $KAFKABROKERSSSL --topic test2 --producer.config

[jira] [Commented] (KAFKA-4753) KafkaConsumer susceptible to FetchResponse starvation

[ https://issues.apache.org/jira/browse/KAFKA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860366#comment-15860366 ] Onur Karaman commented on KAFKA-4753: - One way to mitigate but not fully solve the starvation problem

[jira] [Commented] (KAFKA-4716) Fix logic for re-checking if internal topic is ready

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

[GitHub] kafka pull request #2522: KAFKA-4716: Send request to controller

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2522 --- 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] [Updated] (KAFKA-4716) Fix logic for re-checking if internal topic is ready

[ https://issues.apache.org/jira/browse/KAFKA-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4716: - Resolution: Fixed Fix Version/s: 0.10.3.0 Status: Resolved (was: Patch

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

Eno, You are right, it is not a new scenario. Thinking a bit more on how we could incorporate KIP-98 in Streams, I feel that if EOS is turned on inside Streams, then we probably cannot always resume from the checkpointed offsets as it is not guaranteed to be "consistent"; but since EOS may not

[jira] [Created] (KAFKA-4753) KafkaConsumer susceptible to FetchResponse starvation

Onur Karaman created KAFKA-4753: --- Summary: KafkaConsumer susceptible to FetchResponse starvation Key: KAFKA-4753 URL: https://issues.apache.org/jira/browse/KAFKA-4753 Project: Kafka Issue

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

Hi Guozhang, It seems to me we have the same semantics today. Are you saying there is a new failure scenario? Thanks, Eno > On 9 Feb 2017, at 19:42, Guozhang Wang wrote: > > More specifically, here is my reasoning of failure cases, and would like to > get your feedbacks:

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

More specifically, here is my reasoning of failure cases, and would like to get your feedbacks: *StreamTask* For stream-task, the committing order is 1) flush state (may send more records to changelog in producer), 2) flush producer, 3) commit upstream offsets. My understanding is that the

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Thanks for all the comments Colin! To answer your questions: - Yes, a broker will shutdown if all its log directories are bad. - I updated the KIP to explicitly state that a log directory will be assumed to be good until broker sees IOException when it tries to access the log directory. -

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

Hi, Mayuresh, Thanks for the reply. A few more comments below. On Wed, Feb 8, 2017 at 9:14 PM, Mayuresh Gharat wrote: > Hi Jun, > > Thanks for the review. Please find the responses inline. > > 1. It seems the problem that you are trying to address is that java >

[jira] [Comment Edited] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860011#comment-15860011 ] Vipul Singh edited comment on KAFKA-4739 at 2/9/17 7:21 PM: Hey [~hachikuji].

[jira] [Commented] (KAFKA-4739) KafkaConsumer poll going into an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860011#comment-15860011 ] Vipul Singh commented on KAFKA-4739: Hey [~hachikuji]. We tried to reproduce the issue again.

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

On Thu, Feb 9, 2017, at 11:03, Colin McCabe wrote: > Thanks, Dong L. > > Do we plan on bringing down the broker process when all log directories > are offline? > > Can you explicitly state on the KIP that the log dirs are all considered > good after the broker process is bounced? It seems like

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Thanks, Dong L. Do we plan on bringing down the broker process when all log directories are offline? Can you explicitly state on the KIP that the log dirs are all considered good after the broker process is bounced? It seems like an important thing to be clear about. Also, perhaps discuss how

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

A quick question re: `We will add the above config parameter to *StreamsConfig*. During *StreamTask#commit()*, *StandbyTask#commit()*, and *GlobalUpdateStateTask#flushState()* we will check if the checkpoint interval has elapsed and write the checkpoint file.` Will the writing of the checkpoint

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

Thanks for the explanation. This makes sense. Best, Dong On Thu, Feb 9, 2017 at 10:51 AM, Colin McCabe wrote: > On Wed, Feb 8, 2017, at 19:02, Dong Lin wrote: > > I am not aware of any semantics that will be caused by sharing > > NetworkClient between producer/consumer and

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

On Wed, Feb 8, 2017, at 19:02, Dong Lin wrote: > I am not aware of any semantics that will be caused by sharing > NetworkClient between producer/consumer and AdminClient. But I agree that > there is currently no good way to share such an internal class between > them. And yes, goal is to reduce

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

But 5 min means, that we (in the worst case) need to reply data from the last 5 minutes to get the store ready. So why not go with the min possible value of 30 seconds to speed up this process if the impact is negligible anyway? What do you gain by being conservative? -Matthias On 2/9/17 2:54

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

On Wed, Feb 8, 2017, at 18:39, Dong Lin wrote: > Hey Colin, > > Thanks for updating the KIP. I have two followup questions: > > - It seems that setCreationConfig(...) is a bit redundant given that most > arguments (e.g. topic name, partition num) are already passed to > TopicsContext.create(...)

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 (non-binding) On Thu, Feb 9, 2017 at 6:37 PM, Apurva Mehta wrote: > +1 (non-binding) > > On Thu, Feb 9, 2017 at 10:33 AM, Colin McCabe wrote: > > > +1 (non-binding) > > > > > > > > On Thu, Feb 9, 2017, at 07:31, Ismael Juma wrote: > > > Hi everyone,

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 (non-binding) On Thu, Feb 9, 2017 at 10:33 AM, Colin McCabe wrote: > +1 (non-binding) > > > > On Thu, Feb 9, 2017, at 07:31, Ismael Juma wrote: > > Hi everyone, > > > > Since everyone in the discuss thread was in favour (10 people responded), > > I > > would like to

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 (non-binding) On Thu, Feb 9, 2017, at 07:31, Ismael Juma wrote: > Hi everyone, > > Since everyone in the discuss thread was in favour (10 people responded), > I > would like to initiate the voting process for KIP-118: Drop Support for > Java 7 in Kafka 0.11: > >

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 --Vahid From: Onur Karaman To: dev@kafka.apache.org Date: 02/09/2017 10:02 AM Subject:Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11 +1 On Thu, Feb 9, 2017 at 9:58 AM, Guozhang Wang wrote: > +1 > > On Thu,

[jira] [Commented] (KAFKA-4745) KafkaLZ4BlockOutputStream.java incorrectly finishes the last frame

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

[GitHub] kafka pull request #2528: KAFKA-4745 -Optimize close to remove unnecessary f...

GitHub user wdroste opened a pull request: https://github.com/apache/kafka/pull/2528 KAFKA-4745 -Optimize close to remove unnecessary flush -Remove unnecessary 'flush', the underlying stream should handle it on close, also most apps flush before close. You can merge this pull

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 On Thu, Feb 9, 2017 at 9:58 AM, Guozhang Wang wrote: > +1 > > On Thu, Feb 9, 2017 at 9:32 AM, BigData dev > wrote: > > > +1 > > > > Thanks, > > Bharat > > > > > > On Thu, Feb 9, 2017 at 9:27 AM, Jason Gustafson > > wrote: > >

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 On Thu, Feb 9, 2017 at 9:32 AM, BigData dev wrote: > +1 > > Thanks, > Bharat > > > On Thu, Feb 9, 2017 at 9:27 AM, Jason Gustafson > wrote: > > > +1 > > > > On Thu, Feb 9, 2017 at 9:00 AM, Grant Henke wrote: > > > > > +1 > >

[jira] [Commented] (KAFKA-2507) Replace ControlledShutdown{Request,Response} with org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859871#comment-15859871 ] Ismael Juma commented on KAFKA-2507: [~mimaison], the benefit of this is relatively small with a high

[jira] [Commented] (KAFKA-2507) Replace ControlledShutdown{Request,Response} with org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859862#comment-15859862 ] Mickael Maison commented on KAFKA-2507: --- [~granthenke][~ijuma] It's now over 1 year later. As there

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 Thanks, Bharat On Thu, Feb 9, 2017 at 9:27 AM, Jason Gustafson wrote: > +1 > > On Thu, Feb 9, 2017 at 9:00 AM, Grant Henke wrote: > > > +1 > > > > On Thu, Feb 9, 2017 at 10:51 AM, Mickael Maison < > mickael.mai...@gmail.com> > > wrote: > > > > > +1

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 On Thu, Feb 9, 2017 at 9:00 AM, Grant Henke wrote: > +1 > > On Thu, Feb 9, 2017 at 10:51 AM, Mickael Maison > wrote: > > > +1 too. > > > > On Thu, Feb 9, 2017 at 4:30 PM, Edoardo Comar wrote: > > > +1 (non-binding) > > >

Jenkins build is back to normal : kafka-trunk-jdk8 #1263

See

Re: KIP-121 [VOTE]: Add KStream peek method

＋1 （binding） On Thu, Feb 9, 2017 at 7:44 AM, Eno Thereska wrote: > +1 > > Thanks > Eno > > On 9 Feb 2017, at 11:04, Damian Guy wrote: > > > > +1 > > > > On Thu, 9 Feb 2017 at 10:26 Michael Noll wrote: > > > >> +1

[jira] [Commented] (KAFKA-1448) Filter-plugins for messages

[ https://issues.apache.org/jira/browse/KAFKA-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859803#comment-15859803 ] Mileta Cekovic commented on KAFKA-1448: --- Any filtering on server side should be able to understand

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 On Thu, Feb 9, 2017 at 10:51 AM, Mickael Maison wrote: > +1 too. > > On Thu, Feb 9, 2017 at 4:30 PM, Edoardo Comar wrote: > > +1 (non-binding) > > -- > > Edoardo Comar > > IBM MessageHub > >

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 too. On Thu, Feb 9, 2017 at 4:30 PM, Edoardo Comar wrote: > +1 (non-binding) > -- > Edoardo Comar > IBM MessageHub > eco...@uk.ibm.com > IBM UK Ltd, Hursley Park, SO21 2JN > > IBM United Kingdom Limited Registered in England

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 (non-binding) -- Edoardo Comar IBM MessageHub eco...@uk.ibm.com IBM UK Ltd, Hursley Park, SO21 2JN IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 (non binding) > On 9 Feb 2017, at 15:53, Damian Guy wrote: > > +1 > > On Thu, 9 Feb 2017 at 15:41 Bill Bejeck wrote: > >> +1 >> >> On Thu, Feb 9, 2017 at 10:31 AM, Ismael Juma wrote: >> >>> Hi everyone, >>> >>> Since everyone

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 On Thu, 9 Feb 2017 at 15:41 Bill Bejeck wrote: > +1 > > On Thu, Feb 9, 2017 at 10:31 AM, Ismael Juma wrote: > > > Hi everyone, > > > > Since everyone in the discuss thread was in favour (10 people > responded), I > > would like to initiate the voting

[GitHub] kafka pull request #2527: MINOR: update README with how to run code coverage...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2527 MINOR: update README with how to run code coverage on module. add reportCoverage at subProject level You can merge this pull request into a Git repository by running: $ git pull

Re: KIP-121 [VOTE]: Add KStream peek method

+1 Thanks Eno > On 9 Feb 2017, at 11:04, Damian Guy wrote: > > +1 > > On Thu, 9 Feb 2017 at 10:26 Michael Noll wrote: > >> +1 (non-binding) >> >> And thanks again for suggesting and driving this, Steven! :-) >> >> Best, >> Michael >> >> >> >>

Re: [VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

+1 On Thu, Feb 9, 2017 at 10:31 AM, Ismael Juma wrote: > Hi everyone, > > Since everyone in the discuss thread was in favour (10 people responded), I > would like to initiate the voting process for KIP-118: Drop Support for > Java 7 in Kafka 0.11: > >

[VOTE] KIP-118: Drop Support for Java 7 in Kafka 0.11

Hi everyone, Since everyone in the discuss thread was in favour (10 people responded), I would like to initiate the voting process for KIP-118: Drop Support for Java 7 in Kafka 0.11: https://cwiki.apache.org/confluence/display/KAFKA/KIP-118%3A+Drop+Support+for+Java+7+in+Kafka+0.11 The vote will

Re: KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

So far the feedback is positive, but there weren't many responses. I'll start a vote next week if there are no objections until then. Ismael On Fri, Feb 3, 2017 at 2:30 PM, Ismael Juma wrote: > Hi all, > > I have posted a KIP for dropping support for Scala 2.10 in Kafka

[GitHub] kafka pull request #2524: HOTFIX: default params missing

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2524 --- 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 #2523: MINOR: fix integer overflow in simple benchmark MB...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2523 --- 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 #2526: KAFKA-4716: Fix case when controller cannot be rea...

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2526 KAFKA-4716: Fix case when controller cannot be reached You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka 0.10.2-KAFKA-4716

[jira] [Commented] (KAFKA-4716) Fix logic for re-checking if internal topic is ready

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

[jira] [Work started] (KAFKA-4716) Fix logic for re-checking if internal topic is ready

[ https://issues.apache.org/jira/browse/KAFKA-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4716 started by Eno Thereska. --- > Fix logic for re-checking if internal topic is ready >

[jira] [Updated] (KAFKA-4716) Fix logic for re-checking if internal topic is ready

[ https://issues.apache.org/jira/browse/KAFKA-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4716: Status: Patch Available (was: In Progress) > Fix logic for re-checking if internal topic is ready

[jira] [Commented] (KAFKA-4484) Set more conservative default values on RocksDB for memory usage

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

[jira] [Updated] (KAFKA-4484) Set more conservative default values on RocksDB for memory usage

[ https://issues.apache.org/jira/browse/KAFKA-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4484: -- Status: Patch Available (was: In Progress) > Set more conservative default values on RocksDB for

[jira] [Work stopped] (KAFKA-4716) Fix logic for re-checking if internal topic is ready

[ https://issues.apache.org/jira/browse/KAFKA-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4716 stopped by Eno Thereska. --- > Fix logic for re-checking if internal topic is ready >

[jira] [Work started] (KAFKA-4716) Fix logic for re-checking if internal topic is ready

[ https://issues.apache.org/jira/browse/KAFKA-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4716 started by Eno Thereska. --- > Fix logic for re-checking if internal topic is ready >

[GitHub] kafka pull request #2525: KAFKA-4484: Set more conservative default values o...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2525 KAFKA-4484: Set more conservative default values on RocksDB for memory usage Lowered the default RocksDB settings for the block cache and write buffers You can merge this pull request into a Git

Re: [VOTE] 0.10.2.0 RC0

Unfortunately we had a regression in streams and KAFKA-4716 is now deemed a Blocker. https://issues.apache.org/jira/browse/KAFKA-4716 Eno > On 7 Feb 2017, at 23:56, Jun Rao wrote: > > Hi, Ewen, > > KAFKA-4725 has been

[jira] [Created] (KAFKA-4752) Streams Simple Benchmark MB/sec calculation is not correct for Join operations

Damian Guy created KAFKA-4752: - Summary: Streams Simple Benchmark MB/sec calculation is not correct for Join operations Key: KAFKA-4752 URL: https://issues.apache.org/jira/browse/KAFKA-4752 Project:

[GitHub] kafka pull request #2524: HOTFIX: default params missin

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2524 HOTFIX: default params missin This caused the bounce and smoke tests to fail on trunk. You can merge this pull request into a Git repository by running: $ git pull

  1   2   >