[jira] [Updated] (KAFKA-4515) Async producer send not retrying on TimeoutException: Batch Expired

[ https://issues.apache.org/jira/browse/KAFKA-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Shang updated KAFKA-4515: Description: We are testing out broker failure resiliency, we have a cluster of 3 brokers, a topic with 5

[jira] [Created] (KAFKA-4515) Async producer send not retrying on TimeoutException: Batch Expired

Di Shang created KAFKA-4515: --- Summary: Async producer send not retrying on TimeoutException: Batch Expired Key: KAFKA-4515 URL: https://issues.apache.org/jira/browse/KAFKA-4515 Project: Kafka

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

Usecase in IG: Fund transfer between accounts. When we debit one account and fund another we must ensure the records to both occur as an acid action, and as a single transaction. Today we achieve this because we have jms, as such we can do the actions needed in an xa transaction across both

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

Hi Jay, For me having an XA transaction allows for ensuring ACID across my application. I believe it is part of the JMS api, and obviously JMS still is in enterprise very widely adopted for Messaging transport , so obviously to say it isn't widely used i think is ignoring a whole range of

Re: [VOTE]: KIP-97: The client compatibility KIP

+1 (binding) On Thu, Dec 8, 2016 at 10:00 AM Guozhang Wang wrote: > +1 (binding) > > On Thu, Dec 8, 2016 at 9:39 AM, Sriram Subramanian > wrote: > > > +1 (binding) > > > > On Thu, Dec 8, 2016 at 5:42 AM, Ismael Juma wrote: > > > > >

Re: Improvements to Jenkins pull request builder

Nice! Thanks Ismael. On Thu, Dec 8, 2016 at 10:47 AM Damian Guy wrote: > Cool - thanks Ismael! > > On Thu, 8 Dec 2016 at 18:22 Guozhang Wang wrote: > > > Thanks Ismael, this is sper helpful! > > > > > > Guozhang > > > > On Thu, Dec 8, 2016 at

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734049#comment-15734049 ] Apurva Mehta commented on KAFKA-4477: - Also, could you share the values of the following metrics

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734018#comment-15734018 ] James Cheng commented on KAFKA-4477: Does the broker respond to metadata requests (kafkacat -L)? You

[jira] [Comment Edited] (KAFKA-1120) Controller could miss a broker state change

[ https://issues.apache.org/jira/browse/KAFKA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734005#comment-15734005 ] James Cheng edited comment on KAFKA-1120 at 12/9/16 2:02 AM: - Is KAFKA-4443 an

[jira] [Commented] (KAFKA-1120) Controller could miss a broker state change

[ https://issues.apache.org/jira/browse/KAFKA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734005#comment-15734005 ] James Cheng commented on KAFKA-1120: Is https://issues.apache.org/jira/browse/KAFKA-4443 an instance

Build failed in Jenkins: kafka-trunk-jdk7 #1741

See Changes: [ismael] MINOR: Fix metric collection NPE during shutdown [ismael] MINOR: Upgrade Gradle to 3.2.1 and Scala to 2.12.1 -- [...truncated 8006 lines...] kafka.server.KafkaConfigTest

[jira] [Commented] (KAFKA-4505) Cannot get topic lag since kafka upgrade from 0.8.1.0 to 0.10.1.0

[ https://issues.apache.org/jira/browse/KAFKA-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733965#comment-15733965 ] huxi commented on KAFKA-4505: - Do you use the new consumer or the zk consumer after the migration? > Cannot

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

See Changes: [ismael] MINOR: Fix metric collection NPE during shutdown [ismael] MINOR: Upgrade Gradle to 3.2.1 and Scala to 2.12.1 -- [...truncated 3930 lines...] at

[jira] [Updated] (KAFKA-4509) Task reusage on rebalance fails for threads on same host

[ https://issues.apache.org/jira/browse/KAFKA-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4509: --- Status: Patch Available (was: In Progress) > Task reusage on rebalance fails for threads on

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

See Changes: [wangguoz] MINOR: Update JavaDoc of KStream interface -- [...truncated 26687 lines...] org.apache.kafka.streams.KafkaStreamsTest >

[jira] [Commented] (KAFKA-4509) Task reusage on rebalance fails for threads on same host

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

[GitHub] kafka pull request #2233: KAFKA-4509: Task reusage on rebalance fails for th...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2233 KAFKA-4509: Task reusage on rebalance fails for threads on same host You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka

[jira] [Commented] (KAFKA-4486) Kafka Streams - exception in process still commits offsets

[ https://issues.apache.org/jira/browse/KAFKA-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733801#comment-15733801 ] Joel Lundell commented on KAFKA-4486: - Hi! This was on the critical path of a project so I had to work

[GitHub] kafka pull request #2216: MINOR: Upgrade Gradle to 3.2.1 and Scala to 2.12.1

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2216 --- 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 #2221: MINOR: fix metric collection NPE during shutdown

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2221 --- 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-98: Exactly Once Delivery and Transactional Messaging

Hey Edoardo, For (3) can you outline what you think the benefit and use cases for a more general cross-system XA feature would be an what changes to the proposal would be required to enable it? When I have asked people who wanted cross-system XA in the past what they wanted it for, I haven't

[GitHub] kafka-site issue #32: Added section for Kafka Summit on the Events page

Github user guozhangwang commented on the issue: https://github.com/apache/kafka-site/pull/32 Merged. --- 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

[GitHub] kafka-site pull request #32: Added section for Kafka Summit on the Events pa...

Github user asfgit closed the pull request at: https://github.com/apache/kafka-site/pull/32 --- 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-3008) Connect should parallelize task start/stop

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

[GitHub] kafka pull request #2232: HOTFIX: Fix HerderRequest.compareTo()

GitHub user shikhar opened a pull request: https://github.com/apache/kafka/pull/2232 HOTFIX: Fix HerderRequest.compareTo() With KAFKA-3008 (#1788), the implementation does not respect the contract that 'sgn(x.compareTo(y)) == -sgn(y.compareTo(x))' This fix addresses the

[jira] [Commented] (KAFKA-4514) Add Codec for ZStandard Compression

[ https://issues.apache.org/jira/browse/KAFKA-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733639#comment-15733639 ] Ismael Juma commented on KAFKA-4514: Sounds good. If someone from the community has time and interest

[jira] [Commented] (KAFKA-4514) Add Codec for ZStandard Compression

[ https://issues.apache.org/jira/browse/KAFKA-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733627#comment-15733627 ] Thomas Graves commented on KAFKA-4514: -- Ok thanks. I wanted to get it filed to get peoples input on

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

See Changes: [ismael] KAFKA-4392; Handle NoSuchFileException gracefully in StateDirectory -- [...truncated 15998 lines...] org.apache.kafka.connect.runtime.standalone.StandaloneHerderTest >

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733442#comment-15733442 ] Dustin Cote commented on KAFKA-4477: It may also be helpful to grab the associated zookeeper logs. If

Re: [VOTE] 0.10.1.1 RC0

The scala 2.12 artifacts aren’t showing up, any chance of publishing them? > On 9 Dec 2016, at 07:57, Vahid S Hashemian wrote: > > +1 > > Build and quickstart worked fine on Ubuntu, Mac, Windows 32 and 64 bit. > > Thanks for running the release. > > Regards, >

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

Hi, thanks, very interesting KIP ... I haven't fully digested it yet. We have many users who choose not to use the Java client, so I have concerns about the added complexity in developing the clients. A few questions. 1 - is mixing transactional and non transactional messages on the *same

Re: [VOTE] 0.10.1.1 RC0

+1 Build and quickstart worked fine on Ubuntu, Mac, Windows 32 and 64 bit. Thanks for running the release. Regards, --Vahid From: Guozhang Wang To: "us...@kafka.apache.org" , "dev@kafka.apache.org" ,

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733238#comment-15733238 ] Apurva Mehta commented on KAFKA-4477: - Hi [~tdevoe], [~jj83], [~michael.andre.pearce] : I had a look

[jira] [Assigned] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-4477: --- Assignee: Apurva Mehta > Node reduces its ISR to itself, and doesn't recover. Other nodes do

[GitHub] kafka pull request #2153: MINOR: Update JavaDoc of KStream interface

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2153 --- 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-site issue #36: Streams standalone docs

Github user guozhangwang commented on the issue: https://github.com/apache/kafka-site/pull/36 Thanks @derrickdoo , LGTM overall. One meta question: Does any of those changes need to be in `kafka`'s docs folder as well? During each release we will do a copy-paste from the

[jira] [Commented] (KAFKA-4498) Extract Streams section as a separate page from documentation.html

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

[GitHub] kafka-site pull request #35: KAFKA-4498: [DO NOT MERGE] add rewrite rule for...

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

Re: Improvements to Jenkins pull request builder

Cool - thanks Ismael! On Thu, 8 Dec 2016 at 18:22 Guozhang Wang wrote: > Thanks Ismael, this is sper helpful! > > > Guozhang > > On Thu, Dec 8, 2016 at 5:24 AM, Ismael Juma wrote: > > > Hi everyone, > > > > Given the recent availability of the

[jira] [Commented] (KAFKA-4514) Add Codec for ZStandard Compression

[ https://issues.apache.org/jira/browse/KAFKA-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15733027#comment-15733027 ] Ismael Juma commented on KAFKA-4514: Yeah, this would be a good addition. It probably needs a KIP as

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

Like wise I think handling transactions separately is important as we should consider supporting or at least a how in future session transactions, xa transactions etc Sent using OWA for iPhone From: Michael Pearce Sent: Thursday,

Re: [DISCUSS] KIP-100 - Relax Type constraints in Kafka Streams API

Hi Xavier, The KIP looks good - thanks! Damian On Thu, 8 Dec 2016 at 18:12 Xavier Léauté wrote: > I recently filed https://issues.apache.org/jira/browse/KAFKA-4481, which > Guozhang agreed was a bug. However fixing this will require some minor > changes to the existing

Re: [VOTE] 0.10.1.1 RC0

Ismael, Thanks for pointing out, turns out I forgot to click "close" on the staging repository panel :P It should show up now. Guozhang On Wed, Dec 7, 2016 at 11:01 PM, Ismael Juma wrote: > Thanks Guozhang. The Maven staging repo link doesn't seem to have 0.10.1.1. > Can

[jira] [Created] (KAFKA-4514) Add Codec for ZStandard Compression

Thomas Graves created KAFKA-4514: Summary: Add Codec for ZStandard Compression Key: KAFKA-4514 URL: https://issues.apache.org/jira/browse/KAFKA-4514 Project: Kafka Issue Type: Improvement

Re: Improvements to Jenkins pull request builder

Thanks Ismael, this is sper helpful! Guozhang On Thu, Dec 8, 2016 at 5:24 AM, Ismael Juma wrote: > Hi everyone, > > Given the recent availability of the superior open-source pull request > builder[1] in Apache Jenkins (previously we were only able to use the >

[DISCUSS] KIP-100 - Relax Type constraints in Kafka Streams API

I recently filed https://issues.apache.org/jira/browse/KAFKA-4481, which Guozhang agreed was a bug. However fixing this will require some minor changes to the existing Kafka Streams APIs. I've outlined the required changes and binary / source compatibility implications in the KIP

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

Hi For me delivering the once delivery story should not require transactions. Your last statement makes me feel you think they do. Atm reading the kip I see only once delivery working end to end if I have also transactions enabled on the consumer also. I shouldn't have to do this. Whilst

Re: [VOTE]: KIP-97: The client compatibility KIP

+1 (binding) On Thu, Dec 8, 2016 at 9:39 AM, Sriram Subramanian wrote: > +1 (binding) > > On Thu, Dec 8, 2016 at 5:42 AM, Ismael Juma wrote: > > > Thanks for the KIP Colin, +1 (binding) from me. > > > > I agree with Rajini's suggestions. Also, since the

Re: [VOTE]: KIP-97: The client compatibility KIP

Thanks, folks. I added some discussion about the potential to support new versions of SaslHandshakeRequest through this mechanism. It may be useful down the road. I added a little more detail about how the BrokerVersions command would work, as well as some sample output from the current patch.

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

Hey Michael, There is no overhead from transactions if you don't use them, and they are not needed to leverage the capabilities of the idempotent producer. However, some of the underlying mechanics are shared, such as the message format changes and the InitPidRequest. We see them as the two

[jira] [Updated] (KAFKA-4457) Add a command to list the broker version information

[ https://issues.apache.org/jira/browse/KAFKA-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-4457: --- Issue Type: Sub-task (was: Improvement) Parent: KAFKA-4462 > Add a command to list

Re: [VOTE]: KIP-97: The client compatibility KIP

+1 (binding) On Thu, Dec 8, 2016 at 5:42 AM, Ismael Juma wrote: > Thanks for the KIP Colin, +1 (binding) from me. > > I agree with Rajini's suggestions. Also, since the command is a public > interface, it would be good to include details in the KIP. > > Ismael > > On Wed, Dec

Re: [DISCUSS] KIP-99: Add Global Tables to Kafka Streams

Hi Michael, I don't see how that helps? Lets say we have tables Person(id, device_id, name, ...), Device(id, person_id, type, ...), and both are keyed with same type. And we have a stream, that for the sake of simplicity, has both person_id and device_id ( i know this is a bit contrived!) so our

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732759#comment-15732759 ] Tom DeVoe commented on KAFKA-4477: -- An additional comment - after we restart the node with this issue,

[jira] [Commented] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732738#comment-15732738 ] Tom DeVoe commented on KAFKA-4477: -- We are seeing the same issue on Ubuntu 14.04 - have not gotten a

[jira] [Resolved] (KAFKA-4392) Failed to lock the state directory due to an unexpected exception

[ https://issues.apache.org/jira/browse/KAFKA-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4392. Resolution: Fixed > Failed to lock the state directory due to an unexpected exception >

[jira] [Commented] (KAFKA-4392) Failed to lock the state directory due to an unexpected exception

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

[jira] [Updated] (KAFKA-4392) Failed to lock the state directory due to an unexpected exception

[ https://issues.apache.org/jira/browse/KAFKA-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4392: --- Fix Version/s: 0.10.2.0 > Failed to lock the state directory due to an unexpected exception >

[GitHub] kafka pull request #2121: KAFKA-4392: Handle NoSuchFileException gracefully ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2121 --- 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] Deprecating the old consumers in trunk

Thanks Onur and Jason. I filed a JIRA to track this: https://issues.apache.org/jira/browse/KAFKA-4513 My take is that this would be good to have and one could argue that we should not remove the old consumers until we have it. However, I think we should still go ahead with the deprecation of the

[jira] [Created] (KAFKA-4513) Support migration of old consumers to new consumers without downtime

Ismael Juma created KAFKA-4513: -- Summary: Support migration of old consumers to new consumers without downtime Key: KAFKA-4513 URL: https://issues.apache.org/jira/browse/KAFKA-4513 Project: Kafka

Re: [DISCUSS] KIP-99: Add Global Tables to Kafka Streams

The key type returned by both KeyValueMappers (in the current trunk version, that type is named `R`) would need to be the same for this to work. On Wed, Dec 7, 2016 at 4:46 PM, Damian Guy wrote: > Michael, > > We can only support outerJoin if both tables are keyed the

[jira] [Updated] (KAFKA-4512) Provide snap package

[ https://issues.apache.org/jira/browse/KAFKA-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Hall updated KAFKA-4512: Attachment: snap_run snapcraft.yaml Attached is a snap build config file that will

[jira] [Created] (KAFKA-4512) Provide snap package

Michael Hall created KAFKA-4512: --- Summary: Provide snap package Key: KAFKA-4512 URL: https://issues.apache.org/jira/browse/KAFKA-4512 Project: Kafka Issue Type: New Feature

Re: [VOTE]: KIP-97: The client compatibility KIP

Thanks for the KIP Colin, +1 (binding) from me. I agree with Rajini's suggestions. Also, since the command is a public interface, it would be good to include details in the KIP. Ismael On Wed, Dec 7, 2016 at 5:17 PM, Colin McCabe wrote: > Hi all, > > I heard that the VOTE

Improvements to Jenkins pull request builder

Hi everyone, Given the recent availability of the superior open-source pull request builder[1] in Apache Jenkins (previously we were only able to use the Jenkins Enterprise GH PR plugin), I have switched our PR builds to that. I took the chance to replace the existing build with three separate

[jira] [Resolved] (KAFKA-4511) Update PR jobs to use GitHub pull request builder plugin

[ https://issues.apache.org/jira/browse/KAFKA-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4511. Resolution: Fixed Works like a charm: https://github.com/apache/kafka/pull/2231 > Update PR jobs

[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=15732126#comment-15732126 ] Jan Ehrhardt commented on KAFKA-4497: - [~huxi_2b]: The producer is sending data lz4 compressed. These

[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=15732091#comment-15732091 ] Robert Schumann commented on KAFKA-4497: [~huxi_2b]: Yes, AFAIK we enabled lz4 compression on the

[jira] [Updated] (KAFKA-4509) Task reusage on rebalance fails for threads on same host

[ https://issues.apache.org/jira/browse/KAFKA-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4509: Reviewer: Eno Thereska > Task reusage on rebalance fails for threads on same host >

[jira] [Commented] (KAFKA-4511) Update PR jobs to use GitHub pull request builder plugin

[ https://issues.apache.org/jira/browse/KAFKA-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732086#comment-15732086 ] Ismael Juma commented on KAFKA-4511: I created 3 separate PR builds to replace the existing one:

[GitHub] kafka pull request #2231: NOMERGE: Test new Jenkins PR plugin v4

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2231 NOMERGE: Test new Jenkins PR plugin v4 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-4511-test-jenkins-pr-builds-v4

[GitHub] kafka pull request #2230: NOMERGE: Test new Jenkins PR plugin v3

Github user ijuma closed the pull request at: https://github.com/apache/kafka/pull/2230 --- 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 #2230: NOMERGE: Test new Jenkins PR plugin v3

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2230 NOMERGE: Test new Jenkins PR plugin v3 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-4511-test-jenkins-pr-builds

[GitHub] kafka pull request #2229: NOMERGE: Test new Jenkins PR plugin v2

Github user ijuma closed the pull request at: https://github.com/apache/kafka/pull/2229 --- 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 #2228: NOMERGE: Test new Jenkins PR plugin

Github user ijuma closed the pull request at: https://github.com/apache/kafka/pull/2228 --- 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 #2229: NOMERGE: Test new Jenkins PR plugin v2

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2229 NOMERGE: Test new Jenkins PR plugin v2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-4511-test-jenkins-pr-builds-v2

[GitHub] kafka pull request #2228: NOMERGE: Test new Jenkins PR plugin

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2228 NOMERGE: Test new Jenkins PR plugin You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-4511-test-jenkins-pr-builds Alternatively

[jira] [Created] (KAFKA-4511) Update PR jobs to use GitHub pull request builder plugin

Ismael Juma created KAFKA-4511: -- Summary: Update PR jobs to use GitHub pull request builder plugin Key: KAFKA-4511 URL: https://issues.apache.org/jira/browse/KAFKA-4511 Project: Kafka Issue

[jira] [Commented] (KAFKA-3899) Consumer.poll() stuck in loop if wrong credentials are supplied

[ https://issues.apache.org/jira/browse/KAFKA-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731821#comment-15731821 ] Matthias Klein commented on KAFKA-3899: --- The consumer also gets stuck when accessing a kafka

[jira] [Comment Edited] (KAFKA-4505) Cannot get topic lag since kafka upgrade from 0.8.1.0 to 0.10.1.0

[ https://issues.apache.org/jira/browse/KAFKA-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731713#comment-15731713 ] Romaric Parmentier edited comment on KAFKA-4505 at 12/8/16 10:03 AM: -

Re: [VOTE]: KIP-97: The client compatibility KIP

+1 (non-binding) It may be worth noting in the KIP that clients can check SASL handshake version (prior to authentication) using this approach if we ever need to update the handshake request. But versions request cannot be used to check which SASL mechanisms are supported, that needs to go

[jira] [Commented] (KAFKA-4505) Cannot get topic lag since kafka upgrade from 0.8.1.0 to 0.10.1.0

[ https://issues.apache.org/jira/browse/KAFKA-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731713#comment-15731713 ] Romaric Parmentier commented on KAFKA-4505: --- Hi huxi, Thank you for you answer. Indeed, it

[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=15731654#comment-15731654 ] huxi commented on KAFKA-4497: - [~roschumann] Did you enable compression for topic 'xdc_listing-status-v2' ? >

Re: [VOTE]: KIP-97: The client compatibility KIP

+1 (non-binding) I have some concerns on the potential for complexity and testing requirement, but in general having a client interoperable with two broker version would be great for many users. -- Edoardo Comar IBM MessageHub eco...@uk.ibm.com

[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=15731588#comment-15731588 ] huxi commented on KAFKA-4497: - LogCleaner.cleanOrSleep only captures LogCleaningAbortedException exception, so

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

My apologies, my computer is auto spellchecking and I didn’t notice before sending. *@Sriram Thanks Mike On 08/12/2016, 08:35, "Michael Pearce" wrote: @Shiram, I would like to be able to have though exactly once delivery without the need to use more heavy

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

@Shiram, I would like to be able to have though exactly once delivery without the need to use more heavy weight transactions, this is why I’m proposing separate KIP these are not entirely orthogonal. Agreed the uuid could be re-used in supporting transactionality, but I wouldn’t want to have

[GitHub] kafka-site issue #36: Streams standalone docs

Github user derrickdoo commented on the issue: https://github.com/apache/kafka-site/pull/36 @guozhangwang here's a PR for the standalone Streams docs page --- 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

[GitHub] kafka-site pull request #36: Streams standalone docs

GitHub user derrickdoo opened a pull request: https://github.com/apache/kafka-site/pull/36 Streams standalone docs Here's the changes we talked about to pull Streams documentation out to it's own page. Ended up having to do the redirect on URLs that contain anchor tags that match

Re: [VOTE] KIP-87 - Add Compaction Tombstone Flag

Hi Jun, 4) On v3 we honour the tombstone. As such we expect it to be set correctly as per the KIP. 4.1) why would we want to produce an error when its v3? This is the exact purpose to support non-null tombstone’s 4.2) again here im unclear on the question on the v3, produce request we expect