Limitations
Following are the functional limitations due to external factors.
Related information
Table: Limitation description and workaround
| Description | Workaround |
|---|---|
| Users can create a maximum of 32 snapshots for a volume. (VIKE-4605) | None |
| When DataReplication for DR is configured for a Galera 3 pod cluster, VVR performs a full synchronization instead of a smartsync. (4051639) | None. Wait for initial full synchronization to complete before triggering the migration. |
| Remove node is not supported for FSS storage. | To remove node, contact InfoScale Technical support. |
| InfoScale modules fail to load on Kubernetes if SELinux is enabled on the worker nodes. (VIKE-1028) | Perform the following steps: 1. Run the following commands on the worker nodes to enable the tunables. setsebool -P container_manage_cgroup on setsebool -P domain_kernel_load_modules 1.2. Set selinux-enabled: true in /etc/docker/daemon.json.3. Run the following command on the worker nodes to reboot. systemctl daemon-reload && systemctl restart docker |
| Replacing disks or replacing coordination points without unconfiguring fencing is not supported. (VIKE-2563) | Reconfigure the InfoScale cluster with the new coordination points. |
| During migration of an application or before takeover of an application, if PVCs and PVs are added to its namespace, the PVCs and PVs might not successfully restore on the secondary site. | None |
| Upgrades are not supported on two-node FSS configurations using majority-based fencing. If the node with nid 0 is selected for the upgrade, the remaining node is fenced out, causing the Disk Group (DG) to enter a DISABLED state and the upgrade process to hang. (VIKE-5806) | None |
| The dr-manager pod repeatedly crashes. (VIKE-6224) | Ensure that all pvc present in the cluster are either in Bound or Terminating state. |