eDiscovery Platform (eDP) performance is extremely slow, especially in a Distributed Architecture (DA) environment with multiple eDP nodes and lots of activities running within Veritas eDiscovery Platform.

book

Article ID: 100065239

calendar_today

Updated On:

Description

Error Message

eDP itself doesn't report any errors. However, when examining the mySQL error log in the D:\MySQLData\data\[eDP-Server.err], there are lots of messages below displayed in the log:

[Warning] [MY-013865] [InnoDB] Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.
[Warning] [MY-013865] [InnoDB] Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.
[Warning] [MY-013865] [InnoDB] Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.

Cause

The InnoDB redo log is too small and is running out of space.

Resolution

Increase the InnoDB redo log size so it doesn't run out of space too quickly. There are 2 recommended methods to increase the Innodb_redo_log depending on the environment.
1. Increase the innodb_redo_log_capacity.   Note: By default, the Innodb_redo_log_capacity is 104857600 bytes (100MB).
2. Set innodb_dedicated_server=ON so it can dynamically change as needed.

Method 1: This method is typically beneficial when eDP is a stand-alone server. Increase the innodb_redo_log_capacity to 1GB.

1. Use CW Utility #3 to stop all eDP services and Windows services to stop MySQL service.
2. Open Windows Explorer, and go to D:\MySQL directory.
3. In case something goes wrong, make a copy of my.ini and name it something like my.ini_YYYY-MM-DD.
4. Open the my.ini file with an editor such as Notepad++ or Notepad.
5. Search for the innodb_buffer_pool_size and comment it out by adding the # in front of it.
6. Add the line: innodb_redo_log_capacity = 1048576000; (about 1 GB)

Figure 1. Original my.ini file.

Figure 2. my.ini file after modified.


7. Save the my.ini file in the ANSI format.
8. Use the CW Utility #4 to start eDP services and Windows services to start MySQL service.

Note: If using notepad, use the Save As and save it in an ANSI format; otherwise, the file can become corrupted if saved in another format such as Unicode or UTF-8 format.

Method 2: This method is typically beneficial when eDP is in a DA environment. Set innodb_dedicated_server=ON so it can dynamically change as needed.

Note: When innodb_dedicated_server is enabled, InnoDB automatically configures the following variables:
innodb_buffer_pool_size
innodb_redo_log_capacity
innodb_flush_method

Only consider enabling innodb_dedicated_server if the MySQL instance resides on a dedicated server where it can use all available system resources. In other words, enabling innodb_dedicated_server is not recommended if the MySQL instance shares system resources with other applications.

To enable Innodb_dedicated_server on the server with MySQL installed:

1. Use CW Utility to stop all eDP services and Windows services to stop MySQL service.
2. Open Windows Explorer, and go to D:\MySQL directory.
3. In case something goes wrong, make a copy of my.ini and name it something like my.ini_YYYY-MM-DD.
4. Open the my.ini file with an editor such as Notepad++ or Notepad.
5. Search for the innodb_buffer_pool_size and comment it out by adding the # in front of it.
6. Add the line: innodb_dedicaed_server=ON

Figure 3. my.ini file after modified.

7. Save the my.ini file in the ANSI format.
8. Use the CW Utility #4 to start eDP services and Windows services to start MySQL service.

Note: If using notepad, use the Save As and save it in an ANSI format; otherwise, the file can become corrupted if saved in another format such as Unicode or UTF-8 format.

Issue/Introduction

eDiscovery Platform performance is extremely slow, especially in a Distributed Architecture (DA) environment with multiple eDP nodes and lots of activities running within eDiscovery.