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

[BUG] SearchBackPressureRCA causing Gauntlet test failure #503

Closed
khushbr opened this issue Oct 5, 2023 · 2 comments
Closed

[BUG] SearchBackPressureRCA causing Gauntlet test failure #503

khushbr opened this issue Oct 5, 2023 · 2 comments
Assignees
Labels
bug Something isn't working v2.11.0 Issues targeting release v2.11.0

Comments

@khushbr
Copy link
Collaborator

khushbr commented Oct 5, 2023

What is the bug?
SearchBackPressureRCA causing Gauntlet test failure. refer: https://github.com/opensearch-project/performance-analyzer-rca/actions/runs/6385777195/job/17331223490

 The Runner found the following errors in log: [
  00:20:20.398 [ELECTED_CLUSTER_MANAGER-task-1-] ERROR SearchBackPressureRCA:getHeapStats()::line:403 - Failed to parse metric in FlowUnit from org.opensearch.performanceanalyzer.rca.framework.api.metrics.Heap_Used
  00:20:20.480 [DATA_0-task-1-] ERROR SearchBackPressureRCA:getHeapStats()::line:403 - Failed to parse metric in FlowUnit from org.opensearch.performanceanalyzer.rca.framework.api.metrics.Heap_Used
  00:20:25.402 [ELECTED_CLUSTER_MANAGER-task-1-] ERROR SearchBackPressureRCA:getHeapStats()::line:403 - Failed to parse metric in FlowUnit from org.opensearch.performanceanalyzer.rca.framework.api.metrics.Heap_Used
  00:20:25.488 [DATA_0-task-0-] ERROR SearchBackPressureRCA:getHeapStats()::line:403 - Failed to parse metric in FlowUnit from org.opensearch.performanceanalyzer.rca.framework.api.metrics.Heap_Used

The search backpressure metrics on PA end are:

1696544030000:{"searchbp_shard_stats_cancellationCount":0,"searchbp_shard_stats_limitReachedCount":0,"searchbp_shard_stats_resource_heap_usage_cancellationCount":0,"searchbp_shard_stats_resource_heap_usage_currentMax":0,"searchbp_shard_stats_resource_heap_usage_rollingAvg":0,"searchbp_shard_stats_resource_cpu_usage_cancellationCount":0,"searchbp_shard_stats_resource_cpu_usage_currentMax":0,"searchbp_shard_stats_resource_cpu_usage_currentAvg":0,"searchbp_shard_stats_resource_elaspedtime_usage_cancellationCount":0,"searchbp_shard_stats_resource_elaspedtime_usage_currentMax":0,"searchbp_shard_stats_resource_elaspedtime_usage_currentAvg":0,"searchbp_task_stats_cancellationCount":0,"searchbp_task_stats_limitReachedCount":0,"searchbp_task_stats_resource_heap_usage_cancellationCount":0,"searchbp_task_stats_resource_heap_usage_currentMax":0,"searchbp_task_stats_resource_heap_usage_rollingAvg":0,"searchbp_task_stats_resource_cpu_usage_cancellationCount":0,"searchbp_task_stats_resource_cpu_usage_currentMax":0,"searchbp_task_stats_resource_cpu_usage_currentAvg":0,"searchbp_task_stats_resource_elaspedtime_usage_cancellationCount":0,"searchbp_task_stats_resource_elaspedtime_usage_currentMax":0,"searchbp_task_stats_resource_elaspedtime_usage_currentAvg":0,"searchbp_mode":"MONITOR_ONLY","searchbp_nodeid":"lGFg--rtQ1CRMVK_x8SWmA"}$

Do you have any additional context?
Add any other context about the problem.

@khushbr khushbr added bug Something isn't working untriaged labels Oct 5, 2023
@khushbr khushbr added the v2.11.0 Issues targeting release v2.11.0 label Oct 5, 2023
@khushbr
Copy link
Collaborator Author

khushbr commented Oct 5, 2023

ThegetHeapStats method is failing to parse the metrics:

@khushbr
Copy link
Collaborator Author

khushbr commented Oct 10, 2023

The SBP changes have been reverted and the gauntlet tests are now passing. This is blocked by availability of opensearch-project/OpenSearch#10028

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v2.11.0 Issues targeting release v2.11.0
Projects
None yet
Development

No branches or pull requests

2 participants