Re: Mirror Maker 2 with different Avro Schema Registries

[andreasvdber...@avathar.be]

hi, 

I guess this would mean a deserialisation error, meaning he data you're trying 
to read, is not as expected by the Confluent Avro deserializer.

https://www.youtube.com/watch?v=GWBk9LIzy-A 




> On 29 Dec 2022, at 16:47, Дмитрий Лушников  wrote:
> 
> Anders, maybe you can help me?
> MirrorMaker 2 stops transfer messages after setting up Schema Registry
> Transfer SMT.
> 
> The logs show these errors:
> 
> Caused by: org.apache.kafka.common.errors.SerializationException:
> Unknown magic byte!
> 
> Caused by: 
> cricket.jmoore.confluent.kafka.schemaregistry.client.rest.exceptions.RestClientException:
> Schema 1 not found; error code: 40403
> 
> I can’t figure out what to do with the *magic byte* and who needed *Schema
> 1*?
> 
> https://stackoverflow.com/questions/74952744/mirrormaker-2-stops-transfer-messages-after-setting-up-schema-registry-transfer

Re: Kafka Stream: The state store, wkstore, may have migrated to another instance

[Matthias J. Sax]

Sounds like a SpringBoot issue rather than a KS issues.

-Matthias

On 12/29/22 2:45 AM, Nawal Sah wrote:

Hi,

My SpringBoot stream application works fine in a fresh start of the
clustered environment.
But when I restart one of the pods out of two pods, I start getting the
below exception from "KafkaStreams.store". I debugged the state but found
it was RUNNING.

*org.apache.kafka.streams.errors.InvalidStateStoreException: The state
store, wkstore, may have migrated to another instance.*
*at
org.apache.kafka.streams.state.internals.WrappingStoreProvider.stores(WrappingStoreProvider.java:67)
   *
*at
org.apache.kafka.streams.state.internals.CompositeReadOnlyWindowStore.fetchAll(CompositeReadOnlyWindowStore.java:175)*

To fix this, I must restart all the pods/instances or the cluster.

*Steps to reproduce*

1. Kafka Stream application environment
'kafka-streams', version: '3.0.1'
'kafka-clients', version: '3.0.1'
2. Create a cluster environment with at least two replication factors of
the Kafka Stream application.
3. Restart one of the pods.
4. Call KafkaStreams:store(), it starts throwing an exception. If not then
try at least 5 times to restart the same pod.

Priority: *Blocker*


*Regards,*

Nawal Sah

(M): +91-9717932863

Kafka Stream: The state store, wkstore, may have migrated to another instance

[Nawal Sah]

Hi,

My SpringBoot stream application works fine in a fresh start of the
clustered environment.
But when I restart one of the pods out of two pods, I start getting the
below exception from "KafkaStreams.store". I debugged the state but found
it was RUNNING.

*org.apache.kafka.streams.errors.InvalidStateStoreException: The state
store, wkstore, may have migrated to another instance.*
*at
org.apache.kafka.streams.state.internals.WrappingStoreProvider.stores(WrappingStoreProvider.java:67)
  *
*at
org.apache.kafka.streams.state.internals.CompositeReadOnlyWindowStore.fetchAll(CompositeReadOnlyWindowStore.java:175)*

To fix this, I must restart all the pods/instances or the cluster.

*Steps to reproduce*

1. Kafka Stream application environment
'kafka-streams', version: '3.0.1'
'kafka-clients', version: '3.0.1'
2. Create a cluster environment with at least two replication factors of
the Kafka Stream application.
3. Restart one of the pods.
4. Call KafkaStreams:store(), it starts throwing an exception. If not then
try at least 5 times to restart the same pod.

Priority: *Blocker*


*Regards,*

Nawal Sah

(M): +91-9717932863

Mirror Maker 2 with different Avro Schema Registries

[Дмитрий Лушников]

Anders, maybe you can help me?
MirrorMaker 2 stops transfer messages after setting up Schema Registry
Transfer SMT.

The logs show these errors:

Caused by: org.apache.kafka.common.errors.SerializationException:
Unknown magic byte!

Caused by: 
cricket.jmoore.confluent.kafka.schemaregistry.client.rest.exceptions.RestClientException:
Schema 1 not found; error code: 40403

I can’t figure out what to do with the *magic byte* and who needed *Schema
1*?

https://stackoverflow.com/questions/74952744/mirrormaker-2-stops-transfer-messages-after-setting-up-schema-registry-transfer

Re: [ANNOUNCE] New committer: Satish Duggana

[Bill Bejeck]

Congratulations Satish!

-Bill

On Thu, Dec 29, 2022 at 11:05 AM Satish Duggana 
wrote:

> Thank you, everyone!
>
> On Wed, 28 Dec 2022 at 00:02, Matthias J. Sax  wrote:
> >
> > Congrats!
> >
> > On 12/27/22 10:20 AM, Kirk True wrote:
> > > Congrats, Satish!
> > >
> > > On Fri, Dec 23, 2022, at 10:07 AM, Jun Rao wrote:
> > >> Hi, Everyone,
> > >>
> > >> The PMC of Apache Kafka is pleased to announce a new Kafka committer
> Satish
> > >> Duggana.
> > >>
> > >> Satish has been a long time Kafka contributor since 2017. He is the
> main
> > >> driver behind KIP-405 that integrates Kafka with remote storage, a
> > >> significant and much anticipated feature in Kafka.
> > >>
> > >> Congratulations, Satish!
> > >>
> > >> Thanks,
> > >>
> > >> Jun (on behalf of the Apache Kafka PMC)
> > >>
> > >
>

Re: [ANNOUNCE] New committer: Satish Duggana

[Satish Duggana]

Thank you, everyone!

On Wed, 28 Dec 2022 at 00:02, Matthias J. Sax  wrote:
>
> Congrats!
>
> On 12/27/22 10:20 AM, Kirk True wrote:
> > Congrats, Satish!
> >
> > On Fri, Dec 23, 2022, at 10:07 AM, Jun Rao wrote:
> >> Hi, Everyone,
> >>
> >> The PMC of Apache Kafka is pleased to announce a new Kafka committer Satish
> >> Duggana.
> >>
> >> Satish has been a long time Kafka contributor since 2017. He is the main
> >> driver behind KIP-405 that integrates Kafka with remote storage, a
> >> significant and much anticipated feature in Kafka.
> >>
> >> Congratulations, Satish!
> >>
> >> Thanks,
> >>
> >> Jun (on behalf of the Apache Kafka PMC)
> >>
> >