-
Notifications
You must be signed in to change notification settings - Fork 588
HDDS-8411. Show the total number of CLOSING, QUASI_CLOSED, CLOSED, DELETING Containers in Recon #4591
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HDDS-8411. Show the total number of CLOSING, QUASI_CLOSED, CLOSED, DELETING Containers in Recon #4591
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -109,6 +109,22 @@ public Response getClusterState() { | |
| this.containerManager.getContainerStateCount( | ||
| HddsProtos.LifeCycleState.OPEN)); | ||
|
|
||
| containerStateCounts.setClosingContainersCount( | ||
| this.containerManager.getContainerStateCount( | ||
| HddsProtos.LifeCycleState.CLOSING)); | ||
|
|
||
| containerStateCounts.setQuasiClosedContainersCount( | ||
| this.containerManager.getContainerStateCount( | ||
| HddsProtos.LifeCycleState.QUASI_CLOSED)); | ||
|
|
||
| containerStateCounts.setClosedContainersCount( | ||
| this.containerManager.getContainerStateCount( | ||
| HddsProtos.LifeCycleState.CLOSED)); | ||
|
|
||
| containerStateCounts.setDeletingContainersCount( | ||
| this.containerManager.getContainerStateCount( | ||
| HddsProtos.LifeCycleState.DELETING)); | ||
|
|
||
| containerStateCounts.setDeletedContainersCount( | ||
| this.containerManager.getContainerStateCount( | ||
| HddsProtos.LifeCycleState.DELETED)); | ||
|
|
@@ -180,6 +196,12 @@ public Response getClusterState() { | |
| .setTotalDatanodes(datanodeDetails.size()) | ||
| .setHealthyDatanodes(healthyDatanodes) | ||
| .setOpenContainers(containerStateCounts.getOpenContainersCount()) | ||
| .setClosingContainers(containerStateCounts.getClosingContainersCount()) | ||
| .setQuasiClosedContainers( | ||
| containerStateCounts.getQuasiClosedContainersCount()) | ||
| .setClosedContainers(containerStateCounts.getClosedContainersCount()) | ||
| .setDeletingContainers( | ||
| containerStateCounts.getDeletingContainersCount()) | ||
| .setDeletedContainers(containerStateCounts.getDeletedContainersCount()) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This might be duplicate of PR for HDDS-8127
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Deleted Container and Deleting container shows different info ... and not to be excluded from container count. Only Deleted Container needs to be excluded, |
||
| .build(); | ||
| return Response.ok(response).build(); | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This may not be needed, as difference of total and open will give us closed container count. Rest all information on container states can be easily found out using Ozone admin CLI because we don't want to expose the transitioning container states to other users, and should be exposed to Admin users only.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @devmadhuu
@sumitagrawl has suggested that we include additional states in our state counts, such as close, closing, and quasi_closed. The state closing is especially important and can provide valuable insights into the situation being analyzed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ArafatKhan2198 , these state transitions are too dynamic and quick, let's discuss this, not sure if in so dynamic transitions, if it is really useful for admins. Moreover these are directly queried using admin CLI, so better we should avoid such data and load recon
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also closed is not needed because it can be derived from difference
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO, Quasi-Closed can be important state having special meaning. Also Closing / Deleting if stuck can be identified easily from this perspective.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes in normal scenarios transition will be quick, but have seen large number of containers stuck and remaining in Closing state in some scenarios. So should be useful for analyzing, if easily visible. But we should be careful of cluttering overview page and should have at appropriate place.