11.05.2016 Views

Apache Solr Reference Guide Covering Apache Solr 6.0

21SiXmO

21SiXmO

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

will explain why the request failed.<br />

Examples<br />

Input<br />

Delete ConfigSet 'myConfigSet'<br />

http://localhost:8983/solr/admin/configs?action=DELETE&name=myConfigSet<br />

Output<br />

<br />

<br />

0<br />

170<br />

<br />

<br />

List ConfigSets<br />

/admin/configs?action=LIST<br />

Fetch the names of the ConfigSets in the cluster.<br />

Examples<br />

Input<br />

http://localhost:8983/solr/admin/configs?action=LIST&wt=json<br />

Output<br />

{<br />

"responseHeader":{<br />

"status":0,<br />

"QTime":203},<br />

"configSets":["myConfigSet1",<br />

"myConfig2"]}<br />

Rule-based Replica Placement<br />

When <strong>Solr</strong> needs to assign nodes to collections, it can either automatically assign them randomly or the user can<br />

specify a set nodes where it should create the replicas. With very large clusters, it is hard to specify exact node<br />

names and it still does not give you fine grained control over how nodes are chosen for a shard. The user should<br />

be in complete control of where the nodes are allocated for each collection, shard and replica. This helps to<br />

optimally allocate hardware resources across the cluster.<br />

Rule-based replica assignment allows the creation of rules to determine the placement of replicas in the cluster.<br />

In the future, this feature will help to automatically add or remove replicas when systems go down, or when<br />

higher throughput is required. This enables a more hands-off approach to administration of the cluster.<br />

This feature is used in the following instances:<br />

<strong>Apache</strong> <strong>Solr</strong> <strong>Reference</strong> <strong>Guide</strong> <strong>6.0</strong><br />

605

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!