My Oracle Support Banner

After Upgrade Navigator Metadata Server is in Bad Health with "Error upgrading solr configuration or data. org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: undefined field: "id"" (Doc ID 2343534.1)

Last updated on JANUARY 22, 2020

Applies to:

Big Data Appliance Integrated Software - Version 4.5.0 and later
Linux x86-64

Symptoms

NOTE: In the images, examples and document that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 


After upgrade from BDA V4.5/CDH 5.7.1 to CDH BDA V4.9/CDH 5.11.1 and then upgrade from  BDA v4.9/CDH 5.11.1 to BDA V4.10/CDH 5.12.1 the Cloudera Management server is in bad health.

It fails with an error like:

[main]: Error upgrading solr configuration or data.
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: undefined field: "id"
at org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:552)
at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
at org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:91)
at org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:301)
at com.cloudera.nav.server.NavServerUtil.getMaxIdInSolr(NavServerUtil.java:197)
at com.cloudera.nav.server.SolrSchemaUpgrade.updateMaxIdInDatabase(SolrSchemaUpgrade.java:1035)
at com.cloudera.nav.server.SolrSchemaUpgrade.upgradeSolr(SolrSchemaUpgrade.java:261)
at com.cloudera.nav.server.NavServer.run(NavServer.java:439)
at com.cloudera.nav.server.NavServer.main(NavServer.java:122)

Logging into MySQL and querying "select * from NAV_UPGRADE_ORDINAL;" from the Navigator Metadata database is found to return an incorrect ORDINAL value.

For example, on BDA V4.10/CM 5.12.1 logging into MySQL and querying "select * from NAV_UPGRADE_ORDINAL;" from the Navigator Metadata database should return ORDINAL value of 26 as below.  If anything is else is returned this indicates a problem.  Note that the values are specific to the CM release.  Also note that the ORDINAL value is the current value and OLD_ORDINAL the prior version.

For BDA 4.10/CM 5.12.1 the correct ORDINAL value is 26 e.g.:

Other values indicate an error.

A list of ORDINAL values on other BDA/CM versions is:

Navigator Version Cloudera Manager Version Ordinal Number
 2.6.0  5.7.0  11
 2.6.1  5.7.1  11
 2.6.2  5.7.2  11
 2.6.3  5.7.3  12
 2.6.4  5.7.4  12
 2.7.0  5.8.0  13
 2.7.1  5.8.1  13
 2.7.2  5.8.2  14
 2.7.3  5.8.3  14
 2.8.0  5.9.0  14
 2.8.1  5.9.1  14
 2.8.2  5.9.2  14
 2.8.3  5.9.3  14
 2.9.0  5.10.0  14
 2.9.1  5.10.1  20
 2.9.2  5.10.2  20
 2.10.0  5.11.0  21
 2.10.1  5.11.1  22
 2.10.2  5.11.2  22
 2.11.0  5.12.0  26
 2.11.1  5.12.1  26
 2.12.0  5.13.0  26

Note: BDA V4.5 supports CM 5.7.0, BDA V4.6 supports CM 5.8.1, BDA V4.7 supports CM 5.9.0, BDA V4.8 supports 5.10.1, BDA V4.9 supports CM 5.11.1, BDA V4.10 supports CM 5.12.1, BDA V4.11 supports CM 5.13.1.

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
 Steps to Try First
 Steps to Try Second


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.