Agent configuration & set-up
Basic configuration
Definitions
Resource | Definition |
---|---|
Blackout Agent |
|
High Resource Agent |
|
Default Workers |
|
High Resource Workers |
|
What to know about agent installation
- Blackout Agents are installed through the Blackout Agent Configuration system admin tab instead of the Relativity agent tab
- The Blackout Agent Configuration tab provides a list of all of the agent servers that are registered to your instance and whether they are enabled for use with Blackout
- Agents must be installed via the Blackout Agent Configuration tab
- Blackout Agents must not be on the same servers that are used for the following: Conversion, Conversion Complete, or dtSearch Agents.
Common configurations
For all configurations, it is recommended to have agent servers with no less than 8 CPU cores and 8 GB of RAM.
For a lot of smaller case work, 1-2 Blackout agents is sufficient. For larger cases with documents in the 10's of thousands, 2-4 agents should be employed.
Blackout is flexible! Agents can be turned on and off at any time so long as there is one agent with default and high resource processes. This action can be taken even if there are running projects.
How to install Blackout agents
- Navigate to the Blackout tab, then choose Agent Configuration.
- After identifying which agent server to install the Blackout agent to, select the ‘Enabled’ checkbox.
- Make sure the ‘Is High Resource’ box is checked off
- Blackout requires at least one agent server to be marked as a high resource.
- When selected as a high resource, these agents will perform OCR and Native Spreadsheet markups in addition to all other actions.
- Click the ‘Save Configurations’ button.
The agents will be deployed and installed by Blackout. Low and high priority worker counts will be determined automatically. For more information on this is determined please see the Advanced Configuration section.
Verifying agent installation
The status of the agent can be verified by:
- Navigate to the Server & Agent Management tab, then choose ‘Agents.’
- Filter the application column to ‘Blackout.’
- After finding the ‘enabled’ column, it will be set to ‘Yes.’ The Message column will read ‘Running (#;#).’ The numbers will represent the default and high resource workers, respectively.
Other considerations
- The amount of work Blackout can handle is tied to your configuration and set-up. There are many things that can change how fast Blackout runs such as the size of Excel documents or the resolution of images.
- The worker counts that are automatically assigned are done to help balance other work that may be taking place on the agent server(s).
- This means that dedicated agents can be configured to use all of the resources on a server
- To accomplish this, please see the Advanced Configuration section.
Adding a Blackout server to a resource pool
What to know
Resource pool aware agents allow system administrators to create dedicated agents for individual clients and workspaces, isolating their Blackout capacity from the rest of the system.
System administrators can easily control this behavior from the Blackout Agent Configuration administrator tab. When the setting is enabled, the tab displays which resource pools a server is assigned to. In addition, Blackout Administrators can now view which resource pool a project is running in from the Blackout Project Status tab.
How to do it
- Navigate to the Blackout | Blackout Agent Configuration tab.
- Click on Enable Resource Pools.
A new column will appear showing the resource pool the agent is assigned to.
Advanced Configuration
The Blackout Agent Configuration tab also has an advanced mode. This will allow for a more specific configuration of the default and high resource workers on each agent server.
Note: Before enabling this setting, feel free to reach out to us at support@milyli.com.
What to know
- It is generally safe to increase the number of high resource workers to a 1:1 ratio with the number of CPUs as long as there is not a lot of load on the agent server from other agents
- Increasing beyond this will not necessarily equate to increased throughput
- It is important to use your test instances to identify configurations that work for your hardware and Relativity instance as throughput varies greatly from instance to instance and infrastructure to infrastructure
How to do it
Note: You must be a Relativity administrator to make this change.
- Navigate to the Blackout | Configuration tab.
- Click the ‘Enable Advanced Agent Configuration Options’ checkbox.
- A confirmation prompt will be displayed, asking if you are sure you wish to enable advanced mode.
- Click ‘Ok’ on the confirmation prompt.
- Click the ‘Save’ button.
The Advanced Agent Configuration options are now available on the Agent Configuration tab.
Updating Worker Counts
- After enabling advanced mode, the Agent Configuration page will automatically update to include two additional columns, ‘Default Workers’ and ‘High Resource Workers’
- Updating worker counts while projects are active will result in those projects briefly stopping work before resuming
The following sample will demonstrate how to increase the number of high resource workers. In this example there are three agent servers, TR-Agent, QP-Agent, and JL-Agent, with the following configuration.
Agent Server | Details |
---|---|
TR-Agent | 4 CPUs and 12GB RAM |
QP-Agent | 1 CPU and 4GB RAM |
JL-Agent | 8 CPU and 8GB RAM |
The default installation will set the default and high resource workers as followed.
Server | Default Configuration |
---|---|
TR-Agent | 8 Default Workers 2 High Resource Workers |
QP-Agent | 2 Default Workers 1 High Resource Workers |
JL-Agent | 12 Default Workers 4 High Resource Workers |
An example of maximizing these servers, especially if they are dedicated, would look like this:
Server | Maximized Configuration |
---|---|
TR-Agent | 10 Default Workers 4 High Resource Workers |
QP-Agent | 2 Default Workers 1 High Resource Workers |
JL-Agent | 12 Default Workers 8 High Resource Workers |
After changing the values:
- Click ‘Save Configurations’ after the values are updated.
- A notification will be displayed letting you know that the change has been made.
- If you accidentally uncheck all of the ‘Is High Resources’ boxes so that there are none left, you will receive a validation error letting you know that you must have at least one high resource enabled agent.
After clicking save, behind the scenes:
- The agents internal server will be stopped
- The configuration for each agent will be updated
- The agents will be restarted
- The project engine will work to pick up where it left off.