Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

HDP Ambari: when adding new host, "Cluster not found, clusterName=clusterID=-1"

Highlighted

HDP Ambari: when adding new host, "Cluster not found, clusterName=clusterID=-1"

Contributor

Hi!  Hoping for HOPEFULLY some solution to this?   I'm really stuck.

I have an HDP cluster that's been around for a long while now.   And successfully upgraded from previous versions and so on.    Everything managed by ambari works as expected (start/stop services, etc).

But I am at the point of needing to add a new host to the cluster.   I add the host...  it installs the agent...   SUCCESS.... but then when "checking host for potential problems", I end up with an endless series of this error:

2019-09-09 11:43:50,654 WARN [ambari-action-scheduler] ExecutionCommandWrapper:219 - Unable to lookup the cluster by ID; assuming that there is no cluster and therefore no configs for this execution command: Cluster not found, clusterName=clusterID=-1

So clearly, there's a disconnect somewhere and I am at a loss.   Over time something got lost or corrupted.    I am hoping this can be "repaired" somehow.    When ambari starts, the database check comes out clean (log of that is down below).  And as stated above, everything else appears to work fine.     The curl/api check for the cluster name returns the expected result.

Help?

I am hoping it's a simple config file edit, or perhaps a database entry to verify/update, or...  ?


BUT-- If necessary I wouldn't be averse to just re-installing ambari from the ground up, but do not know how I would "preserve" the settings I have in place and the list of installed services and data for the cluster nodes that are there now.


Database check upon the ambari server startup:

2019-09-09 11:46:00,197 INFO - Checking DB store version
2019-09-09 11:46:00,523 INFO - DB store version is compatible
2019-09-09 11:46:02,630 INFO - ******************************* Check database started *******************************
2019-09-09 11:46:02,631 INFO - Ensuring that the schema set for Postgres is correct
2019-09-09 11:46:02,642 INFO - Checking for configs that are not mapped to any service
2019-09-09 11:46:02,655 INFO - Checking for more than 1 configuration of the same type being enabled.
2019-09-09 11:46:02,656 INFO - Checking for hosts without state
2019-09-09 11:46:02,656 INFO - Checking host component states count equals host component desired states count
2019-09-09 11:46:02,657 INFO - Checking services and their configs
2019-09-09 11:46:02,657 INFO - Getting ambari metainfo instance
2019-09-09 11:46:02,657 INFO - Executing query 'GET_SERVICES_WITHOUT_CONFIGS'
2019-09-09 11:46:02,658 INFO - Executing query 'GET_SERVICE_CONFIG_WITHOUT_MAPPING'
2019-09-09 11:46:02,658 INFO - Getting stack info from database
2019-09-09 11:46:02,659 INFO - Executing query 'GET_SERVICES_WITH_CONFIGS'
2019-09-09 11:46:02,661 INFO - Comparing service configs from stack with configs that we got from db
2019-09-09 11:46:02,661 INFO - Getting services from metainfo
2019-09-09 11:46:02,661 INFO - Processing HDP-3.0 / HDFS
2019-09-09 11:46:02,661 INFO - Processing HDP-3.0 / MAPREDUCE2
2019-09-09 11:46:02,661 INFO - Processing HDP-3.0 / HBASE
2019-09-09 11:46:02,661 INFO - Processing HDP-3.0 / ZOOKEEPER
2019-09-09 11:46:02,661 INFO - Processing HDP-3.0 / YARN
2019-09-09 11:46:02,661 INFO - Comparing required service configs from stack with mapped service configs from db
2019-09-09 11:46:02,661 INFO - Getting services which has mapped configs which are not selected in clusterconfig
2019-09-09 11:46:02,663 INFO - Checking for tables with large physical size
2019-09-09 11:46:02,664 INFO - The database table host_role_command is currently 16.180 MB and is within normal limits (3000.000)
2019-09-09 11:46:02,664 INFO - The database table execution_command is currently 10.570 MB and is within normal limits (3000.000)
2019-09-09 11:46:02,664 INFO - The database table stage is currently 1.234 MB and is within normal limits (3000.000)
2019-09-09 11:46:02,665 INFO - The database table request is currently 0.469 MB and is within normal limits (3000.000)
2019-09-09 11:46:02,665 INFO - The database table alert_history is currently 8.031 MB and is within normal limits (3000.000)
2019-09-09 11:46:02,665 INFO - ******************************* Check database completed *******************************

Don't have an account?
Coming from Hortonworks? Activate your account here