Please follow the below mentioned steps whenever you face such issue: Cloudera Manager provides Atlas action option to initialize Atlas, which creates all the required backend resources HBase table, Solr collection and Kafka topics. Navigate to Atlas from the Cloudera Manager UI. Under actions, the Initialize Atlas option appears. Initiate it; it will create the required resources. Once done, verify the Altas UI. If the issue is still not resolved, perform the following steps: Login to Solr host and kinit with Solr principal as follows: # klist -kt /var/run/cloudera-scm-agent/process/XXX-solr-SOLR_SERVER/solr.keytab # kinit -kt /var/run/cloudera-scm-agent/process/XXX-solr-SOLR_SERVER/solr.keytab solr/host_name.principal.com@COE.CLOUDERA.COM Delete the /solr and /solr-infra znodes using Zookeeper client. Do the following: #/opt/cloudera/parcels/CDH/bin/zookeeper-client # ls / [solr, solr-infra] # deleteall /solr # deleteall /solr-infra # ls / (should not show any solr or solr-infra znodes) While performing the above steps, if you face error as "Authentication is not valid : /solr-infra/security" or "Node not empty: /solr-infra/security/zkdtsm/ZKDTSMRoot", kindly perform the following steps, or else skip to Step 3. Temporarily disable ACL by setting 'zookeeper.skipACL=yes' in ZooKeeper's Java Advance configuration in Cloudera Manager Navigate to Cloudera Manager > Zookeeper Service In Configuration, add '-Dzookeeper.skipACL=yes' to Java Configuration Options for Zookeeper Server Restart ZooKeeper with the new configuration. Run the following:#export JAVA_HOME=/usr/java/jdk1.8.0 #/opt/cloudera/parcels/CDH-X.X.X/lib/solr/server/scripts/cloud-scripts/zkcli.sh -cmd clear -z "localhost:2181" /solr-infra Repeat Step a Stop Solr service Execute Initialize Solr action from Solr service. Start Solr service Stop the Atlas service Execute Initialize Atlas action from Atlas service On Solr host, check if the following command returns the atlas_configs instancedir: #solrctl instancedir --list #sample output _default atlas_configs managedTemplate If it returns atlas_configs, skip this create command. If it does not return atlas_configs, execute the following create command: #solrctl instancedir --create atlas_configs /opt/cloudera/parcels/CDH/etc/atlas/conf.dist/solr/ Check if the following command returns the edge_index, fulltext_index, and vertex_index collections: #solrctl collection --list. #sample output vertex_index (5) edge_index (5) fulltext_index (5) If it does return the 3 collections above, skip the create commands below. If it does not return the 3 collections above, execute the following commands:#solrctl collection --create edge_index -c atlas_configs -s 1 -r 1 -m 1 #solrctl collection --create fulltext_index -c atlas_configs -s 1 -r 1 -m 1 #solrctl collection --create vertex_index -c atlas_configs -s 1 -r 1 -m 1 Start the Atlas service and bring up the UI. For Reference: https://my.cloudera.com/knowledge/quotError-from-server-at-httpsolr-hostapacheorg8993solr-Can?id=300885 https://community.cloudera.com/t5/Customer/ERROR-quot-Can-not-find-the-specified-config-set-vertex/ta-p/310611
... View more
