GitHub user adarshhm6 edited a discussion: deduplicationStatus failed for one
of the partition of the topic
Deduplication enabled at broker level using param brokerDeduplicationEnabled.
When checked for topic stats for 3 partitioned topic using
pulsar-admin topics stats persistent://{tenant}/{namespace}/topic-partition-{i}
2 partitions shows "deduplicationStatus" : "Enabled", while 1 partition shows
"deduplicationStatus" : "Failed"
As a result backlogSize increased on one topic partition alone.
Logs got rolled over and I do not have have any failure traces.
Pulsar version is 2.10
Is it a known case where deDup fail for only one partition and no other topics
under that broker gets impacted or faced any failures?
Please suggest.
GitHub link: https://github.com/apache/pulsar/discussions/24558
----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscr...@pulsar.apache.org
