Support Questions

Find answers, ask questions, and share your expertise

Solr server unexpected version

avatar
Contributor

Hi all,

I've installed SOLR service on HDP 2.6.3 by following this guide:

https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.3/bk_solr-search-installation/content/ch_hdp-...

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: UNKNOWN

Does someone know how to fix this issue? Any suggestions would be appreciated.

Many thanks in advance,

Jorge.

1 ACCEPTED SOLUTION

avatar
Expert Contributor

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 solution in original post

1 REPLY 1

avatar
Expert Contributor

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.