Jenkins build is back to normal : kafka-trunk-jdk7 #1895

See

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

See Changes: [wangguoz] MINOR: update JavaDocs for Kafka Streams DSL helpers [ismael] KAFKA-4635; Client Compatibility follow-ups [ismael] KAFKA-4450; Add upgrade tests for 0.10.1 and rename TRUNK to DEV_BRANCH

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

See Changes: [me] KAFKA-4679: Remove unstable markers from Connect APIs -- [...truncated 95 lines...] if (partitionData.timestamp == OffsetCommitRequest.DEFAULT_TIMESTAMP)

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

a few extra points: 1. broker per disk might also incur more client <--> broker sockets: suppose every producer / consumer "talks" to >1 partition, there's a very good chance that partitions that were co-located on a single 10-disk broker would now be split between several single-disk broker

[jira] [Commented] (KAFKA-4679) Remove unstable markers from Connect APIs

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

[GitHub] kafka pull request #2423: KAFKA-4679 Remove unstable markers from Connect AP...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2423 --- 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-4679) Remove unstable markers from Connect APIs

[ https://issues.apache.org/jira/browse/KAFKA-4679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4679: - Resolution: Fixed Fix Version/s: 0.10.3.0 Status: Resolved

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

See Changes: [wangguoz] MINOR: update JavaDocs for Kafka Streams DSL helpers [ismael] KAFKA-4635; Client Compatibility follow-ups [ismael] KAFKA-4450; Add upgrade tests for 0.10.1 and rename TRUNK to DEV_BRANCH

[jira] [Updated] (KAFKA-3733) Avoid long command lines by setting CLASSPATH in environment

[ https://issues.apache.org/jira/browse/KAFKA-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3733: - Assignee: Adrian Muraru > Avoid long command lines by setting CLASSPATH in

Jenkins build is back to normal : kafka-trunk-jdk7 #1893

See

[jira] [Updated] (KAFKA-4450) Add missing 0.10.1.x upgrade tests and ensure ongoing compatibility checks

[ https://issues.apache.org/jira/browse/KAFKA-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4450: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Add missing 0.10.1.x upgrade

[jira] [Commented] (KAFKA-4450) Add missing 0.10.1.x upgrade tests and ensure ongoing compatibility checks

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

[GitHub] kafka pull request #2457: KAFKA-4450: Add upgrade tests for 0.10.1 releases ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2457 --- 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 #2462: MINOR: JavaDoc markup cleanup

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2462 MINOR: JavaDoc markup cleanup You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka javaDocImprovements9 Alternatively you can review and

[jira] [Updated] (KAFKA-4635) Client Compatibility follow-up

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

[jira] [Commented] (KAFKA-4635) Client Compatibility follow-up

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

[GitHub] kafka pull request #2414: KAFKA-4635: Client Compatibility follow-ups

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2414 --- 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 #2459: MINOR: update JavaDocs for Kafka Streams DSL helpe...

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

Jenkins build is back to normal : kafka-0.10.1-jdk7 #114

See

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

A few more responses: > 101. Compatibility during upgrade: Suppose that the brokers are upgraded to > the new version, but the broker message format is still the old one. If a > new producer uses the transaction feature, should the producer get an error > in this case? A tricky case can be that

[jira] [Updated] (KAFKA-4327) Move Reset Tool from core to streams

[ https://issues.apache.org/jira/browse/KAFKA-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4327: --- Description: This is a follow up on https://issues.apache.org/jira/browse/KAFKA-4008

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

Hi again Jun, I have update the document to address your comments below, but including the responses inline to make it easier for everyone to stay on top of the conversation. > 106. Compacted topics. > 106.1. When all messages in a transaction are removed, we could remove the > commit/abort

[GitHub] kafka pull request #2461: MINOR: added upgrade and API changes to docs

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2461 MINOR: added upgrade and API changes to docs You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka addStreamsUpdateSecton Alternatively

[GitHub] kafka pull request #2449: KAFKA-4557: Handle Producer.send correctly in expi...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2449 --- 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-4557) ConcurrentModificationException in KafkaProducer event loop

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

[jira] [Resolved] (KAFKA-4557) ConcurrentModificationException in KafkaProducer event loop

[ https://issues.apache.org/jira/browse/KAFKA-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4557. Resolution: Fixed Issue resolved by pull request 2449 [https://github.com/apache/kafka/pull/2449]

Jenkins build is back to normal : kafka-0.10.2-jdk7 #50

See

[jira] [Commented] (KAFKA-4277) creating ephemeral node already exist

[ https://issues.apache.org/jira/browse/KAFKA-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843636#comment-15843636 ] Jun Rao commented on KAFKA-4277: According to the following, it doesn't seem this can happen in ZK.

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

See Changes: [ismael] KAFKA-4664; Update docs/protocol.html with KIP-97 information [me] MINOR: Update copyright year in the NOTICE file. -- [...truncated 63 lines...]

[jira] [Assigned] (KAFKA-4220) Clean up & provide better error message when incorrect argument types are provided in the command line client

[ https://issues.apache.org/jira/browse/KAFKA-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishita Mandhan reassigned KAFKA-4220: - Assignee: Vahid Hashemian (was: Ishita Mandhan) > Clean up & provide better error

[jira] [Assigned] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created

[ https://issues.apache.org/jira/browse/KAFKA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishita Mandhan reassigned KAFKA-2857: - Assignee: Vahid Hashemian (was: Ishita Mandhan) > ConsumerGroupCommand throws

[GitHub] kafka pull request #2460: MINOR: Update copyright year in the NOTICE file.

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2460 --- 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 #1787: KAFKA-3940 Log should check the return value of di...

Github user imandhan closed the pull request at: https://github.com/apache/kafka/pull/1787 --- 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 #2203: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

Github user imandhan closed the pull request at: https://github.com/apache/kafka/pull/2203 --- 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-3940) Log should check the return value of dir.mkdirs()

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

[jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created

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

[GitHub] kafka pull request #2288: MINOR: Create Hyperlinks in protocol api docs

Github user imandhan closed the pull request at: https://github.com/apache/kafka/pull/2288 --- 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-4664) Update docs/protocol.html with KIP-97 information

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

[jira] [Updated] (KAFKA-4664) Update docs/protocol.html with KIP-97 information

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

[GitHub] kafka pull request #2387: KAFKA-4664: Update docs/protocol.html with KIP-97 ...

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

Build failed in Jenkins: kafka-0.10.2-jdk7 #49

See Changes: [ismael] KAFKA-4704; Coordinator cache loading fails if groupId is reused for -- [...truncated 4080 lines...] kafka.server.KafkaConfigTest > testUncleanLeaderElectionDefault STARTED

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

See

[GitHub] kafka pull request #2460: MINOR: Update copyright year in the NOTICE file.

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/2460 MINOR: Update copyright year in the NOTICE file. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka minor-update-notice-year

[jira] [Commented] (KAFKA-4708) Transient failure in BrokerApiVersionsCommandTest.checkBrokerApiVersionCommandOutput

[ https://issues.apache.org/jira/browse/KAFKA-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843491#comment-15843491 ] Colin P. McCabe commented on KAFKA-4708: Hmm. I ran this unit test locally in a loop for an hour

[jira] [Resolved] (KAFKA-4704) Group coordinator cache loading fails if groupId is used first for consumer groups and then for simple consumer

[ https://issues.apache.org/jira/browse/KAFKA-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4704. Resolution: Fixed Issue resolved by pull request 2455 [https://github.com/apache/kafka/pull/2455]

[jira] [Commented] (KAFKA-4704) Group coordinator cache loading fails if groupId is used first for consumer groups and then for simple consumer

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

[GitHub] kafka pull request #2455: KAFKA-4704: Coordinator cache loading fails if gro...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2455 --- 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-4704) Group coordinator cache loading fails if groupId is used first for consumer groups and then for simple consumer

[ https://issues.apache.org/jira/browse/KAFKA-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843389#comment-15843389 ] Jason Gustafson commented on KAFKA-4704: [~onurkaraman] Interesting point. Unfortunately, this

[jira] [Created] (KAFKA-4708) Transient failure in BrokerApiVersionsCommandTest.checkBrokerApiVersionCommandOutput

Jason Gustafson created KAFKA-4708: -- Summary: Transient failure in BrokerApiVersionsCommandTest.checkBrokerApiVersionCommandOutput Key: KAFKA-4708 URL: https://issues.apache.org/jira/browse/KAFKA-4708

[jira] [Created] (KAFKA-4707) Transient failure FetchRequestTest.testBrokerRespectsPartitionsOrderAndSizeLimits

Jason Gustafson created KAFKA-4707: -- Summary: Transient failure FetchRequestTest.testBrokerRespectsPartitionsOrderAndSizeLimits Key: KAFKA-4707 URL: https://issues.apache.org/jira/browse/KAFKA-4707

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

See Changes: [wangguoz] MINOR: Update KTable JavaDoc [wangguoz] KAFKA-4644: Improve test coverage of StreamsPartitionAssignor -- [...truncated 8319 lines...]

Re: [DISCUSS]- JIRA ISSUE KAFKA-4566 : Can't Symlink to Kafka bins

Thanks for the background. This is a tough one, because all the proposed solutions are very long, and we would have to put them in each script file. I think it's probably not worth it, since people can write their own wrappers that suit their needs. But I haven't thought about it that much--

[GitHub] kafka pull request #2435: Replaced for with foreach and replace if ,else if,...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2435 --- 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] [Assigned] (KAFKA-4317) RocksDB checkpoint files lost on kill -9

[ https://issues.apache.org/jira/browse/KAFKA-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-4317: - Assignee: Damian Guy > RocksDB checkpoint files lost on kill -9 >

[jira] [Commented] (KAFKA-4644) Improve test coverage of StreamsPartitionAssignor

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

[jira] [Updated] (KAFKA-4644) Improve test coverage of StreamsPartitionAssignor

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

[GitHub] kafka pull request #2448: KAFKA-4644: Improve test coverage of StreamsPartit...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2448 --- 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 #2438: MINOR: update KTable JavaDoc

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2438 --- 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] [Assigned] (KAFKA-4650) Improve test coverage org.apache.kafka.streams.kstream.internals

[ https://issues.apache.org/jira/browse/KAFKA-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-4650: - Assignee: Damian Guy > Improve test coverage org.apache.kafka.streams.kstream.internals >

Re: Fwd: [DISCUSS] KIP-114: KTable materialization and improved semantics

I think Jan is saying that they don't always need to be materialized, i.e., filter just needs to apply the ValueGetter, it doesn't need yet another physical state store. On Fri, 27 Jan 2017 at 15:49 Michael Noll wrote: > Like Damian, and for the same reasons, I am more in

Re: Fwd: [DISCUSS] KIP-114: KTable materialization and improved semantics

Like Damian, and for the same reasons, I am more in favor of overloading methods rather than introducing `materialize()`. FWIW, we already have a similar API setup for e.g. `KTable#through(topicName, stateStoreName)`. A related but slightly different question is what e.g. Jan Filipiak mentioned

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

See Changes: [ismael] MINOR: Include more detail in `ConfigDef.parseType` exception message -- [...truncated 8314 lines...] kafka.integration.SaslPlaintextTopicMetadataTest >

Jenkins build is back to normal : kafka-0.10.2-jdk7 #46

See

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

See

Build failed in Jenkins: kafka-0.10.2-jdk7 #45

See Changes: [ismael] KAFKA-4578; Upgrade notes for 0.10.2.0 -- [...truncated 8302 lines...] kafka.server.KafkaConfigTest > testUncleanLeaderElectionDefault STARTED

Jenkins build is back to normal : kafka-trunk-jdk7 #1888

See

[jira] [Updated] (KAFKA-4385) producer is sending too many unnecessary meta data request if the meta data for a topic is not available and "auto.create.topics.enable" =false

[ https://issues.apache.org/jira/browse/KAFKA-4385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stevo Slavic updated KAFKA-4385: Affects Version/s: 0.9.0.1 > producer is sending too many unnecessary meta data request if the meta

[jira] [Commented] (KAFKA-4385) producer is sending too many unnecessary meta data request if the meta data for a topic is not available and "auto.create.topics.enable" =false

[ https://issues.apache.org/jira/browse/KAFKA-4385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842831#comment-15842831 ] Stevo Slavic commented on KAFKA-4385: - {{UnknownTopicOrPartitionException}} extends

[GitHub] kafka pull request #2345: MINOR: ConfigDef `parseType` exception message upd...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2345 --- 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 #2459: MINOR: update JavaDocs for Kafka Streams DSL helpe...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2459 MINOR: update JavaDocs for Kafka Streams DSL helpers - also deprecate ZK config for Streams You can merge this pull request into a Git repository by running: $ git pull

[jira] [Assigned] (KAFKA-4703) Test with two SASL_SSL listeners with different JAAS contexts

[ https://issues.apache.org/jira/browse/KAFKA-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balint Molnar reassigned KAFKA-4703: Assignee: Balint Molnar > Test with two SASL_SSL listeners with different JAAS contexts >

[GitHub] kafka pull request #2445: KAFKA-4578: Upgrade notes for 0.10.2.0

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2445 --- 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-4578) Upgrade notes for 0.10.2.0

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

[jira] [Commented] (KAFKA-4578) Upgrade notes for 0.10.2.0

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

[jira] [Comment Edited] (KAFKA-4474) Poor kafka-streams throughput

[ https://issues.apache.org/jira/browse/KAFKA-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842519#comment-15842519 ] Andres Gomez Ferrer edited comment on KAFKA-4474 at 1/27/17 10:40 AM: --

[jira] [Updated] (KAFKA-4685) All partitions offline, no controller znode in ZK

[ https://issues.apache.org/jira/browse/KAFKA-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sinóros-Szabó Péter updated KAFKA-4685: --- Summary: All partitions offline, no controller znode in ZK (was: All partitions

[jira] [Commented] (KAFKA-4474) Poor kafka-streams throughput

[ https://issues.apache.org/jira/browse/KAFKA-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842519#comment-15842519 ] Andres Gomez Ferrer commented on KAFKA-4474: Thank you [~enothereska]!! I know that there is

[jira] [Commented] (KAFKA-4474) Poor kafka-streams throughput

[ https://issues.apache.org/jira/browse/KAFKA-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15842514#comment-15842514 ] Eno Thereska commented on KAFKA-4474: - Thanks [~agomez] for your excellent investigation. I can

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

See Changes: [wangguoz] MINOR: Add Streams system test for broker backwards compatibility [wangguoz] MINOR: Streams API JavaDoc improvements -- [...truncated 8317 lines...]

Re: Trying to understand design decision about producer ack and min.insync.replicas

> On Jan 27, 2017, at 12:18 AM, Ewen Cheslack-Postava wrote: > > On Thu, Jan 26, 2017 at 4:23 PM, Luciano Afranllie > wrote: > >> I was thinking about the situation where you have less brokers in the ISR >> list than the number set in

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

[ https://issues.apache.org/jira/browse/KAFKA-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reopened KAFKA-4222: --- re-opening as there was one more case of this recently. However the build has been cleaned up. Just

[jira] [Updated] (KAFKA-4696) Streams standby task assignment should be state-store aware

[ https://issues.apache.org/jira/browse/KAFKA-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4696: -- Description: Task Assignment is currently not aware of which tasks have State Stores. This can result

Re: Trying to understand design decision about producer ack and min.insync.replicas

On Thu, Jan 26, 2017 at 4:23 PM, Luciano Afranllie wrote: > I was thinking about the situation where you have less brokers in the ISR > list than the number set in min.insync.replicas. > > My idea was that if I, as an administrator, for a given topic, want to > favor

Jenkins build is back to normal : kafka-trunk-jdk7 #1886

See