You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/02/27 07:48:24 UTC

[GitHub] [pulsar] eolivelli commented on issue #12556: Permanent namespace corruption after attempting to delete a namespace shortly after it was created and after all contained topics were deleted; broker log of "MetadataNotFoundException: Managed ledger not found"

eolivelli commented on issue #12556:
URL: https://github.com/apache/pulsar/issues/12556#issuecomment-1053314167


   In a system that is not under heavy load on metadata the local caches should be updated in a timely manner.
   If the system does not converge to a consistent view over metadata then we have some bugs.
   We recently found a problem on the usage of Caffeine in the local metadata cache.
   
   The alternative is to switch to a distributed local cache that guarantees causal consistency for the near caches, that is, when I write to the cache and the write returns I am sure that every local copy in each near cache is invalidated (or updated).
   
   Some years ago I worked on this project to solve this problem https://github.com/diennea/blazingcache
   It implements a very lightweight cache with near caching support and strong guarantees about causal consistency. Because we really needed to have such guarantees of distributed cache invalidation.


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org