Build failed in Jenkins: kafka-2.1-jdk8 #75

See Changes: [jason] KAFKA-6388; Recover from rolling an empty segment that already exists -- [...truncated 909.88 KB...] kafka.coordinator.transaction.TransactionCoordinatorT

Re: [VOTE] KIP-228 Negative record timestamp support

I may be missing something, but why are we using an attribute for this? IIRC, we normally bump protocol version to indicate semantic changes. If I understand correctly, not using an attribute will allow us to not change the message format (just the protocol), which makes the upgrade significantly e

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

See

Re: [VOTE] KIP-228 Negative record timestamp support

Bump up on this thread again: we have two binding votes already and need another committer to take a look at it and vote. Guozhang On Fri, Oct 19, 2018 at 11:34 AM Konstantin Chukhlomin wrote: > bump > > On Tue, Jun 12, 2018 at 1:48 PM Bill Bejeck wrote: > > > +1 > > > > Thanks, > > Bill > >

Jenkins build is back to normal : kafka-2.1-jdk8 #74

See

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

See

Jenkins build is back to normal : kafka-1.1-jdk7 #236

See

Re: [VOTE] KIP-345: Introduce static membership protocol to reduce consumer rebalances

+1 (non-binding) Thanks, Mayuresh On Tue, Dec 4, 2018 at 6:58 AM Mike Freyberger wrote: > +1 (non binding) > > On 12/4/18, 9:43 AM, "Patrick Williams" > wrote: > > Pls take me off this VOTE list > > Best, > > Patrick Williams > > Sales Manager, UK & Ireland, Nordics & Israel

[jira] [Created] (KAFKA-7710) Poor Zookeeper ACL management with Kerberos

Mr Kafka created KAFKA-7710: --- Summary: Poor Zookeeper ACL management with Kerberos Key: KAFKA-7710 URL: https://issues.apache.org/jira/browse/KAFKA-7710 Project: Kafka Issue Type: Bug R

Build failed in Jenkins: kafka-0.11.0-jdk7 #410

See Changes: [mjsax] KAFKA-7660: fix streams and Metrics memory leaks (#5983) -- [...truncated 1.55 MB...] org.apache.kafka.streams.kstream.internals.KGroupedStreamImplTes

Re: [DISCUSS] KIP-399: Extend ProductionExceptionHandler to cover serialization exceptions

Matt, That's a good point. If these cases are handled in the serializer, then one cannot continue the stream processing by skipping the record. To continue, you may have to send a empty record serialized key/value (new byte[0]) to the downstream on hitting the error which may cause un-intended

Kafka 1.1.0 no longer available for download?

It looks like 1.1.0 is no longer available at https://www.apache.org/dist/kafka/ Is this intentional? While we'd like to upgrade, losing this version broke our CI today (and upgrading Kafka is always a process we undertake with care). --dave

Re: Kafka 1.1.0 no longer available for download?

Aha, I see that this is normal for old versions because they are on 'archive' only. One note: on https://kafka.apache.org/downloads the release notes link for 1.1.0 should point to archive (it does for older ones that need to be). On Wed, Dec 5, 2018 at 2:12 PM David Glasser wrote: > It looks l

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

See Changes: [me] MINOR: Safe string conversion to avoid NPEs -- [...truncated 4.48 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldFailIfValueIsDifferen

Build failed in Jenkins: kafka-2.0-jdk8 #200

See Changes: [jason] KAFKA-6388; Recover from rolling an empty segment that already exists -- [...truncated 434.01 KB...] kafka.controller.PartitionStateMachineTest > testI

[jira] [Resolved] (KAFKA-7673) Upgrade RocksDB to include fix for WinEnvIO::GetSectorSize

[ https://issues.apache.org/jira/browse/KAFKA-7673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7673. -- Resolution: Fixed Assignee: Guozhang Wang [~yanicks] we've merged https://github.com/apac

Re: Vote for KIP-393 (Fix time windowed serde to deserialize changelog topic)

Hello Shawn, Thanks for the writeup. I've made a pass over it and here are some minor comments: 1) As we discussed in the PR: https://github.com/apache/kafka/pull/5307, the public APIs that we will add is In WindowedSerdes: ``` static public Serde> timeWindowedChangelogSerdeFrom(final Class typ

Build failed in Jenkins: kafka-1.1-jdk7 #235

See Changes: [matthias] KAFKA-7678: Avoid NPE when closing the RecordCollector (#5993) -- [...truncated 424.83 KB...] kafka.utils.json.JsonValueTest > testDecodeMap PASSED k

Build failed in Jenkins: kafka-2.0-jdk8 #199

See Changes: [matthias] KAFKA-7678: Avoid NPE when closing the RecordCollector (#5993) -- [...truncated 435.18 KB...] kafka.controller.PartitionStateMachineTest > testInval

[jira] [Resolved] (KAFKA-6388) Error while trying to roll a segment that already exists

[ https://issues.apache.org/jira/browse/KAFKA-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6388. Resolution: Fixed Fix Version/s: 2.0.2 2.1.1 > Error while trying

Build failed in Jenkins: kafka-2.0-jdk8 #198

See Changes: [me] MINOR: Safe string conversion to avoid NPEs -- [...truncated 438.71 KB...] kafka.utils.SchedulerTest > testRestart STARTED kafka.utils.SchedulerTest > tes

Build failed in Jenkins: kafka-2.1-jdk8 #73

See Changes: [matthias] KAFKA-7678: Avoid NPE when closing the RecordCollector (#5993) -- [...truncated 464.50 KB...] kafka.utils.ShutdownableThreadTest > testShutdownWhenCall

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

If they don't find the time: They usually take the opposite path from me :D so the answer would be clear. hence my suggestion to vote. On 04.12.2018 21:06, Adam Bellemare wrote: > Hi Guozhang and Matthias > > I know both of you are quite busy, but we've gotten this KIP to a point > where we need

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

See Changes: [mjsax] KAFKA-7420: Global store surrounded by read only implementation (#5865) [mjsax] KAFKA-7678: Avoid NPE when closing the RecordCollector (#5993) -- [..

Re: [VOTE] KIP-354 Time-based log compaction policy

Thanks for the update. +1 (binding) On Wed, Dec 5, 2018 at 8:19 AM Colin McCabe wrote: > Thanks, Xiongqi Wu. +1 (binding) > > regards, > Colin > > > On Tue, Dec 4, 2018, at 20:58, xiongqi (wesley) wu wrote: > > Colin, > > > > Thanks for comments. > > Out of ordered message timestamp is a very g

[jira] [Created] (KAFKA-7709) ConcurrentModificationException occurs when iterating through multiple partitions in Sender.getExpiredInflightBatches

Mark Cho created KAFKA-7709: --- Summary: ConcurrentModificationException occurs when iterating through multiple partitions in Sender.getExpiredInflightBatches Key: KAFKA-7709 URL: https://issues.apache.org/jira/browse/KAF

Re: [VOTE] KIP-394: Require member.id for initial join group request

+1 Thanks for the KIP. -Bill On Wed, Dec 5, 2018 at 1:43 PM Matthias J. Sax wrote: > Thanks for the KIP. > > +1 (binding) > > -Matthias > > > On 12/5/18 7:53 AM, Mayuresh Gharat wrote: > > +1 (non-binding) > > > > Thanks, > > > > Mayuresh > > > > > > On Wed, Dec 5, 2018 at 3:59 AM Boyang Chen

Re: Kafka Help

You will need to write a custom deserializer that is able to convert he `byte[]` of key and value into the desired Scala/Java object. Interface: org.apache.kafka.common.serialization.Deserializer You can provide your custom deserializer via config to console consumer and KafkaConsumer in your Sca

Re: [VOTE] KIP-394: Require member.id for initial join group request

Thanks for the KIP. +1 (binding) -Matthias On 12/5/18 7:53 AM, Mayuresh Gharat wrote: > +1 (non-binding) > > Thanks, > > Mayuresh > > > On Wed, Dec 5, 2018 at 3:59 AM Boyang Chen wrote: > >> Hey friends, >> >> I would like to start a vote for KIP-394< >> https://cwiki.apache.org/confluenc

RE: [DISCUSS] KIP-383 Pluggable interface for SSL Factory

I updated the KIP to keep reconfiguration in SslFactory and create a new SslEngineFactory interface public interface SslEngineFactory { void configure(Map configs, Mode mode); SSLEngine createSslEngine(String peerHost, int peerPort); } Please read the KIP and send your comments.

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

Sönke, > The only thing that I could come up with is the limitation to a single offset commit interval Yes, and other internal properties, e.g. those used by the internal consumers and producers, which, granted, probably are not often changed from their defaults, but that apply to Connectors acro

Kafka Help

Dear Team, I want to convert the c++ struct data. I have the data which is send from tcp port to kafka using c++ ,so the data in kafka topic is in c++ struct format. I am not able to print that struct data on console and not able to streaming that data using scala. Could you help me how to solve

Re: [VOTE] KIP-354 Time-based log compaction policy

Thanks, Xiongqi Wu. +1 (binding) regards, Colin On Tue, Dec 4, 2018, at 20:58, xiongqi (wesley) wu wrote: > Colin, > > Thanks for comments. > Out of ordered message timestamp is a very good point. > We can combine max.compaction.lag.ms with > log.message.timestamp.difference.max.ms to achieve

Vote for KIP-393 (Fix time windowed serde to deserialize changelog topic)

Hey all, I wanted to start a vote on approval of KIP-393 to fix the current time windowed serde for properly deserializing changelog input topics. Let me know what you g

Re: [VOTE] KIP-394: Require member.id for initial join group request

+1 (non-binding) Thanks, Mayuresh On Wed, Dec 5, 2018 at 3:59 AM Boyang Chen wrote: > Hey friends, > > I would like to start a vote for KIP-394< > https://cwiki.apache.org/confluence/display/KAFKA/KIP-394%3A+Require+member.id+for+initial+join+group+request>. > The goal of this KIP is to impro

Re: [DISCUSS] KIP-394: Require member.id for initial join group request

Thanks for the KIP Boyang and great to see the progress on solving the rebalance issues with this and KIP-345. Thanks, Mayuresh On Mon, Dec 3, 2018 at 4:57 AM Stanislav Kozlovski wrote: > Everything sounds good to me. > > On Sun, Dec 2, 2018 at 1:24 PM Boyang Chen wrote: > > > In fact, it's p

[jira] [Created] (KAFKA-7708) [kafka-streams-scala] Invalid signature for KTable join in 2.12

Edmondo Porcu created KAFKA-7708: Summary: [kafka-streams-scala] Invalid signature for KTable join in 2.12 Key: KAFKA-7708 URL: https://issues.apache.org/jira/browse/KAFKA-7708 Project: Kafka

Re: [DISCUSS] KIP-399: Extend ProductionExceptionHandler to cover serialization exceptions

Hi there, Thanks for this KIP. What’s the thinking behind doing this in ProductionExceptionHandler versus handling these cases in your serializer implementation? On Mon, Dec 3, 2018 at 1:09 AM Kamal Chandraprakash < kamal.chandraprak...@gmail.com> wrote: > Hello dev, > > I hope to initiate th

[jira] [Resolved] (KAFKA-7697) Possible deadlock in kafka.cluster.Partition

[ https://issues.apache.org/jira/browse/KAFKA-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-7697. --- Resolution: Fixed Reviewer: Jason Gustafson > Possible deadlock in kafka.cluster.Partit

Re: [Discuss] KIP-389: Enforce group.max.size to cap member metadata growth

Hey Stanislav, thanks for the question! `Trivial rebalance` means "we don't start reassignment right now, but you need to know it's coming soon and you should start preparation". An example KStream use case is that before actually starting to shrink the consumer group, we need to 1. partition t

[VOTE] KIP-394: Require member.id for initial join group request

Hey friends, I would like to start a vote for KIP-394. The goal of this KIP is to improve broker stability by fencing invalid join group requests. Best, Boyang

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

See Changes: [github] KAFKA-7697: Process DelayedFetch without holding leaderIsrUpdateLock -- [...truncated 2.24 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Problem with Kafka Connector

Hello! I have question. We have cluster with several connect workers. And we have many different connectors. We need to set for each connector its own settings, max.in.flight.requests.per.connection , partitioner.class, acks. But I have difficulties. How can I do that? Thanks

[jira] [Created] (KAFKA-7707) Some code is not necessary

huangyiming created KAFKA-7707: -- Summary: Some code is not necessary Key: KAFKA-7707 URL: https://issues.apache.org/jira/browse/KAFKA-7707 Project: Kafka Issue Type: Improvement Repo

Re: [Discuss] KIP-389: Enforce group.max.size to cap member metadata growth

Hey Boyang, I think we still need to take care of group shrinkage because even if users change the config value we cannot guarantee that all consumer groups would have been manually shrunk. Regarding 2., I agree that forcefully triggering a rebalance might be the most intuitive way to handle the

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

Hi Ryanne, when you say "Currently worker configs apply across the entire cluster, which is limiting even for use-cases involving a single Kafka cluster.", may I ask you to elaborate on those limitations a little? The only thing that I could come up with is the limitation to a single offset commit

[jira] [Created] (KAFKA-7706) Spotbugs task fails with Gradle 5.0

FuQiao Wang created KAFKA-7706: -- Summary: Spotbugs task fails with Gradle 5.0 Key: KAFKA-7706 URL: https://issues.apache.org/jira/browse/KAFKA-7706 Project: Kafka Issue Type: Bug Compo