The following information describes common tasks that an administrator performs to
maintain watsonx.data in production.
Service configuration
| Task |
Required permissions |
Details |
| Enhancing the query performance
through caching |
Cluster administrator |
This procedure helps you to add (enable), edit, and delete different layers of caching that
watsonx.data supports. Metastore versioned cache and File and stripe footer
cache are enabled by default with an option to update any of the properties listed in the
following procedure |
| Accessing Metadata Service (MDS)
using NodePort |
Cluster administrator |
You can access the watsonx.data Metadata Service (MDS service from outside the
OpenShift Container Platform cluster by exposing the MDS using a NodePort
service. |
Database configuration
| Task |
Required permissions |
Details |
| Accessing the
MinIO console |
Cluster administrator |
For exploratory purposes, you can access the sample bucket that comes with watsonx.data through the user interface of MinIO. An edge route is the recommended way to expose
the MinIO console. |
Resource management
| Task |
Required permissions |
Details |
| Manually scaling
resources for services |
Instance administrator |
Adjust watsonx.data by scaling resources to support high availability or to
increase processing capacity. Resources can be scaled based on predefined resource
configurations. |
| Automatically scaling
resources for services |
Instance administrator |
Enable autoscaling with the OpenShift®
Horizontal Pod Autoscaler (HPA). The HPA changes the resource allocation of services by increasing
or decreasing the number of pods in response to CPU or memory consumption. |
| Shutting down and
restarting services |
Instance administrator |
Manually shut down watsonx.data to prevent it from using resources. You can restart
the service when you need to use it again. |