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

See

Re: [VOTE] KIP-206: Add support for UUID serialization and deserialization

+1 (binding) On Fri, Jan 26, 2018 at 9:16 AM, Colin McCabe wrote: > +1 (non-binding) > > > > On Fri, Jan 26, 2018, at 08:29, Ted Yu wrote: > > +1 > > > > On Fri, Jan 26, 2018 at 7:00 AM, Brandon Kirchner < > > brandon.kirch...@gmail.com> wrote: > > > > > Hi all, > > > > > >

Build failed in Jenkins: kafka-trunk-jdk9 #343

See Changes: [wangguoz] KAFKA-3625: Add public test utils for Kafka Streams (#4402) [wangguoz] KAFKA-6451: Simplifying KStreamReduce and KStreamAggregate [github] MINOR: Code refacotring in KTable-KTable Join

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

See Changes: [wangguoz] MINOR: Fix some streams web doc nits (#4411) -- [...truncated 1.46 MB...] org.apache.kafka.streams.integration.RestoreIntegrationTest >

[jira] [Created] (KAFKA-6500) Can not build aggregatedJavadoc

Pavel Timofeev created KAFKA-6500: - Summary: Can not build aggregatedJavadoc Key: KAFKA-6500 URL: https://issues.apache.org/jira/browse/KAFKA-6500 Project: Kafka Issue Type: Bug

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

See -- Started by an SCM change Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu xenial) in workspace

[jira] [Created] (KAFKA-6499) Avoid creating dummy checkpoint files with no state stores

Guozhang Wang created KAFKA-6499: Summary: Avoid creating dummy checkpoint files with no state stores Key: KAFKA-6499 URL: https://issues.apache.org/jira/browse/KAFKA-6499 Project: Kafka

Jenkins build is back to normal : kafka-1.0-jdk7 #137

See

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

See Changes: [wangguoz] MINOR: Fix some streams web doc nits (#4411) -- [...truncated 405.18 KB...] kafka.controller.ControllerIntegrationTest >

[jira] [Resolved] (KAFKA-6451) Simplify KStreamReduce

[ https://issues.apache.org/jira/browse/KAFKA-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6451. -- Resolution: Fixed Fix Version/s: 1.1.0 > Simplify KStreamReduce > --

Build failed in Jenkins: kafka-trunk-jdk9 #342

See Changes: [wangguoz] MINOR: Fix some streams web doc nits (#4411) -- [...truncated 1.03 MB...] org.apache.kafka.common.record.LegacyRecordTest > testChecksum[365]

Kafka Consumers not rebalancing.

Hi All, I was experimenting on the new consumer API and have a question regarding the rebalance process. I start a consumer group with single thread and make the Thread sleep while processing the records retrieved from the first consumer.poll call, i was making sure the Thread.sleep time goes

[jira] [Resolved] (KAFKA-6280) Allow for additional archive types to be loaded from plugin.path in Connect

[ https://issues.apache.org/jira/browse/KAFKA-6280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantine Karantasis resolved KAFKA-6280. --- Resolution: Fixed Fix Version/s: (was: 1.1.0)

Re: Choose the number of partitions/topics

so it goes beyond the throughput that kafka can support. You have to decide as to what degree of parallelism your application can support. If one message processing depends on processing for another message, that limits the degree to which you can process in parallel. Depending on how much

Re: [VOTE] KIP-232: Detect outdated metadata using leaderEpoch and partitionEpoch

Hey Colin, On Mon, Jan 29, 2018 at 11:23 AM, Colin McCabe wrote: > > On Mon, Jan 29, 2018 at 10:35 AM, Dong Lin wrote: > > > > > Hey Colin, > > > > > > I understand that the KIP will adds overhead by introducing > per-partition > > > partitionEpoch. I

Re: [VOTE] KIP-232: Detect outdated metadata using leaderEpoch and partitionEpoch

> On Mon, Jan 29, 2018 at 10:35 AM, Dong Lin wrote: > > > Hey Colin, > > > > I understand that the KIP will adds overhead by introducing per-partition > > partitionEpoch. I am open to alternative solutions that does not incur > > additional overhead. But I don't see a better

Re: [DISCUSS] KIP-86: Configurable SASL callback handlers

Hi all, To simplify dynamic update of SASL configs in future (e.g add a new SASL mechanism with a new callback handler or Login), I have separated out the broker-side configs with a mechanism prefix in the property name (similar to listener prefix) instead of including all the classes together as

[jira] [Created] (KAFKA-6498) Add RocksDB statistics via Streams metrics

Guozhang Wang created KAFKA-6498: Summary: Add RocksDB statistics via Streams metrics Key: KAFKA-6498 URL: https://issues.apache.org/jira/browse/KAFKA-6498 Project: Kafka Issue Type:

Re: [VOTE] KIP-232: Detect outdated metadata using leaderEpoch and partitionEpoch

I think it is possible to move to entirely use partitionEpoch instead of (topic, partition) to identify a partition. Client can obtain the partitionEpoch -> (topic, partition) mapping from MetadataResponse. We probably need to figure out a way to assign partitionEpoch to existing partitions in the

[jira] [Created] (KAFKA-6497) streams#store ambiguous InvalidStateStoreException

Pegerto Fernandez created KAFKA-6497: Summary: streams#store ambiguous InvalidStateStoreException Key: KAFKA-6497 URL: https://issues.apache.org/jira/browse/KAFKA-6497 Project: Kafka

[jira] [Resolved] (KAFKA-6079) Idempotent production for source connectors

[ https://issues.apache.org/jira/browse/KAFKA-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-6079. -- Resolution: Won't Fix Marking this as WONTFIX since it is *already possible since AK 0.11* to

Re: [DISCUSS] KIP 226 - Dynamic Broker Configuration

Hi all, I made a change to the KIP to specify sasl.jaas.config property for brokers separately for each mechanism, rather than together in a single login context as we do today in the JAAS config file. This will make it easier to add new mechanisms to a running broker (this is not in scope for

Re: [VOTE] KIP-232: Detect outdated metadata using leaderEpoch and partitionEpoch

Hey Colin, I understand that the KIP will adds overhead by introducing per-partition partitionEpoch. I am open to alternative solutions that does not incur additional overhead. But I don't see a better way now. IMO the overhead in the FetchResponse may not be that much. We probably should

Re: [VOTE] KIP-232: Detect outdated metadata using leaderEpoch and partitionEpoch

On Fri, Jan 26, 2018, at 12:17, Dong Lin wrote: > Hey Colin, > > > On Fri, Jan 26, 2018 at 10:16 AM, Colin McCabe wrote: > > > On Thu, Jan 25, 2018, at 16:47, Dong Lin wrote: > > > Hey Colin, > > > > > > Thanks for the comment. > > > > > > On Thu, Jan 25, 2018 at 4:15 PM,

Re: [DISCUSS] KIP-212: Enforce set of legal characters for connector names

Sorry if this has been answered elsewhere. But what is the rationale behind Connect explicitly escaping ' " and / when used in connector names? Shouldn't that be handled by percent-encoding when using REST endpoints? best, Colin On Fri, Jan 26, 2018, at 10:21, Sönke Liebau wrote: > I spent

Re: [VOTE] KIP-232: Detect outdated metadata using leaderEpoch and partitionEpoch

Just some clarification on the current fencing logic. Currently, if the producer uses acks=-1, a write will only succeed if the write is received by all in-sync replicas (i.e., committed). This is true even when min.isr is set since we first wait for a message to be committed and then check the

Choose the number of partitions/topics

Hi everyone I have design an integration between 2 systems throug our API Stream Kafka, and the requirements are unclear to choose properly the number of partitions/topics. That is the use case: My producer will send 28 different type of events, so I have decided to create 28 topics. The max

RE: [DISCUSS]KIP-235 DNS alias and secured connections

Hi, Yes I believe this might address what you're seeing as well. Jonathan Skrzypek Middleware Engineering Messaging Engineering Goldman Sachs International -Original Message- From: Stephane Maarek [mailto:steph...@simplemachines.com.au] Sent: 06 December 2017 10:43 To:

[jira] [Resolved] (KAFKA-6484) 'ConsumerGroupCommand' performance optimization for old consumer describe group

[ https://issues.apache.org/jira/browse/KAFKA-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-6484. -- Resolution: Duplicate > 'ConsumerGroupCommand' performance optimization for old consumer

[jira] [Created] (KAFKA-6496) NAT and Kafka

Ronald van de Kuil created KAFKA-6496: - Summary: NAT and Kafka Key: KAFKA-6496 URL: https://issues.apache.org/jira/browse/KAFKA-6496 Project: Kafka Issue Type: Improvement Affects

[jira] [Created] (KAFKA-6495) Race condition when creating and deleting quickly topics may lead to metrics leak

Mickael Maison created KAFKA-6495: - Summary: Race condition when creating and deleting quickly topics may lead to metrics leak Key: KAFKA-6495 URL: https://issues.apache.org/jira/browse/KAFKA-6495

[jira] [Created] (KAFKA-6494) Extend ConfigCommand to update broker config using new AdminClient

Rajini Sivaram created KAFKA-6494: - Summary: Extend ConfigCommand to update broker config using new AdminClient Key: KAFKA-6494 URL: https://issues.apache.org/jira/browse/KAFKA-6494 Project: Kafka

Build failed in Jenkins: kafka-trunk-jdk9 #341

See Changes: [wangguoz] MINOR: Optimize KTable-KTable join value getter supplier (#4458) -- [...truncated 1.74 MB...]