Environment
Novell Filr 1.2
Situation
This affects the MySQL appliance (build 1.2.0.409) in a Large Filr deployment:
During initial system initialization when MySQL appliance is setup for the first time, the innodb_buffer_pool memory size is calculated and set in the /etc/my.cnf file. The size is set proportional to the total available physical memory assigned to the appliance at that time. Due to a bug in the initialization scripts, this setting has been set in KB instead of MB which can lead to MySQL service failure (and crash recovery as observed in the mysqld.log file).
During initial system initialization when MySQL appliance is setup for the first time, the innodb_buffer_pool memory size is calculated and set in the /etc/my.cnf file. The size is set proportional to the total available physical memory assigned to the appliance at that time. Due to a bug in the initialization scripts, this setting has been set in KB instead of MB which can lead to MySQL service failure (and crash recovery as observed in the mysqld.log file).
Resolution
A fix for this issue is available in the Filr 1.2 Hot Patch 4, available via the Novell Patch Finder.
Once the fix is applied, the innodb_buffer_pool will be reset proportional to the total physical memory of the system. If you wish to adjust the memory further, please modify the /etc/my.cnf file manually or consult with Novell Technical Support.
Once the fix is applied, the innodb_buffer_pool will be reset proportional to the total physical memory of the system. If you wish to adjust the memory further, please modify the /etc/my.cnf file manually or consult with Novell Technical Support.