The discovery.properties file contains startup and configuration information for the Discovery Search Engine.
NOTE: As of version 2.8.5, most of the
discovery.properties settings have been
discovery.settings. The Admin Tool now persistently stores settings
applied in the interface to
discovery.settings. Customers should not manually
edit the settings file.
Basic Configuration Options¶
These options would be useful for all engine configurations. The discovery.properties file is read once at engine startup, so any changes made to this file will not be visible until the server has been restarted.
The port setting determines the port on which the Discovery Search Engine listens for requests. To choose another port, set the desired port number using this entry.
Example:port = 8091
The jvm settings are passed to the JVM by the Discovery Search Engine startup script. The value for jvm.memory specifies the maximum memory in megabytes, the engine will use when running.
Example:jvm.memory = 512
The jvm settings are passed to the JVM by the Discovery Search Engine startup script. The engine’s startup script will pass the value of jvm.args as a command -line parameter to configure the JVM. For example, customers who wish to take advantage of Java 1.6 compressed object references in a 64-bit JVM, may want to specify the setting here.
Default: not set
Example:jvm.args = -XX:+UseCompressedOops
This setting represents the total number of data partitions available to the current engine. For Master engines without data, total-partitions would be 0. For Query engines with data, total-partitions would be 1.
Example for Master:total-partitions = 0
Advanced Configuration Options¶
Please contact our support team if you need to change any of these advanced options we can optimize for your use cases.
Controls how far into the search results you can page using startIndex and pageSize.
This defaults to 10,000 items to keep memory and cpu usage sane. Increase this value with caution.
Controls the maximum number of results per group when using groupBy topN.
This defaults to 100 results per group to keep memory and cpu usage sane. Increase this value with caution.