Component configuration recommendations for horizontal scaling

Based on the recommended hardware sizes, you might need to change the configurations of various product components to make optimum use of available resources.

The following table provides a list of the configuration properties, their locations, and the recommended values for the properties for each setup.

Use the following table in conjunction with the recommendations provided in the horizontal sizing recommendations.

In the table, the configuration location paths must be preceded by one of the following environment variables:

  • Windows: %BMC_ITDA_HOME%
  • Linux: $BMC_ITDA_HOME

Note

When you change any of the following properties, ensure that you re-start the corresponding service for the particular component and any dependent services. For example, the wrapper.java.initmemory property defines the initial memory required for the Indexer, so when you change this property value, ensure that you re-start the Indexer.

For more information about starting or stopping services and service dependencies, see Starting or stopping product services

Ensure that you make the same configuration changes for components of the same type. For example, if you change certain configurations for the Indexer, and you have multiple instances of Indexers deployed, ensure that you make the change for all Indexers in your environment.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Product Component

Configuration property and location

Medium setup

Large setup
IndexerInitial memory required for the Indexer
Indexer

wrapper.java.initmemory

5,000 MB5,000 MB
Indexercustom\conf\services\indexer.conf

Indexer

Maximum memory required for the Indexer
Indexer 

wrapper.java.maxmemory

5,000 MB5,000 MB
Indexercustom\conf\services\indexer.conf
Configuration DatabaseInitial memory required for the Configuration Database
Configuration Database

wrapper.java.initmemory

1,000 MB1,000 MB
Configuration Databasecustom\conf\services\configdb.conf
Configuration DatabaseMaximum memory required for the Configuration Database
Configuration Database  wrapper.java.maxmemory1,000 MB1,000 MB
Configuration Databasecustom\conf\services\configdb.conf
Console Server + SearchInitial memory required for the Console Server + Search
Console Server + Search
 
wrapper.java.initmemory3,000 MB3,000 MB
Console Server + Searchcustom\conf\services\server.conf

Console Server + Search

Maximum memory required for the Console Server + Search
Console Server + Search wrapper.java.maxmemory3,000 MB3,000 MB
Console Server + Searchcustom\conf\services\server.conf
Collection StationInitial memory required for the Collection Station
Collection Station wrapper.java.initmemory4,000 MB4,000 MB

Collection Station

custom\conf\services\collectionstation.conf
Collection StationMaximum memory required for the Collection Station
Collection Station wrapper.java.maxmemory4,000 MB5,000 MB

Collection Station

custom\conf\services\collectionstation.conf
Collection StationMaximum number of concurrent collector threads
Collection Stationcollection.thread.pool.size160160
Collection Station\station\collection\custom\conf\agent.properties
Collection StationNumber of hours of data per index for the Collection Station
Collection Station 

intervalInHrs
(in the name: "data" section only)

2424

Collection Station

\station\collection\custom\conf\customIndexstrategies.yml

Console Server + Search 

Number of hours of data per index for the Console Server + Search

Console Server + Search  

intervalInHrs
(in the name: "data" section only)

2424

Console Server + Search 

\custom\conf\server\customIndexstrategies.yml
Console Server + SearchMaximum number of events to fetch in a single search query

Console Server + Search

search.events.fetch.query.limit 4,000 2,000
Console Server + Search\custom\conf\server\searchserviceCustomConfig.properties
Console Server + SearchUpper cap on the number of search buckets that can be created when events are greater than the search.events.fetch.query.limit value
Console Server + Searchsearch.events.bucket.max.limit150100
Console Server + Search\custom\conf\server\searchserviceCustomConfig.properties
IndexerNumber of shards per index
Indexer 
index.number_of_shards
 Read more...

These changes are required only for the master Indexer installed on the primary node.

Tip: A shard is a way of splitting a large amount of data into multiple portions, where each portion is called a shard. Shards also provide a way of evenly balancing data indexed across multiple Indexer instances.

Notes:

  • Any changes regarding the number of shards are applied only to the newly created indices.
  • Modifying the value in the dynamic_template_1.json file will work only when you start the Indexer for the first time. After the first startup, this value can be changed by using the indexertemplates CLI command

  • With one Indexer instance: 6
  • With two Indexer instances: 12
  • With three Indexer instances: 18
  • With one Indexer instance: 6
  • With two Indexer instances: 12
  • With three Indexer instances: 18
  • With four Indexer instances: 24
  • With five Indexer instances: 30
  • With six Indexer instances: 36
  • With seven Indexer instances: 42

Indexer

\conf\indexer\templates\dynamic_template_1.json
Indexer

Indexing request timeout (in milliseconds)

Indexer 
indexing.request.timeoutmillis
 Read more...

At the time of adding multiple Indexers in your environment, this property must be adjusted to a lower value. Doing this can enable quicker recovery if any of the Indexer nodes go down.

30,0005,000

Indexer

\station\collection\custom\conf\agent.properties
Was this page helpful? Yes No Submitting... Thank you

Comments