All Apps and Add-ons

where do you install Python for Scientific Computing (for Linux 64-bit) in a distributed search environment?

davebo1896
Communicator

Where does the Python for Scientific Computing SA get installed in a distributed environment? Indexers? Search Heads? Both?

1 Solution

msainani_splunk
Splunk Employee
Splunk Employee
  1. For a non-distributed environment:
    a. Single Instance Splunk Deployment i.e. SH + Indexer on the same server: PSC and MLTK should be both installed
    b. 1 Search Head + 1 Indexer: PSC should be installed on both Search Head and Indexer (only if using streaming apply feature), while MLTK needs to be installed only on Search Head

  2. For distributed search environment:
    a. 1 Search Head + N Indexers: PSC should be installed on both Search Head and Indexers (only if using streaming apply feature), while MLTK needs to be installed only on Search Head
    b. N Search Heads + N Indexers: PSC should be installed on all Search Heads and Indexers (only if using streaming apply feature), while MLTK needs to be installed only on all Search Heads

  3. For Search Head Clustering - N Search Heads (part of Search Head Cluster) + M Indexers: PSC + MLTK should be installed via a deployer to the Search Head Cluster, in addition, PSC should be installed on all Indexers (only if using streaming apply feature).

To be clear, please note that customers are required to install PSC on Indexers ONLY if they want to use the streaming apply capability. By default, the streaming apply feature is turned off, so you’re not required to have PSC installed on all your indexers in the indexing cluster. For more details, read the section Use your indexers to apply models here -> https://docs.splunk.com/Documentation/MLApp/2.0.0/User/Installandconfigure

View solution in original post

msainani_splunk
Splunk Employee
Splunk Employee
  1. For a non-distributed environment:
    a. Single Instance Splunk Deployment i.e. SH + Indexer on the same server: PSC and MLTK should be both installed
    b. 1 Search Head + 1 Indexer: PSC should be installed on both Search Head and Indexer (only if using streaming apply feature), while MLTK needs to be installed only on Search Head

  2. For distributed search environment:
    a. 1 Search Head + N Indexers: PSC should be installed on both Search Head and Indexers (only if using streaming apply feature), while MLTK needs to be installed only on Search Head
    b. N Search Heads + N Indexers: PSC should be installed on all Search Heads and Indexers (only if using streaming apply feature), while MLTK needs to be installed only on all Search Heads

  3. For Search Head Clustering - N Search Heads (part of Search Head Cluster) + M Indexers: PSC + MLTK should be installed via a deployer to the Search Head Cluster, in addition, PSC should be installed on all Indexers (only if using streaming apply feature).

To be clear, please note that customers are required to install PSC on Indexers ONLY if they want to use the streaming apply capability. By default, the streaming apply feature is turned off, so you’re not required to have PSC installed on all your indexers in the indexing cluster. For more details, read the section Use your indexers to apply models here -> https://docs.splunk.com/Documentation/MLApp/2.0.0/User/Installandconfigure

hjauch_splunk
Splunk Employee
Splunk Employee

The MLTK doc been updated with this information: http://docs.splunk.com/Documentation/MLApp/2.0.0/User/Installandconfigure

Information for cloud installs has also been added.

Get Updates on the Splunk Community!

Join Us for Splunk University and Get Your Bootcamp Game On!

If you know, you know! Splunk University is the vibe this summer so register today for bootcamps galore ...

.conf24 | Learning Tracks for Security, Observability, Platform, and Developers!

.conf24 is taking place at The Venetian in Las Vegas from June 11 - 14. Continue reading to learn about the ...

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...