Hello !
I'm going deeper into the mystery...
There is something wrong in my configuration or with solr because segments
merging never work as it should.
Example (step by step) :
* I clear my index.
* I had entries one by one. No problem when looking at items ; all fields are
ok -if no segments merging is done-.
* When segments merging is done, the fields of my entries go wrong ! For
example, here is the result of a query :
- before merging (ok ; all item_id equals is_nid) :
{
"response":{"numFound":3,"start":0,"docs":[
{
"item_id":"84",
"is_nid":84},
{
"item_id":"85",
"is_nid":85},
{
"item_id":"87",
"is_nid":87}]
}}
- after merging (wrong ; look at the second item where item_id <> is_nid and
the good number is is_nid) :
{
"response":{"numFound":3,"start":0,"docs":[
{
"item_id":"84",
"is_nid":84},
{
"item_id":"87",
"is_nid":85},
{
"item_id":"87",
"is_nid":87}]
}}
Here are links to my configuration files if it helps...
https://www.dropbox.com/s/pn19va6ss6n2gql/solrconfig.xml?dl=0
https://www.dropbox.com/s/9sjo7q1zi1y1o1k/schema.xml?dl=0
Best Regards,
Y. Alméras
Le mardi 7 mai 2019, 15:25:13 CEST Shawn Heisey a écrit :
> On 5/7/2019 5:28 AM, Alméras Yannick wrote:
> > I don't understand a problem on my ubuntu 18.04 solr server (version
> > 7.6.0)...
> >
> > When merge of segments is called, there is an error and then, the index is
> > not writable. The logs of a failed segments merging are at the end of
> > this message (here, I forced the merge but it's the same without
> > forcing).
> >
> > How can I debug this ? I don't understand the cause of the following error
> >
> > java.lang.IllegalArgumentException: terms out of order: priorTerm=[6e 61
> > 64 69 6e 65 2e 76 61 6c 61 64 65 5f 33 35 32 37],currentTerm=[6e 61 64 69
> > 6e 65 2e 76 61 6c 61 64 65 5f 33 35 32 37]"
> >
> > Another thing : I can't reproduce the bug on archlinux with the same
> > configuration of solr server (version 7.6.0)... ????
>
> Are the two systems running different Java? What vendor and version of
> Java is on each server? Knowing the vendor is very important. Some of
> this information is on the admin UI dashboard, and you can get
> definitive information by running "java -version" at the commandline.
> Since it is easy to have multiple Java versions on a system, and only
> one of those versions is likely the be accessible via the system PATH,
> you need to make sure you're running the right one.
>
> Can you share the entire solr.log file that contains the problem, so we
> can see the entire sequence of errors?
>
> You won't be able to attach the log to an email message. The mailing
> list filters out most attachments. You'll need to use a file sharing site.
>
> Normally I would say there's nothing sensitive in the log, but people
> disagree with that all the time. If you do redact anything, please do
> so sparingly, and do it in a way that we can tell redacted things apart
> from each other.
>
> Thanks,
> Shawn
