dlg99 opened a new pull request, #3713:
URL: https://github.com/apache/bookkeeper/pull/3713
cherry-pick of PR 3710, with minor conflicts resolved
Descriptions of the changes in this PR:
Information provided by current REST API is not enough (and cumbersome to
combine) to answer such question as "is any data in danger if I shut down one
more bookie". E.g. getting list of underreplicated ledgers can get some info
but it is either fast (no ledgers) or can be super slow on large cluster with
some bookies lost (it retrieves full list of ledgers). Even if there are no UR
ledgers it still possible that the problem is that Auditor is down etc.
Added api/v1/bookie/cluster_info REST API
```
curl -s 127.0.0.1:8080/api/v1/bookie/cluster_info
{
"auditorElected" : false,
"auditorId" : "",
"clusterUnderReplicated" : false,
"ledgerReplicationEnabled" : true,
"totalBookiesCount" : 1,
"writableBookiesCount" : 1,
"readonlyBookiesCount" : 0,
"unavailableBookiesCount" : 0
}%
```
Side-fix:
`org.apache.bookkeeper.stream.cluster.StandaloneStarter` (used by bookie
standalone) did not pass `LedgerManagerFactory` to the http server thus REST
calls that needed it didn't work.
Reviewers: Nicolò Boschi <[email protected]>, Enrico Olivelli
<[email protected]>
This closes #3710 from dlg99/rest-cluster-info
(cherry picked from commit 032aef7e75f6b3487a6611a2b8af8306b9a3f7bb)
--
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]
