You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under each Ledger we can see the EnsebleSize, WriteQuorumSize and AckQuorumSize config used to create the ledger, but we cannot see the CURRENT status of the ledger.
If a Ledger has been written to 2 bookies and 1 of the bookie is currently DOWN we should report a "undereplicated" warning.
The text was updated successfully, but these errors were encountered:
Please note that since BookKeeper 4.10 we could leverage the Cluster Consistency Checker to also check the actual consistency of the checked ledger. Based on the cost of this type of call we could decide to limitate the check by a specific button and/or only when the user open the detail page of a specific ledger
Under each Ledger we can see the EnsebleSize, WriteQuorumSize and AckQuorumSize config used to create the ledger, but we cannot see the CURRENT status of the ledger.
If a Ledger has been written to 2 bookies and 1 of the bookie is currently DOWN we should report a "undereplicated" warning.
The text was updated successfully, but these errors were encountered: