Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-2430

Swapping cores with persistent switched on should save swapped core to defaultCoreName

    XMLWordPrintableJSON

    Details

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

      CentOS

      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>

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                tech@bidorbuy.co.za bidorbuy
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: