Component configuration recommendations

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. The nonproduction setup values are default values of the properties described. Use the following table in conjunction with the recommendations provided in the Hardware sizing recommendations topic. For example, if you are using a small setup with 8 GB of RAM and four core CPUs, you should change the value of the wrapper.java.initmemory property to 4096 MB.

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

Related topics

Where to find more information

Variables that affect sizing and scalability

Hardware sizing recommendations

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.

Configuration property and location	Description	Non-production setup (Default)	Small setup	Medium setup	Large setup
`wrapper.java.initmemory`	Initial memory required for the Indexer	512 MB	4096 MB	8192 MB	8192 MB
\conf\services\indexer.conf	Initial memory required for the Indexer	512 MB	4096 MB	8192 MB	8192 MB
`wrapper.java.maxmemory`	Maximum memory required for the Indexer	1024 MB	4096 MB	8192 MB	8192 MB
\conf\services\indexer.conf	Maximum memory required for the Indexer	1024 MB	4096 MB	8192 MB	8192 MB
`wrapper.java.initmemory`	Initial memory required for the Configuration Database	256 MB	256 MB	256 MB	256 MB
\conf\services\configdb.conf	Initial memory required for the Configuration Database	256 MB	256 MB	256 MB	256 MB
`wrapper.java.maxmemory`	Maximum memory required for the Configuration Database	512 MB	512 MB	512 MB	512 MB
\conf\services\configdb.conf	Maximum memory required for the Configuration Database	512 MB	512 MB	512 MB	512 MB
`wrapper.java.initmemory`	Initial memory required for the Console Server + Search	512 MB	1024 MB	2048 MB	2048 MB
\conf\services\server.conf	Initial memory required for the Console Server + Search	512 MB	1024 MB	2048 MB	2048 MB
`wrapper.java.maxmemory`	Maximum memory required for the Console Server + Search	768 MB	1536 MB	3072 MB	3072 MB
\conf\services\server.conf	Maximum memory required for the Console Server + Search	768 MB	1536 MB	3072 MB	3072 MB
`wrapper.java.initmemory`	Initial memory required for the Collection Station	512 MB	768 MB	1024 MB	2048 MB
\conf\services\collectionstation.conf	Initial memory required for the Collection Station	512 MB	768 MB	1024 MB	2048 MB
`wrapper.java.maxmemory`	Maximum memory required for the Collection Station	768 MB	1024 MB	1772 MB	3072 MB
\conf\services\collectionstation.conf	Maximum memory required for the Collection Station	768 MB	1024 MB	1772 MB	3072 MB
`collection.thread.pool.size`	Maximum number of concurrent collector threads	10	20	40	40
\station\collection\custom\conf\agent.properties	Maximum number of concurrent collector threads	10	20	40	40
`intervalInHrs` (in the name: "data" section only)	Number of hours of data per index for the Collection Station 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	2	1	1
\station\collection\custom\conf\indexstrategies.yml		6	2	1	1
`intervalInHrs` (in the name: "data" section only)	Number of hours of data per index for the Console Server + Search 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	2	1	1
\custom\conf\server\customIndexstrategies.yml		6	2	1	1
index.number_of_shards	Number of shards per index 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	4	With one Indexer instance in the cluster: 4 With two Indexer instances in the cluster: 4 With three Indexer instances in the cluster: 6 With four Indexer instances in the cluster: 8 With five Indexer instances in the cluster: 10
\conf\indexer\dynamic_template_1.json		4	4	4
indexing.request.timeoutmillis	Indexing request timeout (in milliseconds) At the time of adding Indexers to the Indexer cluster, this property must be adjusted to a lower value. Doing this can enable quicker recovery of the Indexer cluster if any of the Indexer nodes go down.	30000	30000	30000	5000
\station\collection\custom\conf\agent.properties		30000	30000	30000	5000

Page tree

Component configuration recommendations