[jira] [Commented] (SOLR-10534) Core state doesn't get cleaned up if core initialization fails

2017-04-21 Thread Varun Thacker (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-10534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15979546#comment-15979546
 ] 

Varun Thacker commented on SOLR-10534:
--

This reproduces on Solr 6.5 and Solr 6.4.2

> Core state doesn't get cleaned up if core initialization fails
> --
>
> Key: SOLR-10534
> URL: https://issues.apache.org/jira/browse/SOLR-10534
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Reporter: Varun Thacker
>
> Steps to reproduce:
> Add this to the "add-unknown-fields-to-the-schema" in the data_driven config 
> set
> {code}
> 
> _version_
> 
> {code}
> ./bin/solr start
> ./bin/solr create -c test
> This doesn't work currently because of SOLR-10533 so it throws an error when 
> creating a core.
> At this point I have no local core created for 'test' but the UI displays  
> 'SolrCore initalization failures'
> Now let's fix the schema and remove the update processor
> Running the create command again throws this error but I don't have this core.
> {code
> ~/solr-6.5.0$ ./bin/solr create -c test
> ERROR: 
> Core 'test' already exists!
> Checked core existence using Core API command:
> http://localhost:8983/solr/admin/cores?action=STATUS=test
> {code}
> When I restart and then try again it work correctly.
> The same happens in SolrCloud as well but the experience is even worse. 
> Since no collection was never created but a local core exists the create 
> command blocks and then after a while returns with an error. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[jira] [Commented] (SOLR-10534) Core state doesn't get cleaned up if core initialization fails

2017-04-20 Thread Erick Erickson (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-10534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15977465#comment-15977465
 ] 

Erick Erickson commented on SOLR-10534:
---

Possibly related to SOLR-10021? Can you reproduce this with that patch applied 
(patch on 6.5)

> Core state doesn't get cleaned up if core initialization fails
> --
>
> Key: SOLR-10534
> URL: https://issues.apache.org/jira/browse/SOLR-10534
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Reporter: Varun Thacker
>
> Steps to reproduce:
> Add this to the "add-unknown-fields-to-the-schema" in the data_driven config 
> set
> {code}
> 
> _version_
> 
> {code}
> ./bin/solr start
> ./bin/solr create -c test
> This doesn't work currently because of SOLR-10533 so it throws an error when 
> creating a core.
> At this point I have no local core created for 'test' but the UI displays  
> 'SolrCore initalization failures'
> Now let's fix the schema and remove the update processor
> Running the create command again throws this error but I don't have this core.
> {code
> ~/solr-6.5.0$ ./bin/solr create -c test
> ERROR: 
> Core 'test' already exists!
> Checked core existence using Core API command:
> http://localhost:8983/solr/admin/cores?action=STATUS=test
> {code}
> When I restart and then try again it work correctly.
> The same happens in SolrCloud as well but the experience is even worse. 
> Since no collection was never created but a local core exists the create 
> command blocks and then after a while returns with an error. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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