Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 05-17-2018 03:08 PM
Hi all,
I've installed SOLR service on HDP 2.6.3 by following this guide:
After successfully installed and started the the SOLR service, this alert is displayed in Ambari:
The following components are reporting unexpected versions:
host.fqdn
SOLR_SERVER: UNKNOWNDoes someone know how to fix this issue? Any suggestions would be appreciated.
Many thanks in advance,
Jorge.
Created 03-28-2019 02:01 PM
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.
Created 03-28-2019 02:01 PM
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.