You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Aaron Greenspan (JIRA)" <ji...@apache.org> on 2015/08/07 06:33:45 UTC

[jira] [Created] (SOLR-7894) Solr Forgets Core Setup And Throws Fake Errors Each Time It Starts

Aaron Greenspan created SOLR-7894:
-------------------------------------

             Summary: Solr Forgets Core Setup And Throws Fake Errors Each Time It Starts
                 Key: SOLR-7894
                 URL: https://issues.apache.org/jira/browse/SOLR-7894
             Project: Solr
          Issue Type: Bug
    Affects Versions: 5.2.1
         Environment: CentOS 6.3
Linux 2.6.32-504.23.4.el6.x86_64 #1 SMP Tue Jun 9 20:57:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
            Reporter: Aaron Greenspan


I have two Solr cores that I need to use. Their folders are already set up with appropriate permissions in the /solr subdirectory I'm using. Nevertheless, each time I start and stop Solr, the following ridiculous dance has to take place:

1. I go to the web interface on port 8983.
2. No cores are listed. I press the Add Core button.
3. I type in the name of the first of the two cores I want to re-add that was just there when the process was running previously in the "name" and "instanceDir" fields. I leave the other fields with their default values.
4. I press the blue "Add Core" button.
5. I get the following red error message: "Error CREATEing SolrCore '[core name]': Could not create a new core in /home/solr/server/solr/[core name]/as another core is already defined there
6. I press the gray "Cancel" button.
7. I click "Java Properties" on the left side, or some other link in the administrative interface, just to get off the cores page.
8. I go back to the cores page.
9. The core is listed and is working fine.

This is absurd.

For one thing, I shouldn't have to do *anything*. Either by scanning the directory for the annoying-as-hell XML configuration files or some other method, it should remember the cores that were just there. But even assuming that's impossible for some reason (which it's not), I should not be getting a technically true but practically useless and misleading error message that suggests that adding the core *didn't* work when in fact it *did*.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org