sh Venkatraman
> Sent: Monday, March 25, 2019 10:49 AM
> To: dev@samza.apache.org
> Subject: Re: Empty Kafka topic partition Warning
>
> Hi Jeremiah,
>
> >> It looks like my configuration for changelog.replication.factor is not
> being applied. Instead the def
kedIn
From: Jagadish Venkatraman
Sent: Monday, March 25, 2019 10:49 AM
To: dev@samza.apache.org
Subject: Re: Empty Kafka topic partition Warning
Hi Jeremiah,
>> It looks like my configuration for changelog.replication.factor is not
being applied. Instead the default seems to be appl
nkedIn
>
> ________
> From: Jagadish Venkatraman
> Sent: Friday, March 22, 2019 3:01 PM
> To: dev@samza.apache.org
> Subject: Re: Empty Kafka topic partition Warning
>
> Hi Jeremiah,
>
> >> why is the offset 0?
>
> This lik
, March 22, 2019 3:01 PM
To: dev@samza.apache.org
Subject: Re: Empty Kafka topic partition Warning
Hi Jeremiah,
>> why is the offset 0?
This likely means that the change-log is empty and does not have any
messages.
Can you try consuming from partition-number: 0 using a KafkaConsumer?
Hi Jeremiah,
>> why is the offset 0?
This likely means that the change-log is empty and does not have any
messages.
Can you try consuming from partition-number: 0 using a KafkaConsumer?
Best,
Jagadish
On Fri, Mar 22, 2019 at 11:45 AM Jeremiah Adams
wrote:
> I'm seeing these in our log pe
I'm seeing these in our log periodically and havn't seen them before. Does
this imply that the topic associated with the change log is being replayed from
the beginning?
Also, why is the offset 0? It definitely should not be. We have messages across
all partitions.
2019-03-22 18:30:24 Kafka
