Looks like because we don't update the ephemeral metadata representation until the new state is persistent, we need to remember that we kicked off such a close. I'm a bit confused as to why asyncReadLastConfirmed only needs to check the LedgerMatadata.isClosed() method. Seems like it should be uniform -- all client calls fail once the LedgerHandle close process has begun -- in which case probably there should be a helper which wraps the closing || LedgerMatdata.isClosed() check.
[ Full content available at: https://github.com/apache/bookkeeper/pull/1646 ] This message was relayed via gitbox.apache.org for [email protected]
