Skip to content
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

Improved cat help description #14771

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

landon-lengyel
Copy link

Description

The _cat API's help returns (in part) the following:
Header | Description
memory.total | total used memory
pri.memory.total | total user memory

The word 'user' is almost certainly a typo. However, I also strongly suspect that this is total used memory for primary shards and that should be explained more clearly.

Related Issues

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Landon Lengyel [email protected]

Copy link
Contributor

❌ Gradle check result for b66562a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@landon-lengyel
Copy link
Author

The Gradle failure doesn't appear to be related to my change.
Let me know if I've submitted this in the wrong way or something.

@kotwanikunal
Copy link
Member

Thanks for your contribution @landon-lengyel! Let me take care of the workflows.

@@ -694,8 +694,8 @@ protected Table getTableWithHeader(final RestRequest request) {
table.addCell("suggest.total", "sibling:pri;alias:suto,suggestTotal;default:false;text-align:right;desc:number of suggest ops");
table.addCell("pri.suggest.total", "default:false;text-align:right;desc:number of suggest ops");

table.addCell("memory.total", "sibling:pri;alias:tm,memoryTotal;default:false;text-align:right;desc:total used memory");
table.addCell("pri.memory.total", "default:false;text-align:right;desc:total user memory");
table.addCell("memory.total", "sibling:pri;alias:tm,memoryTotal;default:false;text-align:right;desc:total used memory of primaries & replicas");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@reta Does this seem accurate to you?

Copy link
Collaborator

@reta reta Jul 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kotwanikunal I think the pri.* prefix generally reflects primary, so it looks accurate but not complete, we have many other columns which probably have to be documented in a similar fashion, not only *memory*

@kotwanikunal
Copy link
Member

@landon-lengyel You missed signing off on your commit. Can you please follow the process here to correct it?
https://github.com/opensearch-project/OpenSearch/actions/runs/9959735699/job/27575301784?pr=14771

@landon-lengyel
Copy link
Author

@landon-lengyel You missed signing off on your commit. Can you please follow the process here to correct it? https://github.com/opensearch-project/OpenSearch/actions/runs/9959735699/job/27575301784?pr=14771

Okay I think I amended that correctly.
Apologies, git can be a little confusing when you don't regularly use it.

Copy link
Contributor

❌ Gradle check result for 782755c: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

❌ Gradle check result for 124c3fb: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@opensearch-trigger-bot
Copy link
Contributor

This PR is stalled because it has been open for 30 days with no activity.

@opensearch-trigger-bot opensearch-trigger-bot bot added the stalled Issues that have stalled label Aug 17, 2024
@opensearch-trigger-bot opensearch-trigger-bot bot removed the stalled Issues that have stalled label Sep 19, 2024
@opensearch-trigger-bot
Copy link
Contributor

This PR is stalled because it has been open for 30 days with no activity.

@opensearch-trigger-bot opensearch-trigger-bot bot added the stalled Issues that have stalled label Oct 27, 2024
@dblock
Copy link
Member

dblock commented Oct 30, 2024

@landon-lengyel @sandeshkr419 @reta let's finish this?

@opensearch-trigger-bot opensearch-trigger-bot bot removed the stalled Issues that have stalled label Oct 31, 2024
@sandeshkr419
Copy link
Contributor

@landon-lengyel Did you get a chance to check out the comments?

landon-lengyel and others added 2 commits December 2, 2024 14:23
…sAction.java

Co-authored-by: Andriy Redko <[email protected]>
Signed-off-by: Landon Lengyel <[email protected]>
…sAction.java

Co-authored-by: Andriy Redko <[email protected]>
Signed-off-by: Landon Lengyel <[email protected]>
@landon-lengyel
Copy link
Author

@sandeshkr419 LGTM. I approved the changes on this PR from @reta - thank you for adding those.

Is there anything else I can do for this PR?

@reta
Copy link
Collaborator

reta commented Dec 2, 2024

@sandeshkr419 LGTM. I approved the changes on this PR from @reta - thank you for adding those.

Thanks @landon-lengyel , so if you look on any other column out there, most of them have pri.* / total splits, for example:

       table.addCell("suggest.total", "sibling:pri;alias:suto,suggestTotal;default:false;text-align:right;desc:number of suggest ops");
       table.addCell("pri.suggest.total", "default:false;text-align:right;desc:number of suggest ops"); 
table.addCell("warmer.total", "sibling:pri;alias:wto,warmerTotal;default:false;text-align:right;desc:total warmer ops");
table.addCell("pri.warmer.total", "default:false;text-align:right;desc:total warmer ops");

(and many others). So if we want to accurately reflect the primary / primary + replicas, we should update all column descriptions, not only memory column. Does it make sense?

Thank you

@reta
Copy link
Collaborator

reta commented Dec 2, 2024

DCO check needs fixing sadly

@sandeshkr419
Copy link
Contributor

@landon-lengyel Re-iterating on what I mentioned in my comment and what @reta also seconded in his comment, it only makes sense to fix the typo user/used and not add total/primary details to keep it consistent with other descriptions already in place.

If required, a small line clarifying this on top of the help section might be a value addition instead of making this change at each row to keep the individual rows' description concise, and not at all for a single row (which brings up inconsistency).

Copy link
Contributor

github-actions bot commented Dec 2, 2024

❌ Gradle check result for 149eb3d:

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants