Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The following page has been changed by HossMan: http://wiki.apache.org/solr/CoreAdmin The comment on the change is: minor formating fixes and "multi core" vocab cleanup ------------------------------------------------------------------------------ + = Core Administration = <!> ["Solr1.3"] + + Since ["Solr1.3"], !SolrCore can optionally be managed at runtime. Additionally, Solr allows multiple !SolrCore instances to run within a single web-app. The cores can be dynamically managed via the !CoreAdminHandler. For alternative ways to manage multiple indicies, see MultipleIndexes. [[TableOfContents]] - = Overview = - - Since ["Solr1.3"], SolrCore can optionally be managed at runtime. Additionally, Solr allows multiple SolrCore instances to run within a single web-app. The cores can be dynamically managed via the CoreAdminHandler. For alternative ways to manage multiple indicies, see MultipleIndexes. - = Configuration = - To enable multi core support, place a file named ''solr.xml'' in the solr.home + To enable support for dynamic !SolrCore administration, place a file named ''solr.xml'' in the solr.home directory. Here is an example ''solr.xml'' file: {{{ <solr persistent="true" sharedLib="lib"> @@ -38, +37 @@ The properties can also be defined in a core's scope (inside the <core> element) in which case they can be used only in that core's scope. If a property by that name already exists in the container scope then it will be overridden. Besides them, a few properties are automatically added in the core scope. They are: - * solr.core.name -- The core's name as defined in solr.xml + * `solr.core.name` -- The core's name as defined in solr.xml - * solr.core.instanceDir -- The core's instance directory (i.e. the directory under which that core's config and data directory are located) + * `solr.core.instanceDir` -- The core's instance directory (i.e. the directory under which that core's `conf/` and `data/` directory are located) - * solr.core.configName -- The name of the core's config file (solrconfig.xml by default) + * `solr.core.configName` -- The name of the core's config file (solrconfig.xml by default) - * solr.core.schemaName -- The name of the core's schema file (schema.xml by default) + * `solr.core.schemaName` -- The name of the core's schema file (schema.xml by default) Such properties can be used inside solrconfig.xml and schema.xml files by specifying an expression with optionally, a default value. {{{ @@ -59, +58 @@ == cores == The `<cores>` tag accepts one attribute: - *'''adminPath''' - RequestHandler path to access the !CoreAdminHandler for dynamic core manipulation. For example, adminPath="/admin/cores" configures access via http://localhost:8983/solr/admin/cores. If this attribute is not specified, dynamic manipulation is unavailable. + *'''adminPath''' - Relative path to access the !CoreAdminHandler for dynamic core manipulation. For example, adminPath="/admin/cores" configures access via http://localhost:8983/solr/admin/cores. If this attribute is not specified, dynamic manipulation is unavailable. == core == The `<core>` tag accepts two attributes: @@ -73, +72 @@ = Example = - Solr ships with an example running two cores together setup. To run this configuration, start jetty using: + Solr ships with an example running two cores together setup. To run this configuration, start jetty in the `example/` directory using: {{{ java -Dsolr.solr.home=multicore -jar start.jar }}} @@ -93, +92 @@ The !CoreAdminHandler is a special SolrRequestHandler that is used to manage existing cores. Unlike normal !SolrRequestHandlers, the !CoreAdminHandler is not attached to a core, - it is configured in solr.xml. A single CoreAdminHandler exists for each web-app + it is configured in solr.xml. A single !CoreAdminHandler exists for each web-app To enable dynamic core configuration, make sure the ''adminPath'' attribute is set in solr.xml. If this attribute is absent, the !CoreAdminHandler will not be available.
