Are you absolutely sure that you are starting and restarting Solr in
the same way? You could look at overview page to compare properties
and at the core/collection's overview page to check the filesystem
paths.

Regards,
   Alex.
----
http://www.solr-start.com/ - Resources for Solr users, new and experienced


On 28 March 2017 at 09:35, robg <goldf...@comcast.net> wrote:
> I have a simple Visual Studio 2013 c# application using SOLRNET to test
> indexing a document by a standalone single core SOLR instance (v6.4.1. or
> v6.4.2 running on Windows 2008 R2).
> The document class is a simple one, having only 2 fields - a c# string ID (a
> SOLR string & a unique field) and a c# string Title (a SOLR general text
> field that is tokenized and stored).
>
> After running the application to index 1 document, I can connect to the SOLR
> instance's Admin page and examine the values of the fields in the indexed
> document. If, after indexing 1 document,
> I then shutdown the SOLR instance, when I restart it I get the following
> error when I connect to the Solr instance's Admin page:
>
> SolrCore Initialization Failure:
>
> <Core Name>:
> java.lang.NumberFormatException:java.lang.NumberFormatException: Invalid
> shift value (64) in prefixCoded bytes (is encoded value really an INT?)
>
> I get the same error if i try to reload the core after indexing one doument
> via the application.
>
> The only work around is to delete the solr core's folder containing the
> index data files and replace it with one that corresponds to a new core
> where no documents have been indexed.
> I have no idea what the error indicates or how to go about diagnosing the
> problem. But there is no way i can continue to use SOLR if i have to reindex
> the many documents i expect to have
> each time i have to restart the Solr instance.
>
>
>
>
> --
> View this message in context: 
> http://lucene.472066.n3.nabble.com/Get-a-java-lang-NumberFormatException-when-initializing-a-SOLR-Core-tp4327206.html
> Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to