Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

There are two new attributes of a core (defaults in bold) and one new attribute for controlling how many transient cores are loaded at once.

  • Wiki Markup
    transientCacheSize=\[NNN\]. If this limit is crossed, old cores marked 'transient="true"' are removed to make room on an LRU basis. Default size *Integer.MAX_VALUE*. _Only_ cores with "transient=true" are put in this cache, so specifying this attribute without having any cores marked as "transient" has no effect except wasting a bit of memory.

    • Having this size be less than the number of cores marked 'transient="true"' AND 'loadOnStartup="true"' should work, but it's wasteful since a bunch of cores will be loaded on startup then immediately unloaded after the cache fills up.
    • NOTE: All transient core information is read at startup and the "list of cores" is unbounded.
  • old-style: this is an attribute of the <cores> tag
    • new-style: this is a child node of the <solr> tag, and looks like <int name="transientCacheSize">12</int>
  • Wiki Markup
    loadOnStartup=\["*true*"|"false"\]. Whether the core should be completely loaded upon startup.

    • old-style: this is an attribute of each individual <core> tag
    • new-style: this is an entry in the "core.properties" file for each core.
  • Wiki Markup
    transient=\["true"|"*false*"\]. Whether the core should be put in the LRU list of cores that may be unloaded. NOTE: When a core is unloaded, any outstanding operations (indexing or query) will be completed before the core is closed.

    • old-style: this is an attribute of each individual <core> tag
    • new-style: this is an entry in the "core.properties" file for each core.

...