Page tree

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. For example, if you are using a small setup with 16 GB of RAM and eight CPUs, you should change the value of the Indexer's wrapper.java.initmemory property to 12288 .

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

12288 MB12288 MB
Indexer\conf\services\indexer.conf

Indexer

Maximum memory required for the Indexer
Indexer 

wrapper.java.maxmemory

12288 MB12288 MB
Indexer\conf\services\indexer.conf
Configuration DatabaseInitial memory required for the Configuration Database
Configuration Database

wrapper.java.initmemory

256 MB256 MB
Configuration Database\conf\services\configdb.conf
Configuration DatabaseMaximum memory required for the Configuration Database
Configuration Database  wrapper.java.maxmemory512 MB512 MB
Configuration Database\conf\services\configdb.conf
Console Server + SearchInitial memory required for the Console Server + Search
Console Server + Search
 
wrapper.java.initmemory2048 MB2048 MB
Console Server + Search\conf\services\server.conf

Console Server + Search

Maximum memory required for the Console Server + Search
Console Server + Search wrapper.java.maxmemory3072 MB3072 MB
Console Server + Search\conf\services\server.conf
Collection StationInitial memory required for the Collection Station
Collection Station wrapper.java.initmemory2048 MB2048 MB

Collection Station

\conf\services\collectionstation.conf
Collection StationMaximum memory required for the Collection Station
Collection Station wrapper.java.maxmemory4096 MB4096 MB

Collection Station

\conf\services\collectionstation.conf
Collection AgentMaximum number of concurrent collector threads
Collection Agentcollection.thread.pool.size160160
Collection Agent\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)

The value of this property must be a factor of 24, which means it can be one of the following values:

1, 2, 3, 4, 6, 8, 12, 24

This value and the value of the same property for Console Server + Search must match.

11

Collection Station

\station\collection\custom\conf\indexstrategies.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)

The value of this property must be a factor of 24, which means it can be one of the following values:

1, 2, 3, 4, 6, 8, 12, 24

This value and the value of the same property for the Collection Station must match.

11

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 4000 2000
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

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.

Note: Any changes regarding the number of shards are applied only to the newly created indices.

  • With one Indexer instance: 4
  • With two Indexer instances: 8
  • With three Indexer instances: 12
  • With one Indexer instance: 4
  • With two Indexer instances: 8
  • With three Indexer instances: 12
  • With four Indexer instances: 16
  • With five Indexer instances: 20
  • With six Indexer instances: 24
  • With seven Indexer instances: 28

Indexer

\conf\indexer\dynamic_template_1.json
Indexer

Indexing request timeout (in milliseconds)

Indexer 
indexing.request.timeoutmillis

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.

300005000

Indexer

\station\collection\custom\conf\agent.properties

2 Comments

  1.  

  2.