Frequently Asked Questions
Frequently Asked Questions
IDOL - Adding New Engines Into IDOL 12.x. Cluster
Posted by Kimmo Pyhältö (M-Files) on 20 December 2019 10:13 AM

IDOL index can be expanded after the initial deployment by adding extra engines to the cluster. Currently, up to 16 engines can be used in a single cluster meaning some 20 million documents per index. Even adding the engine is quite straightforward operation, the vault has to be re-indexed (only .idx indexing) after the addition. As an extra motivation, the index backup is created during the process.

This document describes how to add new engines into existing cluster and how to re-index it so IDOL can utilize the extra capacity.

NOTE 1! This document is valid for IDOL version 12.x and beyond.
NOTE 2! Using this document requires basic understanding of IDOL components and terminology.

Keywords: IDOL, cluster, engine, addition

1. Prerequisites

- Existing IDOL 12.x cluster
- Setup tools for IDOL 12. Because the procedure uses some installation scripts and the installation instructions, the setup tools for IDOL 12 should be available. 
- MFAutonomyConsole is used for verifying the functionality of addition and for investigating problem situations. It can be found also from Setup tools for IDOL 12.

2. Steps to add new engines into the existing cluster

1. During the initial installation you have used IDOL12_setup_tool.xlsm to plan the cluster and to generate the installation scripts. You have also saved that file to have the current configuration for future usage. Now is that time. Open the file.

2. Select the last content engine line (whole line) and copy it.
 
3. Insert the copied line into the last free line after the content engine.

Result: The line is copied under the last content engine and the conflict appears due to the same port numbers.
 
4. Change the port numbers and select Solo install: Yes.
 
5. If you have previously added new engines with the solo install, change any previous Solo: yes to empty.

6. Generate scripts.

Result: A new installation scripts have been generated to the installation folder. The notable one is that has SOLO_INSTALL on it.
 
7. Open the command prompt with administrative rights and run the solo installation script.

Result: If the script is successful, it will tell few manual steps you have to do to make the cluster aware of the new engine.
 
8. Before taking the steps mentioned in number 7's Result, repeat steps 2-7 as many times as many extra engines you want.

9. Add new engines to the DIH's and DAH's configuration files.

Example: We have added two extra engines using port ranges 13000 and 14000. In following lines, changes are in orange color and added lines are in blue color. The usual location of dih.cfg and dah.cfg is C:\IDOL12\bin\[installation name]\dih and C:\IDOL12\bin\[installation name]\dah.

DIH

[DIHEngines]
Number=4
[DIHEngine0]
Host = 10.1.8.122
Port = 11000
[DIHEngine1]
Host = 10.1.8.122
Port = 12000
[DIHEngine2]
Host = 10.1.8.122
Port = 13000
[DIHEngine3]
Host = 10.1.8.122
Port = 14000

DAH

///[Server]
DistributedEngines=5
……
[DistributedEngine0]
Host = 10.1.8.122
Port = 9000
[DistributedEngine1]
Host = 10.1.8.122
Port = 11000
[DistributedEngine2]
Host = 10.1.8.122
Port = 12000
[DistributedEngine3]
Host = 10.1.8.122
Port = 13000
[DistributedEngine4]
Host = 10.1.8.122
Port = 14000

10. Restart DIH and DAH services.

11. Now it is time to export the index and import it again so the DIH will more or less spread the contents of the index to the new engines. Refer to IDOL 12 installation instructions chapters 10.1 and 10.2 for exporting and importing (= Re-indexing) the data.

3. Process in the future

The process of adding new engines will become easier in the future, when we abandon the idea of "fixed" index content. That will make the need of re-indexing obsolete.

 

(0 vote(s))
This article was helpful
This article was not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below. This is required to prevent automated registrations and form submissions.

Help Desk Software by Kayako case