As I pointed, the style 'create a ledger and record the ledger id in some other places' is bad, especially changing ledger would cause 2 metadata writes and it is in the publish path, which caused latency spike (the latency spike depends on the two metadata writes latency). The reason why I proposed using 'ledger name', 're-open' and 'shrink', is trying to remove any metadata accesses during publishes. Removing metadata accessing means you could not change ledgers, a better way to do that is to 'shrink' a ledger.
-Sijie On Thu, Jan 17, 2013 at 7:26 AM, Ivan Kelly <[email protected]> wrote: > Also, I don't think the shrink operation is necessary. The aim here is > to avoid the metadata spike, yes? If so, we can still roll the ledger > when it gets to a certain capacity, and this is unlikely to happen on > a spike. >
