Let me answer each question though most of them were already covered in the
previous reply.
>> Firstly, could you submit an issue that you encountered a ledger lost
issue, and we should solve the issue
There are multiple issues already created about the missing schema ledgers
and that could happe
Hi dev, I proposed a PIP: https://github.com/apache/pulsar/pull/23427, this pip
is intended to fix issue https://github.com/apache/pulsar/issues/23239.
Please take a look and give your feedback.
Best Regards!
Jiawen Wang
Hi, pulsar-dev community,
I’ve opened a PIP to discuss : PIP-380: Support setting up specific namespaces
to skipping the load-shedding.
PIP link: https://github.com/apache/pulsar/pull/23304
Thanks,
Kai
I'm glad you're concerned about the lost schema ledger.
Here are some of the fixes I tried for lost schema ledger:
https://github.com/apache/pulsar/issues/20414
https://github.com/apache/pulsar/pull/20415
And the previous related discussions.
https://lists.apache.org/thread/zbkpypb1yw89op510f7zg7
Makes sense, just wondering if the behavior should only be enabled when
config.isSchemaLedgerForceRecovery() == true (PIP-327)?
-Lari
On 2024/10/09 04:51:23 Rajan Dhabalia wrote:
> >> When the schemas of a topic are lost, all of the messages in the topic
> can not be consumed successfully, and p
Hi Rajan
> Therefore, this PR is important to make sure
> tenants don't face topic
> unavailability due to well known issues of
> missing schema ledgers.
Firstly, could you submit an issue that you encountered a ledger lost
issue, and we should solve the issue
Secondly, the ledger containing user
Hi Baodi
> Additionally, if a consumer is already
> using schema ID 1: `Int32`,
> consuming the M3(id:1 `String`) message
> will get an error, right?
Correct
On Wed, Oct 9, 2024 at 11:42 AM Baodi Shi wrote:
> +1 Additionally, if a consumer is already using schema ID 1: `Int32`,
> consuming the
