Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

OpenSearch Dashboard is in red status after the upgrade process.

0

We upgraded our Elasticsearch cluster from 7.4 → 7.10 → OpenSearch 1.3. The upgrade shows “Upgrade from 7.10 to OpenSearch 1.3 succeeded with issues.” When we check eligibility for an upgrade to OpenSearch 2.19, we get, “All Kibana nodes are OOS in Elasticsearch. Please fix the issue and try again.”

We have tried:

  • Adding a new data node
  • Adding a coordinator node
  • Deleting .kibana* index during every upgrade step
  • Restarting the Kibana/OpenSearch Dashboard process from the console but none of those helped to solve this problem.

After that, somehow checking eligibility to upgrade to 2.19 was successful, and we upgraded it to OS 2.19. OpenSearch Dashboard stays in red status. We currently cannot access OpenSearch Dashboards, but other functions work fine. We need to know:

  • How can this dashboard issue be fixed?
  • If we can safely continue the use without fixing it in a short time, or if it may cause issues.
Topics
Analytics
Tags
Amazon OpenSearch Service
Language
English
asked 7 months ago219 views
1 Answer
0

Based on your description, you're experiencing issues with OpenSearch Dashboards after multiple version upgrades, with the dashboard showing a red status and being inaccessible even after upgrading to OpenSearch 2.19.

Here are some steps to fix the dashboard issue:

  1. Clear browser cache and cookies: Sometimes dashboard loading issues after an upgrade can be related to browser caching. Try clearing your browser cache and cookies completely before attempting to access the dashboard again.

  2. Restart the OpenSearch Dashboards process again: Even though you've already tried this, it's worth attempting once more after the final upgrade to 2.19:

  • Go to the OpenSearch Service console
  • Navigate to your domain and open the "Instance health" tab
  • Select the node running the Dashboards process (typically a coordinator node)
  • Choose "Actions" and select "Restart Dashboard/Kibana process"
  • Confirm the action and check the Events tab to monitor the restart status
  1. Check for configuration issues: The error "All Kibana nodes are OOS in Elasticsearch" suggests there might be compatibility issues between your dashboard configuration and the OpenSearch version. This could be related to custom plugins or settings that didn't migrate properly during the multiple upgrades.

Regarding continuing without fixing:

You can safely continue using other OpenSearch functions that are working correctly in the short term, as the dashboard issue doesn't necessarily affect the core functionality of your OpenSearch cluster for data indexing and searching operations. However, without access to the dashboard, you'll be limited in your ability to visualize data, create and manage visualizations, and use the dashboard's administrative features. This could become problematic for monitoring and managing your cluster over time.

If these steps don't resolve the issue, you may need to contact AWS Support for more in-depth assistance, as they can access more detailed information about your OpenSearch Service setup and help diagnose any underlying problems that might not be immediately apparent.
Sources
OpenSearch not loading dashboards after version upgrade | AWS re:Post
Restarting the OpenSearch Dashboards process on a node in Amazon OpenSearch Service - Amazon OpenSearch Service

answered 7 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content