-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HDDS-1146. Adding container related metrics in SCM. #1541
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
Conversation
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.
+1, there is a minor comment. Feel free to commit once you get a CI run.
* @param isFullReport | ||
* @param success | ||
*/ | ||
void notifyContainerReportProcessing(boolean isFullReport, boolean success); |
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.
I am not sure, But I think we have a Enum that indicates if the report is full or partial. If there is already one, then we might want to use it. Otherwise, I am okay with the boolean.
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.
From proto, there is no enum. But i see we have TypedEvent
TypedEvent
INCREMENTAL_CONTAINER_REPORT = new TypedEvent<>(
IncrementalContainerReportFromDatanode.class,
"Incremental_Container_Report")
TypedEvent CONTAINER_REPORT =
new TypedEvent<>(ContainerReportFromDatanode.class, "Container_Report");
Do you mean we want to use them instead of boolean?
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
@bharatviswa504 If you don't mind, can you tell me where a metric like numContainerReportsSuccess would be useful? Failures I guess may be useful. |
LOG.error("Exception while processing ICR for container {}", | ||
replicaProto.getContainerID()); | ||
} | ||
} | ||
|
||
if (success) { | ||
getContainerManager().notifyContainerReportProcessing(false, true); | ||
} else { |
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.
Any reason we are not doing getContainerManager().notifyContainerReportProcessing(false, success) ?
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.
We can do that, just due to copy/paste from ICR code it is like this. (End result is same)
Let me know if you want to change it?
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, we should change it to 1 line instead of if-else.
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.
As discussed offline, will change this in later jira. For now we shall go with the current way.
If the user wants to know numContainerReportsProcessed successfully in system. And he wants to compare with failure count, then it might be useful. And also I got to know yesterday it would be good to have metrics in the system for some actions happened/performed. |
Test failures are not related to this patch. |
No description provided.