My Oracle Support Banner

Step 7 of Mammoth Upgrade Fails With "Navigator Metadata Server fails to start" (Doc ID 2308119.1)

Last updated on OCTOBER 14, 2018

Applies to:

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


Step 7 of Mammoth upgrade fails with output like:

Error [9179]: (//[main]/Hadoop::Upgradeactions/Exec[set_cluster_conf]/returns)
change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/ &>
/opt/oracle/BDAMammoth/bdaconfig/tmp/setclusterconf.out returned 1 instead of one of [0]

Additional Symptoms are:

1. /opt/oracle/BDAMammoth/bdaconfig/tmp/setclusterconf.out points to commands_51933.out which shows output like:

a) /opt/oracle/BDAMammoth/bdaconfig/tmp/setclusterconf.out shows output like:

Command 51933 finished after 5 seconds
Operation failed
Result Message is: "Service must have either started or stopped roles.",

b) commands_51933.out shows output like:

"id" : 51933,
"name" : "Restart",
"startTime" : "2017-09-09T22:42:54.876Z",
"endTime" : "2017-09-09T22:42:54.876Z",
"active" : false,
"success" : false,
"resultMessage" : "Service must have either started or stopped roles.",
"serviceRef" : {
"serviceName" : "mgmt"
"children" : {
"items" : [ ]
"canRetry" : false

2. Checking Cloudera Manager (CM) shows that the Management Service, mgmt, is not starting because the Navigator Metadata Server fails to start.

3. Navigating: mgmt > Navigator Metadata Server > Instances > Process, shows:

This role's process is starting. This role is supposed to be started.

4. The Navigator Metadata Server log, /var/log/cloudera-scm-navigator/, on the node with Navigator Metadata Server role, Node 3 by default,  shows output like:

Exception: Cursor functionality requires a sort containing a uniqueKey field tie breaker
at org.apache.solr.handler.component.QueryComponent.prepare(
at org.apache.solr.handler.component.SearchHandler.handleRequestBody(
at org.apache.solr.handler.RequestHandlerBase.handleRequest(
at org.apache.solr.core.SolrCore.execute(
at org.apache.solr.servlet.SolrDispatchFilter.execute(
at org.apache.solr.servlet.SolrDispatchFilter.doFilter(
at org.apache.solr.servlet.SolrDispatchFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at org.eclipse.jetty.servlets.UserAgentFilter.doFilter(
at org.eclipse.jetty.servlets.GzipFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
at com.cloudera.nav.auth.SharedSecretRequestFilter.doFilter(
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
2017-09-09 19:40:48,181 ERROR com.cloudera.nav.server.NavServer [main]: Error upgrading solr configuration or data.
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Cursor functionality requires a sort containing a uniqueKey field tie breaker
at org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(
at org.apache.solr.client.solrj.impl.HttpSolrServer.request(
at org.apache.solr.client.solrj.impl.HttpSolrServer.request(
at org.apache.solr.client.solrj.request.QueryRequest.process(
at org.apache.solr.client.solrj.SolrServer.query(
at com.cloudera.nav.utils.solr.SolrResultSetIterator.getNextBatch(
at com.cloudera.nav.utils.solr.SolrResultSetIterator.hasNext(
at com.cloudera.nav.server.upgrade.DeleteEntities.deleteForSide(
at com.cloudera.nav.server.upgrade.DeleteEntities.blindDelete(
at com.cloudera.nav.server.upgrade.DeleteEntities.upgrade(
at com.cloudera.nav.server.upgrade.AbstractSolrUpgrade.upgrade(
at com.cloudera.nav.server.SolrSchemaUpgrade.performJavaUpgrade(



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

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