Solr Errors in Log - Reindexing V6.6

[Sherry Lake]

UVA upgraded our "test" Dataverse server to V6.6

After upgrading solr, and running this command:

curl http://localhost:8080/api/admin/index

while indexing.... we are seeing errors in the log file like the following:

Remote error message: Exception writing document id dataset_236400_draft to the index; possible analysis error: cannot change field "dateOfCollectionStart" from index options=DOCS_AND_FREQS_AND_POSITIONS to inconsistent index options=DOCS

I have attached a snippet of our log file with errors and other messages around those errors.

I checked the datasets that are pointed out in the log, all look OK.

Any cause for alarm?

Thanks,

Sherry Lake

University of Virginia Dataverse http://dataverse.lib.virginia.edu

[James Myers]

Sherry,

I think these errors are related to the changes in the types of those fields in solr – many were changed to dates from strings.

 

I think if you followed the upgrade order – installing a new solr 9.8.0, with the new schema.xml for v6.6 ( using the update_fields.sh script if needed), and then indexing for the first time in that solr, you shouldn’t be seeing these.

 

If you still have the old solr, or old schema.xml, or ran the new solr with the old Dataverse, etc. you could have existing indexed data that is inconsistent with the new definitions for those fields.

 

In any case, I think if you call /api/admin/index/clear before indexing, to remove all the existing solr data, these should go away.

 

-- Jim

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/dc62d12d-7607-4ab8-9946-8ccc3a8724ffn%40googlegroups.com.

[Philip Durbin]

Right, at first we had https://github.com/IQSS/dataverse/pull/11140 queued up for the release notes to tell people to clear their index.

Then, like Jim said, we ended up requiring a new version of Solr, which would have an empty index.

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/IA2P220MB198600D49E7AE7C2EAE9807CBF91A%40IA2P220MB1986.NAMP220.PROD.OUTLOOK.COM.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Sherry Lake]

Since Jim isn't on Zulip..... sent the following:

Still not working.... and now not seeing any datasets.

After upgrading to V6.6, we were getting errors in our server.log. Before I reindexed "all" (clear index), I created a new dataset. It didn't show up in the listing. The direct URLs work, shows draft record and one published, but nothing in the collection list.

So I ran api/admin/index/clear - and then reindex. And still getting the errors reported in google.

BUT now nothing shows in any collection.....

Help! Luckily this is my test server.

[James Myers]

 

I can only guess at this point – it seems that solr still has the old definitions somewhere.

 

• Restarting solr after doing the clear might help.
• Checking to make sure you have the new schema.xml - https://github.com/IQSS/dataverse/blob/50239a082e38d30efa8c9bd6cc3b76980dbba3f3/conf/solr/schema.xml#L221 with namesort defined as type=”string” is one new line to look for.)
• Recreate your solr collection1. Hopefully just restarting works, but if not, starting with a new collection1 should. I think there are solr commands that would do this, but I think you could also just delete the existing one and follow the Dataverse guides to create it again.

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/a0691ba7-53d2-4b75-8506-3a0e4317caafn%40googlegroups.com.

[Sherry Lake]

Thanks, Jim.

Looking back at my command history, looks like I used the schema.xml from the "wget" command and not our local (current) version of schema.xml.

Then ran update-fields.sh on the downloaded one, not on our local one.

Our solr is also complicated by being on a different AWS "box" than our dataverse, so I need to get my admin to re-push a new version of schema.xml.

Then will do all the clear index and re-index for solr.

I'll keep everyone posted. Luckily it is just "test". And it seems to only be solr problem. I can add datasets, just can't "see" them, but the URLs work, so they are all there.

--

Sherry

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/IA2P220MB1986DE849F197FC6E6A47548BF90A%40IA2P220MB1986.NAMP220.PROD.OUTLOOK.COM.

[James Myers]

Not sure I’m following exactly, but - one thing to note: I think that using an ‘old’ local schema.xml, even running update-fields, won’t work. Some of the fields whose type has changed aren’t in a metadata block and therefore aren’t updated by update-fields. I think it is this section where you need to make sure you have the latest: https://github.com/IQSS/dataverse/blob/b881147df59e8999bcab845dec3d43f28db66b35/conf/solr/schema.xml#L123-L243.

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/CADL9p-WwVBMJ_EqmYOYFTJNEbO1sGC%3DPHwUpw8o%2BYSvSHrsnxw%40mail.gmail.com.

[Sherry Lake]

OK:

Asking my sysadmin to restart solr... but if that doesn't work.....

To get things back on track....... 

Can I take the new V6.6 schema.xml file (from wget V6.6 release notes) and add the lines for my customized metadata block (from my old V6.5 schemal.xml)?

I'll also look at the section you link to, to find missing lines.

I've done this before in previous upgrades since we have had a customized metadata block for a couple of years. My head is swimming with so many things as I try to wrap up and retire 

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/IA2P220MB19866D9390D1327EA23769B1BF90A%40IA2P220MB1986.NAMP220.PROD.OUTLOOK.COM.

[James Myers]

You should be able to take the 6.6 schema and run update-fields.sh on that.

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/CADL9p-VCEkdFeioDAoB1gyCa%2BMuLQ%2BxNOwnhzRqd-LcJHAu%2Bnw%40mail.gmail.com.

[Sherry Lake]

Thanks, Jim.

Ok, datasets now showing. Not sure what the problem was, but Tim (my sysadmin, not my cat... who is also called "Tim")
"reloaded the core" (not sure what that is)
and reindexed.

I am seeing existing datasets and new ones.

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/IA2P220MB19864CB04DF25A87C47E1B77BF90A%40IA2P220MB1986.NAMP220.PROD.OUTLOOK.COM.