zymap commented on code in PR #17228:
URL: https://github.com/apache/pulsar/pull/17228#discussion_r970567887
##########
managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/ManagedLedgerImpl.java:
##########
@@ -2357,6 +2357,42 @@ private void
maybeOffloadInBackground(CompletableFuture<PositionImpl> promise) {
}
}
+ // Although we have caught the connection loss exception on the meta
store, to avoid other exceptions cause
+ // the mismatch between meta store and in memory, we refresh the ledger
info list when the offload execute
+ // failed by badversion
+ private void asyncRefreshLedgersInfoOnBadVersion(ManagedLedgerException
exception) {
+ if (!(exception instanceof BadVersionException)) {
+ return;
+ }
+ if (!metadataMutex.tryLock()) {
+ scheduledExecutor.schedule(
+ () -> asyncRefreshLedgersInfoOnBadVersion(exception), 100,
TimeUnit.MILLISECONDS);
+ return;
+ }
+ store.getManagedLedgerInfo(name, false, new MetaStoreCallback<>() {
+ @Override
+ public void operationComplete(ManagedLedgerInfo mlInfo, Stat stat)
{
+ ledgersStat = stat;
+ try {
+ synchronized (ManagedLedgerImpl.this) {
Review Comment:
Because when we use metadataMutex, we are trying to lock it, I think it
won't cause a deadlock?
When we lock the metadataMutex, I saw all other places will retry. It won't
update the ledgers or metadata successfully. Then it has to wait for the
refresh done and then do other things.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
