Changing Solr configuration file properties in the managed configuration

To override default values for managed search templates set in the solrconfig.xml file use a solrcore.properties file. You can create a solrcore.properties file in the conf directory of a master, subordinate, or repeater core under the managed Solr template.

Before you begin

Procedure

  1. Create a solrcore.properties file in the conf directory of a master, subordinate, or repeater core under the managed-solr template.
    Example

    Search.zip/managed-solr/repeater/solr/home/MC_masterCatalogId/locale/CatalogEntry/conf

    .
  2. Add the new properties and values that you want to override to the file.
    You can override the following properties:
    solr.ramBufferSizeMB
    Sets the amount of memory that can be used by Lucene indexing for buffering added documents and deletions before they are flushed to the directory.
    solr.mergeFactor
    Controls how many segments get merged at a time. For TieredMergePolicy, mergeFactor is a convenience parameter that sets both MaxMergeAtOnce and SegmentsPerTier at the same time. For LogByteSizeMergePolicy, mergeFactor decides how many new segments are allowed before they are merged into one.
    solr.filterCache.size
    The maximum number of entries in the filter cache
    solr.filterCache.initialSize
    The initial number of entries in the filter cache.
    solr.filterCache.autowarmCount
    The number of entries to prepopulate from the old cache.
    solr.queryResultCache.size
    The initial number of document objects to cache.
    solr.queryResultCache.initialSize
    The initial number of search results to cache.
    solr.queryResultCache.autowarmCount
    The number of search results to prepopulate from the old cache.
    solr.documentCache.size
    The maximum number of document objects to cache.
    solr.documentCache.initialSize
    The maximum number of document objects to cache.
    solr.documentCache.autowarmCount
    The number of document objects to prepopulate from the old cache.
    solr.queryResultWindowSize
    An optimization for use with the queryResultCache. When a search is requested, a superset of the requested number of document IDs are collected.

    For example, if a search for a particular query requests matching documents 10 - 19, and queryWindowSize is 50, then documents 0 - 49 are collected. Any further requests in that range can be retrieved from the cache.

    solr.queryResultMaxDocsCached
    The maximum number of documents to cache for any entry in the queryResultCache.
    solr.maxWarmingSearchers
    The maximum number of searchers that might be concurrently warming in the background. An error is returned if this limit is exceeded.

    Recommended: Set a master or repeater to 1 or 2, when the server is dedicated for indexing and not designed to handle live traffic.

    While not recommended, if the master or repeater is used for both indexing and handling live traffic, set the value higher.

    Set subordinates to 1 or 2.

    solr.maxBooleanClauses
    The maximum number of clauses in each BooleanQuery. An exception is thrown if this limit is exceeded.

    Warning: This option modifies a global Lucene property that affects all Solr cores. If multiple solrconfig.xml files contain different values for this property, the last Solr core value to be initialized is used.

    For example, to change the solr.ramBufferSizeMB property, use the following format:
    
solr.ramBufferSizeMB=1024
  3. Save your changes and close the file.
  4. Repeat the property changes for all the search cores.