GitHub user adarshhm6 edited a comment on the discussion: deduplicationStatus failed for one of the partition of the topic
Thank you for the response @BewareMyPower > As you can see, the `readPosition` is 147505614:682, while this ledger has > 1045 entries. It means the step 2 is interrupted, typically by an exception > throwing in the callback: I believe you meant the ledger has 1060 entries because 1045 entries were present in ledger 146914057 and not in 47505614. ledgerId is different for markDeletePosition and readPosition And mark-delete position 146914057:-1 --> This ledger has 1045 entries and -1 specifies no messages has been read and acknowledged yet. And as you mentioned "readPosition" : "147505614:682" points to some exception in between and got interrupted as this ledger has 1060 entries. You also mentioned since waitingReadOp is false, it is not blocked for reading entries, **so why the entries were not read completely if it's not blocked.** ? Since you mentioned your PR - [#24511 ](https://github.com/apache/pulsar/pull/24511) will fix these issues(deDuplication failures will be avoided completely and will it be successful?) and can be backported but your next statement was confusing and contradictory. Please suggest on that. GitHub link: https://github.com/apache/pulsar/discussions/24558#discussioncomment-14018738 ---- This is an automatically sent email for commits@pulsar.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@pulsar.apache.org
