Glad the issue the resolved but try to use some other location to store those jars instead of /opt/cloudera/parcels as when you upgrade you can lose all those jars. ... View more

Yes, thats correct. You can get more details here https://www.cloudera.com/documentation/enterprise/5-9-x/topics/search_sentry.html   Also, Now sentry as a service is also provided for solr you can use that too and use solr sentry tool commands ... View more

yes, that's the correct solution and you can look at this code example too.   import org.apache.solr.client.solrj.SolrServer; import org.apache.solr.client.solrj.SolrServerException; import org.apache.solr.common.SolrInputDocument; //import org.apache.solr.client.solrj.impl.CommonsHttpSolrServer; import org.apache.solr.client.solrj.impl.HttpSolrServer; import org.apache.solr.client.solrj.impl.CloudSolrServer; import org.apache.solr.client.solrj.response.QueryResponse; import org.apache.solr.client.solrj.SolrQuery; import org.apache.solr.client.solrj.*; import org.apache.solr.common.SolrInputDocument; import org.apache.solr.client.solrj.beans.Field; import org.apache.solr.common.cloud.*; import org.apache.solr.common.SolrDocumentList; import org.apache.solr.common.params.ModifiableSolrParams; import org.apache.solr.client.solrj.impl.*;   import javax.security.auth.callback.*; import javax.security.auth.login.LoginContext; import java.io.*; import java.util.*; import java.net.MalformedURLException;   public class SolrKerberosAuth { public SolrKerberosAuth() {   }     public static void main(String[] args) throws SolrServerException, IOException {   HttpClientUtil.setConfigurer(new Krb5HttpClientConfigurer()); System.setProperty("java.security.auth.login.config", "/home/user.name/jaas-client.conf <http://user.name/jaas-client.conf>"); HttpSolrServer server = new HttpSolrServer("http://solr-host:8983/solr/solrtest");     SolrInputDocument doc = new SolrInputDocument(); doc.addField("id", "1111"); // doc.addField("source", "TestSource9");   try { // server.ping(); server.add(doc); } catch (SolrServerException e) { e.printStackTrace(); } catch (IOException e) { e.printStackTrace(); } }   }   javac -cp "/opt/cloudera/parcels/CDH/jars/*" SolrKerberosAuth.java   ... View more

The only current way to log solr request queries is:   Please set log4j.logger.org.apache.solr.core.SolrCore.Request=DEBUG to show queries before they are executed. Add this snippet to: Cloudera Manager --> Solr --> Configuration --> Solr Server Logging Advanced Configuration Snippet (Safety Valve) If this is set, queries will show a DEBUG log entry before they are executed, then an INFO with qtime and numDocs returned ... View more

No, I meant the gateway role or if needed spark history server role where you don't see spark-default.conf having a correct config.   Gateway role is better. If you don't want to delete. Just add a new gateway role from CM->Spark->Instances and then see if then configuration comes correct.     ... View more

This issue only can occur if spark-default.conf has the wrong config and getting overwritten from safety valve or it got changed manually from command line.   Maybe try deleting the role and add on a new host and do deploy client config and see what happens.     ... View more

Simple solr indexing example using post:   http://www.solrtutorial.com/solr-in-5-minutes.html   or you can use solrj   http://www.solrtutorial.com/solrj-tutorial.html   even you can try indexing using flume and moprhline solr sink   https://www.cloudera.com/documentation/enterprise/5-5-x/topics/search_tutorial.html ... View more

Were you running the above commands from one of the solr nodes or the node which had the solr gateway on it? Did you have any solr node down when you were deleting or creating a collection as taking time issue can happen that time? Did you see any unexpected exits with solr like out of memory issues?   As taking the time can either happen when no solr gateway but that time it will throw some error after a certain time.   or if you had any shard down for the collection you were trying to delete then restart may have helped with that. ... View more

The error showing that file_length field is missing Caused by: org.apache.solr.common.SolrException: ERROR: [doc=1966-05-19 10:36:59.365118] unknown field 'file_length'   solr doesn't have a file_length field specified so either you need to sanitize unknown fields using morphline before sending to solr or add file_length to solr.   Solr throws an exception on any attempt to load a document that contains a field that is not specified in schema.xml and looks like your data have that and your scheme.xml doesn't have that field.   More details regarding sanitizeUnknownSolrFields   http://kitesdk.org/docs/1.1.0/morphlines/morphlines-reference-guide.html#sanitizeUnknownSolrFields       ... View more