Configuration properties

The directory location where table data is stored (in SSTables). The database distributes data evenly across the location, subject to the granularity of the configured compaction strategy. Default locations: /var/lib/cassandra/data.

To ensure that records with TTLs are purged from search indexes when they expire, the search indexes are periodically checked for expired documents. The ttl_index_rebuild_options settings control the schedulers in charge of querying for and removing expired records, and the execution of the checks.

Schedules how often to check for expired data in seconds. Default: 300

Speeds startup time by delaying the first TTL checks in seconds. Default: 20

Sets the maximum number of documents to check and delete per batch by the TTL rebuild thread. Default: 4096

To manage system resource consumption and prevent many search cores from executing simultaneous TTL deletes, defines the maximum number of cores that can execute TTL cleanup concurrently. Default: 1

Default: 10. You can configure the maximum resource file size or disable resource upload Sets the maximum DSE Search resource upload size limit in megabytes (MB). Set to 0 to disable resource uploading.

Configures the maximum number of concurrent asynchronous indexing threads per DSE Search index. Default: number_of_available_CPU_cores.

Allows back pressure system to adapt max auto soft commit time (defined per search index config) to the actual load. Setting is respected only for NRT (near real time) cores. When DSE search cores have real-time (RT) live indexing, adaptive commits are disabled regardless of this property value. See live indexing with RT.

The total number of queued asynchronous indexing requests per search core. When this number is exceeded, back pressure prevents excessive resource consumption by throttling new incoming requests. DataStax recommends using a back_pressure_threshold_per_core value of 1000 * max_solr_concurrency_per_core.

The maximum time, in minutes, to wait for the flushing of asynchronous index updates, which occurs at DSE Search commit time or at flush time. Expert level knowledge is required to change this value. Always set the value reasonably high to ensure flushing completes successfully to fully sync DSE Search indexes with the database data. If the configured value is exceeded, index updates are only partially committed, and the commit log is not truncated to ensure data durability.

The maximum time, in minutes, to wait for each DSE Search index to load on startup or create/reload operations, expressed. This advanced option should be changed only if exceptions happen during core loading.

DSE Search activates the configured disk failure policy if IOExceptions occur during index update operations.

The directory to store index data. For example:

The Apache Lucene® field cache is deprecated. Instead, for fields that are sorted, faceted, or grouped by, set docValues="true" on the field in the schema.xml file. Then reload the core and reindex. The default value is false. To override false, set useFieldCache=true in the request.

For DSE Search, configure whether to asynchronously reindex bootstrapped data. Default: false

Configuration options include:

Default: 5000. The number of milliseconds that the coordinator waits for read operations to complete before timing it out.

Security options for DSE Search. See DSE Search security checklist.

Specify settings to tune encryption of search indexes.

Specify whether to allocate shared DSE Search decryption cache off JVM heap. Default: true

Sets the maximum size of shared DSE Search decryption cache, in megabytes (MB). Default: 256

The http_principal is used by the Tomcat application container to run DSE Search. The Tomcat web server uses GSS-API mechanism (SPNEGO) to negotiate the GSSAPI security mechanism (Kerberos). Set REALM to the name of your Kerberos realm. In the Kerberos principal, REALM must be uppercase.

Inter-node communication between DSE Search nodes.

For inter-node communication between DSE Search nodes.

Default: 60000. The client request timeout is the maximum cumulative time (in milliseconds) that a distributed search request will wait idly for shard responses. Defines timeout behavior during distributed queries.

Options for CQL Solr queries.

Options to specify the paging behavior.

The maximum time in milliseconds to wait for each row to be read from the database during CQL Solr queries. Default: 10000 (10 seconds).

The default IP address that the HTTP and Solr Admin interface uses to access DSE Search. See Changing Tomcat web server settings.

Default: localhost. The listen address for client connections (Thrift RPC service and native transport). Valid values:

Decreasing the memtable space to make room for Solr caches might improve performance. See Changing the stack size and memtable space.

Default: 32. note Writes in DSE are rarely I/O bound, so the ideal number of concurrent writes depends on the number of CPU cores on the node. The recommended value is 8 x number_of_cpu_cores.

Default: 1/4 of heap size. note

Node routing options.

Node health options are always enabled for all nodes. Node health is a score-based representation of how fit a node is to handle search queries.

Default: 60000

Default: 10800 (3 hours). The amount of continuous uptime required for the node’s uptime score to advance the node health score from 0 to 1 (full health), assuming there are no recent dropped mutations. The health score is a composite score based on dropped mutations and uptime.

Default: 30. The historic time window over which the rate of dropped mutations affect the node health score.