Veritas InfoScale™ for Kubernetes Environments 8.0.330 - Linux
- Overview
- System requirements
- Preparing to install InfoScale on Containers
- Installing Veritas InfoScale on OpenShift
- Installing InfoScale on a system with Internet connectivity
- Installing InfoScale in an air gapped system
- Installing Veritas InfoScale on Kubernetes
- Tagging the InfoScale images on Kubernetes
- Installing InfoScale on Kubernetes
- Configuring KMS-based Encryption on an OpenShift cluster
- Configuring KMS-based Encryption on a Kubernetes cluster
- InfoScale CSI deployment in Container environment
- Dynamic provisioning
- Snapshot provisioning (Creating volume snapshots)
- Managing InfoScale volume snapshots with Velero
- Volume cloning
- Installing and configuring InfoScale DR Manager on OpenShift
- Installing and configuring InfoScale DR Manager on Kubernetes
- Disaster Recovery scenarios
- Configuring InfoScale
- Administering InfoScale on Containers
- Upgrading InfoScale
- Troubleshooting
Changing the peerinact value in a cluster
The LLT peerinact parameter determines the amount of time InfoScale waits before declaring a node as faulted. Increasing the peerinact value allows for more tolerance for network outages, especially in environments that have known higher network latencies.
The default peerinact value may not be suitable for all environments. You may have to adjust this parameter as per your specific network requirements to ensure an optimal performance. Set peerinact to a value greater than the longest expected network delay in your environment.
The peerinact value is set in hundredths of a second or centiseconds. The default value is 1600 or 16 seconds. The recommended value is 3200 or 32 seconds.
To modify the peerinact value
- Sign in to a driver node as an admin user and overwrite the peerinact annotation value using the following command:
# oc annotate infoscalecluster -n infoscale-vtas infoscalecluster-qa "infoscale.veritas.com/peerinact"="<value>" --overwrite
Here, <value> is the desired peerinact value in seconds or minutes.
For example, to set the peerinact value to 32 seconds, run the following command:
# oc annotate infoscalecluster -n infoscale-vtas infoscalecluster-qa "infoscale.veritas.com/peerinact"="32s" --overwrite
Note:
Specify the peerinact value in seconds or minutes. The InfoScale Operator converts it into centiseconds and updates the llttab configuration file.
- It may take some time for the changes to take effect in a running cluster. You can verify the changes using the following commands:
# oc exec -ti -n infoscale-vtas infoscale-sds-21532-731e5d2fe3e92f-v67zp - lltconfig -T query | grep peerinact
The output may resemble the following:
peerinact = 6000 udppeerinact = 700
# oc exec -ti -n infoscale-vtas infoscale-sds-21532-731e5d2fe3e92f-v67zp - cat /etc/llttab | grep peerin
The output may resemble the following:
set-timer peerinact:6000
Note:
For fresh InfoScale clusters, you can add this annotation with the desired value in the yaml before applying the yaml file. In case of OpenShift, from the web console, switch to the yaml view for adding or modifying this parameter value.