Re: mirror whitelist

Hi, I think the "" where the culprit, when removing "" it works On Sat, 25 Jul 2020 at 10:22, Dumitru-Nicolae Marasoui < nicolae.maras...@kaluza.com> wrote: > Hello kafka community, > > Doing the following cli command to copy messages from one cluster to > another, without any transformation on

Re: 409 incompatible schema (after delete subject with permanent=true)

Hello kafka community, So the schema that the kafka streams is trying to push into the registry is this: { "type" : "record", "name" : "AccountKey", "namespace" : "...", "fields" : [ { "name" : "accountId", "type" : "string", } ] } I removed it: curl -X DELETE

409 incompatible schema (after delete subject with permanent=true)

Hello kafka community, I am getting exception [1] even if i previously remove the culprit subject: curl -X DELETE 'http://localhost:8081/subjects/global_account_v1-key' [1] curl -X DELETE ' http://localhost:8081/subjects/global_account_v1-key?permanent=true' [1] Exception received:

Re: [VOTE] 2.5.1 RC0

+1 (binding), verified signatures, ran the tests on the source archive with Scala 2.13 and Java 11 and verified the quickstart with the source archive and Scala 2.13 binary archive. Ismael On Thu, Jul 23, 2020 at 7:39 PM John Roesler wrote: > Hello Kafka users, developers and

Re: Sharing of State Stores

Hi Charles, Two transformers that share the same state store should end up into the same sub-topology. A sub-topology is executed by as many task as the number of partitions of the input topics. Each task processes the records from one input partition group (i.e. the same partition from both

Re: [VOTE] 2.5.1 RC0

Hello again all, Just a reminder that the 2.5.1 RC0 is available for verification. Thanks, John On Thu, Jul 23, 2020, at 21:39, John Roesler wrote: > Hello Kafka users, developers and client-developers, > > This is the first candidate for release of Apache Kafka 2.5.1. > > Apache Kafka 2.5.1

Follower node receiving records out of order

Hi, We are expanding a 3-node cluster to a 5-node cluster, and have encountered an issue where a follower node is fetching offsets out of order. We are on 2.4.0. We've used the kafka-reassign-partitions tool. Several partitions are affected. Picking an example partition (11), it was configured

Kafka Active Active with MMK2

Hi All, Assume I am using the latest version + mmk2. Let's say I have 3 data centers with high latency between them >~10ms Can I use the mmk2 between them to maintain active active or, mmk2 can only be used between 2 data centers ? Thanks in advanced, Dor This email and the information

Re: Partition assignment not well distributed over threads

Hey Sophie, This was indeed the issue. An environment variable got passed through wrong. Thank you for your tip that made me check this. Giselle On 2020/07/29 17:41:43, Sophie Blee-Goldman wrote: > Hey Giselle, > > How many stream threads is each instance configured with? If the total >