Model management
Deploy a retrained model directly in to a running Joule with zero down time
Objective
The predictor processor can be configured to load and refresh a model from a linked reference data storage platform.
When this optional setting is applied the relevant logic to switch the model in-place is activated and a model file change process occurs. On a model update the predictor processor execution is paused while the model is replaced.
Any model replacement can be trigger by external drift analysis by using the model audit function.

Explanation on what is going on
Although the configuration may look confusing it due to the ability for every processor to be able to reuse reference data store while being able to gain flexible approach to building capabilities.
To ensure the PMML processor operates with reliable models, it must connect to a model store, allowing for model replacement when necessary.
The key configuration items are:
Defines which
stores
to include. PMML only requires the model store.Set the model store to the
production_churn_models.
One processor initialisation the processor will configure file watchers on the store to trigger model refreshes.
Example
The example below demonstrates how to link to model store.
pmml predictor:
name: customer_churn_predictor
model: churn/customer_churn_rf.pmml
response field: churn_prediction
# Link to the store for this model
model store: production_churn_models
audit configuration:
...
# 1. Define interested stores to bind too
stores:
# Model store
production_churn_models:
store name: customer_churn_models
# Customer spend profiles
production_customer_profiles:
store name: customer_spend_profiles
Storage definition
For this example to work the below reference data definition would need to be deployed so that the processor can successfully bind to the underlying storage platform.
See Reference Data API documentation for further details.
reference data:
name: predictiveModelStores
data stores:
- minio stores:
name: production_models
connection:
endpoint: "https://localhost"
port: 9000
tls: false
credentials:
access key: "AKIAIOSFODNN7"
secret key: "wJalrXUtnFEMIK7MDENGbPxRfiCY"
stores:
customer_churn_models:
bucketId: churn_models
customer_spend_profiles:
bucketId: customer_historical_spend
Last updated
Was this helpful?