Component configuration recommendations for single-server sizing

Based on the single-server sizing recommendations, 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. The nonproduction setup values are default values of the properties described.

Use the information in the table in conjunction with the single-server 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 restart 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.

Product Component	Configuration property and location	Non-production setup (Default)	Small setup
Indexer	Initial memory required for the Indexer
Indexer	`wrapper.java.initmemory`	512 MB	4,000 MB
Indexer	custom\conf\services\indexer.conf	512 MB	4,000 MB
Indexer	Maximum memory required for the Indexer
Indexer	`wrapper.java.maxmemory`	1,024 MB	4,000 MB
Indexer	custom\conf\services\indexer.conf	1,024 MB	4,000 MB
Configuration Database	Initial memory required for the Configuration Database
Configuration Database	`wrapper.java.initmemory`	256 MB	512 MB
Configuration Database	custom\conf\services\configdb.conf	256 MB	512 MB
Configuration Database	Maximum memory required for the Configuration Database
Configuration Database	`wrapper.java.maxmemory`	512 MB	512 MB
Configuration Database	custom\conf\services\configdb.conf	512 MB	512 MB
Console Server + Search	Initial memory required for the Console Server + Search
Console Server + Search	`wrapper.java.initmemory`	512 MB	1024 MB
Console Server + Search	custom\conf\services\server.conf	512 MB	1024 MB
Console Server + Search	Maximum memory required for the Console Server + Search
Console Server + Search	`wrapper.java.maxmemory`	768 MB	3,000 MB
Console Server + Search	custom\conf\services\server.conf	768 MB	3,000 MB
Collection Station	Initial memory required for the Collection Station
Collection Station	`wrapper.java.initmemory`	512 MB	2,048 MB
Collection Station	custom\conf\services\collectionstation.conf	512 MB	2,048 MB
Collection Station	Maximum memory required for the Collection Station
Collection Station	`wrapper.java.maxmemory`	768 MB	2,048 MB
Collection Station	custom\conf\services\collectionstation.conf	768 MB	2,048 MB
Collection Station	Maximum number of concurrent collector threads
Collection Station	`collection.thread.pool.size`	10	40
Collection Station	\station\collection\custom\conf\agent.properties	10	40
Collection Station	Number of hours of data per index for the Collection Station
Collection Station	`intervalInHrs` (in the name: "data" section only) Read more... 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.	6	1
Collection Station	\station\collection\custom\conf\customIndexstrategies.yml	6	1
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) Read more... 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.	6	1
Console Server + Search	\custom\conf\server\customIndexstrategies.yml	6	1
Console Server + Search	Maximum number of events to fetch in a single search query
Console Server + Search	`search.events.fetch.query.limit`	1,000	1,000
Console Server + Search	\custom\conf\server\searchserviceCustomConfig.properties	1,000	1,000
Console Server + Search	Upper limit on the number of search buckets that can be created when events are greater than the `search.events.fetch.query.limit` value
Console Server + Search	`search.events.bucket.max.limit`	50	50
Console Server + Search	\custom\conf\server\searchserviceCustomConfig.properties	50	50
Indexer	Number of shards per index
Indexer	index.number_of_shards Read more... To change this property, you need to run the configureindexsettings CLI command. 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.	4	4
Indexer	\conf\indexer\dynamic_template_1.json	4	4
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,000	30,000
Indexer	\station\collection\custom\conf\agent.properties	30,000	30,000

Page tree

Component configuration recommendations for single-server sizing