Search

E.3. Enabling Gluster Block Storage as Backend for Metrics

download PDF
Follow the tasks mentioned below to enable Gluster Block Storage as backend for metrics

Note

By default, since Container Native Storage performs three-way replication, data will be available to the restarted node from anywhere in the cluster. As a result, it is recommended that Cassandra-level replication is turned off to avoid capacity overhead
  1. The openshift_metrics_cassandra_storage_type ansible variable should be set to dynamic:
    [OSEv3:vars]openshift_metrics_cassandra_storage_type=dynamic
    For example, a sample set of variables for openshift_metrics_ are listed below.
    openshift_metrics_cassandra_storage_type=dynamic
    openshift_metrics_cassandra_pvc_size=5G
    openshift_metrics_cassandra_replicas=3
    openshift_metrics_cassandra_limits_memory=2G
    openshift_metrics_cassandra_nodeselector={'region':'infra'}
    openshift_metrics_hawkular_nodeselector={'region':'infra'}
    openshift_metrics_heapster_nodeselector={'region':'infra'}
  2. To verify, execute the following command:
    # oc get pods --n openshift-infra
    It should list the following pods running:
    heapster-cassandra
    heapster-metrics
    hawkular-&*9
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.