You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by GitBox <gi...@apache.org> on 2019/10/01 15:26:23 UTC

[GitHub] [metron] nickwallen edited a comment on issue #1519: METRON-2265: Update Kerberos settings

nickwallen edited a comment on issue #1519: METRON-2265: Update Kerberos settings
URL: https://github.com/apache/metron/pull/1519#issuecomment-536046991
 
 
   +1 I was able to kerberize successfully.  I am finding that running kerberized in the development environment with HDP 3.1 is a bit unstable due to limited resources in the VM.  This has always been a problem and requires a bit of massaging. 
   
   Here are some brief notes on things I did to get this to work in our resource constrained dev environment.
   * Before you begin the kerberization wizard in Ambari stop all sensor stubs.
       ```
       systemctl stop sensor-stubs-bro
       systemctl stop sensor-stubs-yaf
       systemctl stop sensor-stubs-snort
       ```
   
   * Elasticsearch will fail the service check after kerberization.  Its status will remain "yellow" due to resource constraints.  This will prevent the other services from being started automatically.  
   
   * When this service check fails, just close the kerberos wizard and continue on. Then manually restart the HDP and Metron services that you want to test.  Avoid starting anything that you don't need like YARN, etc.
   
   * Restart a single telemetry source to see telemetry flow end-to-end.  No need to run all 3 of the demo telemetry sources and this lightens the load a bit.
       ```
       systemctl start sensor-stubs-bro
       ```
   
   * Shut-down  as many services as you can that are not directly in-use like YARN, MR, Profiler, Pcap, etc when trying to validate.
   
   @tigerquoll Might any of this help explain what might have happened in your environment?
   

----------------------------------------------------------------
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