Hi Penghui & Asaf:
Please allow me to provide some more detailes about **metadata**
synchronization
between source topic and shadow topic.
1.When shadow topic initializes, it will read from metadata store path
"/managed-ledgers/{source_topic_ledger_name}", which contains all the managed
ledger info. We don't
need to read the ledger information from source topic broker.
2. When shadow topic received new message from replicator, if the ledger id of
the message
is the same as the last ledger, it just updates the LAC. If not, it will
update ledger list from metadata,
and then open the new ledger handle and update the LAC.
As for the copy itself and add shadow message id in CommandSend, it mostly
serves the purpose
of filling the EntryCache.
Thanks,
Haiting
On 2022/06/23 02:08:46 PengHui Li wrote:
> > One question comes to mind here: Why not simply read the ledger information
> from original topic, without copy?
>
> I think this is a good idea.
>
> Penghui
> On Jun 22, 2022, 23:57 +0800, dev@pulsar.apache.org, wrote:
> >
> > One question comes to mind here: Why not simply read the ledger information
> > from original topic, without copy?
>
