-
Notifications
You must be signed in to change notification settings - Fork 67
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
Depreceate NodeStatsFixedShardsMetricsCollector in favor of NodeStatsAllShardsMetricsCollector #551
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 |
---|---|---|
|
@@ -34,7 +34,10 @@ | |
import org.opensearch.performanceanalyzer.util.Utils; | ||
|
||
/** | ||
* This collector collects metrics for fixed number of shards on a node in a single run. These | ||
* Note: 'NodeStatsAllShardsMetricsCollector' is already released and out of shadow mode, this class | ||
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. Any reason why we cannot remove this as part of current release? 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. Following the standard practice of marking the class deprecated in (n-1) release and finally removing in nth release. |
||
* can be deprecated/removed in future versions. | ||
* | ||
* <p>This collector collects metrics for fixed number of shards on a node in a single run. These | ||
* metrics are heavy which have performance impacts on the performance of the node. The number of | ||
* shards is set via a cluster settings api. The parameter to set is shardsPerCollection. The | ||
* metrics will be populated for these many shards in a single run. | ||
|
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.
Better not to reduce coverage percentage
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 agree, but in this case, the build on the repo depends on coverage verification and will fail now that we are ignoring the redundant
NodeStatsFixedShardsMetricsCollectorTests.java
.The coverage increase will have to be separately addressed from this PR.