This happens since the "version" fields in the DB remain un-updated. You can follow: 1. Login into Ambari DB. 2. Look out for the "version" column in "hostcomponentstate" table. 3. Update the column with the current active version of your cluster. 4. Restart ambari server process. This is an example from my test cluster: ambari=> select * from hostcomponentstate where component_name='SOLR_SERVER';
id | cluster_id| component_name| version| current_state| host_id| service_name| upgrade_state|security_state
----+-----------+---------------+--------+--------------+--------+-------------+--------------+---------------
100| 2| SOLR_SERVER | UNKNOWN| INSTALLED | 2| SOLR | NONE |SECURED_KERBEROS
(1 row) ambari=> update hostcomponentstate set version = '2.6.5.108-1'
where component_name = 'SOLR_SERVER';
UPDATE 1 ambari=> select * from hostcomponentstate where component_name='SOLR_SERVER';
id |cluster_id| component_name| version |current_state|host_id|service_name|upgrade_state| security_state
----+----------+---------------+-----------+-------------+-------+------------+-------------+---------------
100| 2| SOLR_SERVER |2.6.5.108-1|INSTALLED | 2|SOLR |NONE |SECURED_KERBEROS
(1 row) # ambari-server restart Hope this addresses your concern.
... View more
Hi @anarasimham, after enabling interactive query we can use Hive 2.1. Hive users were asking for this feature because they needed to use Hive 2.1 syntax in their queries. Many thanks for your help, Jorge.
... View more
Hi Aditya, I've checked the DNS, forward and reverse, and I've seen that "hostname -f" doesn't display fqdn. After solving this issue, all services are up and running. Thank you! Jorge.
... View more
