[jira] [Commented] (SOLR-11361) After Restarting Solr 6.6.1 Seems to cause Error if Application is Reading/Writing?

2017-11-04 Thread Richard Rominger (JIRA) 

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

Richard Rominger commented on SOLR-11361:
-

Best that I can tell, this is no longer happening with Solr 6.6.2

> After Restarting Solr 6.6.1 Seems to cause Error if Application is 
> Reading/Writing?
> ---
>
> Key: SOLR-11361
> URL: https://issues.apache.org/jira/browse/SOLR-11361
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Affects Versions: 6.6.1
> Environment: Windows 10 VM
>Reporter: Richard Rominger
>Priority: Major
>  Labels: newbie, upgrade, windows
>
> I have just updated from Solr 6.2.1 to 6.6.1.  I put into place a fresh 6.6.1 
> and mounted our Core (umslogs).  This loaded perfectly fine on port 8181 and 
> our application is able to write/read data.
> The problem started when I restart Solr 6.6.1 and the below error appeared 
> after Solr 6.6.1 came up accessible via the web page. 
>   
> *HttpSolrCall
> null:org.apache.solr.core.SolrCoreInitializationException: SolrCore 'umslogs' 
> is not available due to init failure: null *
> Next my testing lead me to start up Solr on port 8282 that no application is 
> connecting/reading/writing to.  On this test umslogs core loads is perfectly 
> fine after erroring above.
> Next my testing lead me to close +our application+ that writes/reads to Solr 
> 8181umslogs core and shutdown Solr 8282 umslogs core.  Then  I restarted  
> Solr back on Poret 8181 and the umslogs core loads properly and our 
> application that that writes/reads to Solr 8181 is once again operational.
> Our application has used Solr 4.10.x, then Solr 6.2.x okay.  Then again I do 
> not doubt that I might have done something wrong with the 6.6.1 upgrade that 
> is causing the above behavior 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (SOLR-11361) After Restarting Solr 6.6.1 Seems to cause Error if Application is Reading/Writing?

2017-09-18 Thread Shawn Heisey (JIRA) 

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

Shawn Heisey commented on SOLR-11361:
-

With 6.6.0, I see the problem in SOLR-11297.

I was trying to track something down on the 6.6.0 install (/solr/admin/metrics 
not working), and came across an error about an index, but the error didn't 
mention the index directory.  Therefore I found the error logging in the source 
code, checked out the branch_6x code, modified the code to display what 
directory was having the issue, and built/installed version 6.6.2-SNAPSHOT.

With the upgrade, I began having problems where cores actually did not 
successfully load, which is a very different problem than SOLR-11297.  I saw 
the "SolrCore 'xx' is not available due to init failure: null" message in 
my logs just like this issue mentions, but could not find anything in the logs 
that actually indicated why the core failed to initialize.


> After Restarting Solr 6.6.1 Seems to cause Error if Application is 
> Reading/Writing?
> ---
>
> Key: SOLR-11361
> URL: https://issues.apache.org/jira/browse/SOLR-11361
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Affects Versions: 6.6.1
> Environment: Windows 10 VM
>Reporter: Richard Rominger
>  Labels: newbie, upgrade, windows
>
> I have just updated from Solr 6.2.1 to 6.6.1.  I put into place a fresh 6.6.1 
> and mounted our Core (umslogs).  This loaded perfectly fine on port 8181 and 
> our application is able to write/read data.
> The problem started when I restart Solr 6.6.1 and the below error appeared 
> after Solr 6.6.1 came up accessible via the web page. 
>   
> *HttpSolrCall
> null:org.apache.solr.core.SolrCoreInitializationException: SolrCore 'umslogs' 
> is not available due to init failure: null *
> Next my testing lead me to start up Solr on port 8282 that no application is 
> connecting/reading/writing to.  On this test umslogs core loads is perfectly 
> fine after erroring above.
> Next my testing lead me to close +our application+ that writes/reads to Solr 
> 8181umslogs core and shutdown Solr 8282 umslogs core.  Then  I restarted  
> Solr back on Poret 8181 and the umslogs core loads properly and our 
> application that that writes/reads to Solr 8181 is once again operational.
> Our application has used Solr 4.10.x, then Solr 6.2.x okay.  Then again I do 
> not doubt that I might have done something wrong with the 6.6.1 upgrade that 
> is causing the above behavior 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Re: [jira] [Commented] (SOLR-11361) After Restarting Solr 6.6.1 Seems to cause Error if Application is Reading/Writing?

2017-09-18 Thread Erick Erickson 
Richard:

WARNING:

SOLR-11297 is on my list so I don't lose track of it. If my past
record this year is any indication there's no guarantee I'll be able
to actively work on it any time soon. All help welcome

Erick

On Mon, Sep 18, 2017 at 5:21 AM, Richard Rominger (JIRA)
 wrote:
>
> [ 
> https://issues.apache.org/jira/browse/SOLR-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169937#comment-16169937
>  ]
>
> Richard Rominger commented on SOLR-11361:
> -
>
> I've done that after the fact but then found my issue was already reported 
> and being looked into by Erick Erickson in SOLR-11297.  So I think there is 
> more than a question but a issue going on here but regardless this SOLR-11361 
> at best a duplicate.
>
>> After Restarting Solr 6.6.1 Seems to cause Error if Application is 
>> Reading/Writing?
>> ---
>>
>> Key: SOLR-11361
>> URL: https://issues.apache.org/jira/browse/SOLR-11361
>> Project: Solr
>>  Issue Type: Bug
>>  Security Level: Public(Default Security Level. Issues are Public)
>>Affects Versions: 6.6.1
>> Environment: Windows 10 VM
>>Reporter: Richard Rominger
>>  Labels: newbie, upgrade, windows
>>
>> I have just updated from Solr 6.2.1 to 6.6.1.  I put into place a fresh 
>> 6.6.1 and mounted our Core (umslogs).  This loaded perfectly fine on port 
>> 8181 and our application is able to write/read data.
>> The problem started when I restart Solr 6.6.1 and the below error appeared 
>> after Solr 6.6.1 came up accessible via the web page.
>>
>> *HttpSolrCall
>> null:org.apache.solr.core.SolrCoreInitializationException: SolrCore 
>> 'umslogs' is not available due to init failure: null *
>> Next my testing lead me to start up Solr on port 8282 that no application is 
>> connecting/reading/writing to.  On this test umslogs core loads is perfectly 
>> fine after erroring above.
>> Next my testing lead me to close +our application+ that writes/reads to Solr 
>> 8181umslogs core and shutdown Solr 8282 umslogs core.  Then  I restarted  
>> Solr back on Poret 8181 and the umslogs core loads properly and our 
>> application that that writes/reads to Solr 8181 is once again operational.
>> Our application has used Solr 4.10.x, then Solr 6.2.x okay.  Then again I do 
>> not doubt that I might have done something wrong with the 6.6.1 upgrade that 
>> is causing the above behavior
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>

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

[jira] [Commented] (SOLR-11361) After Restarting Solr 6.6.1 Seems to cause Error if Application is Reading/Writing?

2017-09-18 Thread Richard Rominger (JIRA) 

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

Richard Rominger commented on SOLR-11361:
-

I've done that after the fact but then found my issue was already reported and 
being looked into by Erick Erickson in SOLR-11297.  So I think there is more 
than a question but a issue going on here but regardless this SOLR-11361 at 
best a duplicate.

> After Restarting Solr 6.6.1 Seems to cause Error if Application is 
> Reading/Writing?
> ---
>
> Key: SOLR-11361
> URL: https://issues.apache.org/jira/browse/SOLR-11361
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Affects Versions: 6.6.1
> Environment: Windows 10 VM
>Reporter: Richard Rominger
>  Labels: newbie, upgrade, windows
>
> I have just updated from Solr 6.2.1 to 6.6.1.  I put into place a fresh 6.6.1 
> and mounted our Core (umslogs).  This loaded perfectly fine on port 8181 and 
> our application is able to write/read data.
> The problem started when I restart Solr 6.6.1 and the below error appeared 
> after Solr 6.6.1 came up accessible via the web page. 
>   
> *HttpSolrCall
> null:org.apache.solr.core.SolrCoreInitializationException: SolrCore 'umslogs' 
> is not available due to init failure: null *
> Next my testing lead me to start up Solr on port 8282 that no application is 
> connecting/reading/writing to.  On this test umslogs core loads is perfectly 
> fine after erroring above.
> Next my testing lead me to close +our application+ that writes/reads to Solr 
> 8181umslogs core and shutdown Solr 8282 umslogs core.  Then  I restarted  
> Solr back on Poret 8181 and the umslogs core loads properly and our 
> application that that writes/reads to Solr 8181 is once again operational.
> Our application has used Solr 4.10.x, then Solr 6.2.x okay.  Then again I do 
> not doubt that I might have done something wrong with the 6.6.1 upgrade that 
> is causing the above behavior 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (SOLR-11361) After Restarting Solr 6.6.1 Seems to cause Error if Application is Reading/Writing?

2017-09-18 Thread JIRA 

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

Jan Høydahl commented on SOLR-11361:


Here are instructions for signing up to the mailing list: 
http://lucene.apache.org/solr/community.html#mailing-lists-irc
Then later if it turns out to be a bug, we can create a new issue.

> After Restarting Solr 6.6.1 Seems to cause Error if Application is 
> Reading/Writing?
> ---
>
> Key: SOLR-11361
> URL: https://issues.apache.org/jira/browse/SOLR-11361
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Affects Versions: 6.6.1
> Environment: Windows 10 VM
>Reporter: Richard Rominger
>  Labels: newbie, upgrade, windows
>
> I have just updated from Solr 6.2.1 to 6.6.1.  I put into place a fresh 6.6.1 
> and mounted our Core (umslogs).  This loaded perfectly fine on port 8181 and 
> our application is able to write/read data.
> The problem started when I restart Solr 6.6.1 and the below error appeared 
> after Solr 6.6.1 came up accessible via the web page. 
>   
> *HttpSolrCall
> null:org.apache.solr.core.SolrCoreInitializationException: SolrCore 'umslogs' 
> is not available due to init failure: null *
> Next my testing lead me to start up Solr on port 8282 that no application is 
> connecting/reading/writing to.  On this test umslogs core loads is perfectly 
> fine after erroring above.
> Next my testing lead me to close +our application+ that writes/reads to Solr 
> 8181umslogs core and shutdown Solr 8282 umslogs core.  Then  I restarted  
> Solr back on Poret 8181 and the umslogs core loads properly and our 
> application that that writes/reads to Solr 8181 is once again operational.
> Our application has used Solr 4.10.x, then Solr 6.2.x okay.  Then again I do 
> not doubt that I might have done something wrong with the 6.6.1 upgrade that 
> is causing the above behavior 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (SOLR-11361) After Restarting Solr 6.6.1 Seems to cause Error if Application is Reading/Writing?

2017-09-17 Thread Richard Rominger (JIRA) 

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

Richard Rominger commented on SOLR-11361:
-

I just went and grabbed Solr 6.6.0 and unpacked.  Then I copied my umslog core 
from 6.6.1 and ran the same tests.  The problem that I am seeing in v6.6.1 does 
not appear to happen in v6.6.0

> After Restarting Solr 6.6.1 Seems to cause Error if Application is 
> Reading/Writing?
> ---
>
> Key: SOLR-11361
> URL: https://issues.apache.org/jira/browse/SOLR-11361
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>Affects Versions: 6.6.1
> Environment: Windows 10 VM
>Reporter: Richard Rominger
>  Labels: newbie, upgrade, windows
>
> I have just updated from Solr 6.2.1 to 6.6.1.  I put into place a fresh 6.6.1 
> and mounted our Core (umslogs).  This loaded perfectly fine on port 8181 and 
> our application is able to write/read data.
> The problem started when I restart Solr 6.6.1 and the below error appeared 
> after Solr 6.6.1 came up accessible via the web page. 
>   
> *HttpSolrCall
> null:org.apache.solr.core.SolrCoreInitializationException: SolrCore 'umslogs' 
> is not available due to init failure: null *
> Next my testing lead me to start up Solr on port 8282 that no application is 
> connecting/reading/writing to.  On this test umslogs core loads is perfectly 
> fine after erroring above.
> Next my testing lead me to close +our application+ that writes/reads to Solr 
> 8181umslogs core and shutdown Solr 8282 umslogs core.  Then  I restarted  
> Solr back on Poret 8181 and the umslogs core loads properly and our 
> application that that writes/reads to Solr 8181 is once again operational.
> Our application has used Solr 4.10.x, then Solr 6.2.x okay.  Then again I do 
> not doubt that I might have done something wrong with the 6.6.1 upgrade that 
> is causing the above behavior 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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