Veritas InfoScale™ 7.4.3 Release Notes - Linux
- Introduction and product requirements
- Changes introduced in InfoScale 7.4.3
- Limitations
- Virtualization software limitations
- Storage Foundation software limitations
- Dynamic Multi-Pathing software limitations
- Veritas Volume Manager software limitations
- Veritas File System software limitations
- SmartIO software limitations
- Replication software limitations
- Cluster Server software limitations
- Limitations related to bundled agents
- Limitations related to VCS engine
- Veritas cluster configuration wizard limitations
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- Limitations related to LLT
- Limitations related to I/O fencing
- Limitations related to bundled agents
- Storage Foundation Cluster File System High Availability software limitations
- Storage Foundation for Oracle RAC software limitations
- Storage Foundation for Databases (SFDB) tools software limitations
- Known issues
- Issues related to installation and upgrade
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager known issues
- Veritas File System known issues
- Virtualization known issues
- Replication known issues
- Cluster Server known issues
- Operational issues for VCS
- Issues related to the VCS engine
- Issues related to the bundled agents
- Issues related to the VCS database agents
- Issues related to the agent framework
- Cluster Server agents for Volume Replicator known issues
- Issues related to Intelligent Monitoring Framework (IMF)
- Issues related to global clusters
- Issues related to the Cluster Manager (Java Console)
- VCS Cluster Configuration wizard issues
- LLT known issues
- I/O fencing known issues
- Operational issues for VCS
- Storage Foundation and High Availability known issues
- Storage Foundation Cluster File System High Availability known issues
- Storage Foundation for Oracle RAC known issues
- Oracle RAC known issues
- Storage Foundation Oracle RAC issues
- Storage Foundation for Databases (SFDB) tools known issues
- Application isolation feature known Issues
- Cloud deployment known issues
- Issues related to Veritas InfoScale Storage in Amazon Web Services cloud environments
- Container deployment know issues
Linux I/O Scheduler for Database Workloads
Veritas recommends using the Linux deadline I/O scheduler for database workloads on both Red Hat and SUSE distributions.
To configure a system to use this scheduler, include the elevator=deadline
parameter in the boot arguments of the GRUB or LILO configuration file.
The location of the appropriate configuration file depends on the system's architecture and Linux distribution:
Configuration File | Architecture and Distribution |
---|---|
| RHEL7 x86_64, RHEL8 x86_64, SLES12 x86_64 and SLES15 x86_64 |
For the GRUB configuration files, add the elevator=deadline
parameter to the kernel command.
For RHEL 7, add elevator=deadline
to GRUB_CMDLINE_LINUX
in /etc/default/grub
.
For example:
GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rd.lvm.lv=vgroot/root elevator=deadline crashkernel=auto rhgb quiet" GRUB_DISABLE_RECOVERY="true"
and then rebuild the /boot/grub2/grub.cfg
file to reflect the changes:
On BIOS-based machines:
# grub2-mkconfig -o /boot/grub2/grub.cfg
On UEFI-based machines:
# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
A setting for the elevator parameter is always included by SUSE in its LILO and GRUB configuration files. In this case, change the parameter from elevator=cfq
to elevator=deadline
.
Reboot the system once the appropriate file has been modified.
See the Linux operating system documentation for more information on I/O schedulers.