[GitHub] [metron] tigerquoll commented on issue #1526: METRON-2275 Solr Indexing Topology Fails to Start on Secure Cluster with HDP 3.1

[GitBox <gi...@apache.org>]

tigerquoll commented on issue #1526: METRON-2275 Solr Indexing Topology Fails to Start on Secure Cluster with HDP 3.1
URL: https://github.com/apache/metron/pull/1526#issuecomment-538288079
 
 
   Ok, I could not get his one to work.
   Spun up a centos7 cluster (1 hour 45 minutes for a deployment :( ) and then kerberised it ok.
   The followed the instructions at:
     https://metron.apache.org/current-book/metron-platform/metron-solr/index.html
   Which should have got solr up and running, unfortunately when restarted Metron in Ambari, I started getting:
   ```
   
   
   Traceback (most recent call last):
     File "/var/lib/ambari-agent/cache/common-services/METRON/0.7.2/package/scripts/enrichment_master.py", line 118, in <module>
       Enrichment().execute()
     File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 352, in execute
       method(env)
     File "/var/lib/ambari-agent/cache/common-services/METRON/0.7.2/package/scripts/enrichment_master.py", line 110, in restart
       from params import params
     File "/var/lib/ambari-agent/cache/common-services/METRON/0.7.2/package/scripts/params/params.py", line 27, in <module>
       from params_linux import *
     File "/var/lib/ambari-agent/cache/common-services/METRON/0.7.2/package/scripts/params/params_linux.py", line 266, in <module>
       hostname_lowercase = config['hostname'].lower()
     File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py", line 73, in __getattr__
       raise Fail("Configuration parameter '" + self.name + "' was not found in configurations dictionary!")
   resource_management.core.exceptions.Fail: Configuration parameter 'hostname' was not found in configurations dictionary!
   ``` 
   I could use the metron solr collection scripts to create the various collections, and I could then log into http://node1:8983/solr/#/bro/query and see that the solr collections were created.
   
   
   And then I realised I could curl to the SOLR admin interface without any kerberos ticket 
   ```
   klist
   klist: No credentials cache found (filename: /tmp/krb5cc_0)
   set | grep SECURITY
   KAFKA_SECURITY_PROTOCOL=SASL_PLAINTEXT
   SECURITY_ENABLED=false./create_collection.sh yaf
     adding: schema.xml (deflated 80%)
     adding: solrconfig.xml (deflated 72%)
   {
     "responseHeader":{
       "status":0,
       "QTime":16}}
   {
     "responseHeader":{
       "status":0,
       "QTime":2731},
     "success":{
       "10.0.2.15:7574_solr":{
         "responseHeader":{
           "status":0,
           "QTime":1368},
         "core":"yaf_shard1_replica_n1"}}}
   ```
   Is SOLR supposed to be kerberised as well?  
   I dug up some instructions at https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.4/managing-auditing/content/configuring_solrcloud_for_kerberos.html
   Is this supposed to be for lucidwork's distrubtion or well this work for the (I assume) apache solr-cloud distro?
   
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services