SAP Knowledge Base Article - Preview

2839319 - Elasticsearch validation failed during upgrade, not healthy - SAP Data Hub

Symptom

SAP Data Hub upgrade from 2.5.x to 2.6.x fails with:

  1. [ERROR] Failed! Please see the validation logs

  2. diagnostics-elasticsearch-0 pod is in crash loop 

  3. kubectl describe pod diagnostics-elasticsearch-0 shows:

Warning FailedPostStartHook [...] failed - error: command '/bin/sh -c python /script/elasticsearch_configurator.py' exited with 1: , message: "Exit: Failed to run Elasticsearch configurator: Failed to run Elasticsearch configurator after 170.30376792s (timeout: 180s, backoff interval 10s): Failed to configure elasticsearch: Elasticsearch not healthy, health information: {u'status': u'yellow', u'number_of_nodes': 1, u'unassigned_shards': 10, u'number_of_pending_tasks': 0, u'number_of_in_flight_fetch': 0, u'timed_out': False, u'active_primary_shards': 13, u'task_max_waiting_in_queue_millis': 0, u'cluster_name': u'diagnostics-elasticsearch', u'relocating_shards': 0, u'active_shards_percent_as_number': 56.52173913043478, u'active_shards': 13, u'initializing_shards': 0, u'number_of_data_nodes': 1, u'delayed_unassigned_shards': 0}\n"

Note the 'unassigned_shards': 10 in the printout of the health information


Read more...

Environment

SAP Data Hub (DH) 2.x

Product

SAP Data Hub 2.0

Keywords

DataHub, upgrade, validationfailes, unassigned_shards , KBA , EIM-DH-INS , Installation , EIM-DH , SAP Data Hub , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.