[SOLR-2430] Swapping cores with persistent switched on should save swapped core to defaultCoreName

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 4.0-ALPHA
• Component/s: multicore
• Labels: core multicore

Environment

CentOS

• Assignee: Unassigned
• Reporter: bidorbuy
• Created: 16/Mar/11 09:32
• Updated: 02/Oct/16 02:49
• Resolved: 02/Oct/16 02:49

Description

Running on the latest trunk version and configured multi-cores with persistent turned on and set a default-core. When swapping cores I would have expected default behavior to be that the swapped core name would be persisted as the new defaultCoreName. i.e. if switching from primary to staging, the defaultCoreName should be written to "staging".

When swapping out cores (i.e. from primary to staging) and then restarting Jetty, Solr falls back to the current configured default-core (=primary) instead of the previously swapped one (=staging). If this is intended, can perhaps the swap command be extended to force rewritting Solr.xml

Current config file:
<?xml version="1.0" encoding="UTF-8" ?>
<solr sharedLib="lib" persistent="true">
<cores adminPath="/admin/cores" shareSchema="true" defaultCoreName="primary">
<core name="primary" instanceDir="conf/primary/" dataDir="../../data/primary"/>
<core name="staging" instanceDir="conf/staging/" dataDir="../../data/staging"/>
</cores>
</solr>

Issue Links

• relates to: SOLR-2127 When using the defaultCoreName attribute, after performing a swap, solr.xml no longer contains the defaultCoreName attribute, and the core which was dafult is now renamed to ""