Hi There
Thanks for replying to my query. Yes I had seen the notes saying that on upgrading to a new major release the advice is to wipe and re-index. But I did see this on Major Changes in Solr 8 | Apache Solr Reference Guide 8.7 <https://lucene.apache.org/solr/guide/8_7/major-changes-in-solr-8.html> Upgrade Prerequisites If using SolrCloud, you must be on Solr 7.3.0 or higher. Solr’s LeaderInRecovery (LIR) functionality <https://lucene.apache.org/solr/guide/8_7/major-changes-in-solr-8.html#solr-7-3> changed significantly in Solr 7.3. While these changes were back-compatible for all subsequent 7.x releases, that compatibility has been removed in 8.0. In order to upgrade to Solr 8.x, all nodes of your cluster must be running Solr 7.3 or higher. If an upgrade is attempted with nodes running versions earlier than 7.3, documents could be lost. If you are not using Solr in SolrCloud mode (you use Standalone Mode instead), we expect you can upgrade to Solr 8 from any 7.x version without major issues. So I was hoping to carry out just an upgrade as our customer’s data would take 2-3 weeks to re-index from scratch. You mentioned about committing after carrying out an update. Were you referring to the running of the IndexUpgrader? This is what carried out * With solr service stopped * Open a CMD window * cd c:\solr-8.7.0\server\solr-webapp\webapp\WEB-INF\lib * "C:\Program Files\Java\jre11_0_2\bin"\java -cp lucene-core-8.7.0.jar;lucene-backward-codecs-8.7.0.jar org.apache.lucene.index.IndexUpgrader -verbose C:\solr-8.7.0\server\solr\uleaf\data\index And it generated output of the form MS 0 [2021-01-09T10:16:54.405441300Z; main]: initDynamicDefaults spins=true maxThreadCount=1 maxMergeCount=6 IFD 0 [2021-01-09T10:16:54.450123300Z; main]: init: current segments file is "segments_1s"; deletionPolicy=org.apache.lucene.index.KeepOnlyLastCommitDeletionPolicy@7d68ef40 IFD 0 [2021-01-09T10:16:54.451123400Z; main]: init: load commit "segments_1s" IFD 0 [2021-01-09T10:16:54.456124300Z; main]: init: seg=_1l set nextWriteFieldInfosGen=2 vs current=1 IFD 0 [2021-01-09T10:16:54.456727400Z; main]: init: seg=_1l set nextWriteDocValuesGen=2 vs current=1 IFD 0 [2021-01-09T10:16:54.462160900Z; main]: now checkpoint "_1i(7.7.1):C1:[diagnostics={java.vendor=AdoptOpenJDK, os=Windows 10, java.version=11.0.2, java.vm.version=11.0.2+9, lucene.version=7.7.1, os.arch=amd64, java.runtime.version=11.0.2+9, source=flush, os.version=10.0, timestamp=1609332625247}]:[attributes={Lucene50StoredFieldsFormat.mode=BEST_SPEED}] _1j(7.7.1):C16:[diagnostics={java.vendor=AdoptOpenJDK, os=Windows 10, java.version=11.0.2, java.vm.version=11.0.2+9, lucene.version=7.7.1, os.arch=amd64, java.runtime.version=11.0.2+9, source=flush, os.version=10.0, timestamp=1609335456070}]:[attributes={Lucene50StoredFieldsFormat.mode=BEST_SPEED}] _1k(8.7.0):C1:[diagnostics={java.vendor=AdoptOpenJDK, os=Windows 10, java.version=11.0.2, java.vm.version=11.0.2+9, lucene.version=8.7.0, os.arch=amd64, java.runtime.version=11.0.2+9, source=flush, os.version=10.0, timestamp=1610016791080}]:[attributes={Lucene87StoredFieldsFormat.mode=BEST_SPEED}] Ending with IFD 0 [2021-01-09T10:16:55.448195200Z; main]: now checkpoint "_1q(8.7.0):C17:[diagnostics={os=Windows 10, java.version=11.0.2, os.arch=amd64, java.runtime.version=11.0.2+9, source=merge, os.version=10.0, java.vendor=AdoptOpenJDK, java.vm.version=11.0.2+9, lucene.version=8.7.0, mergeMaxNumSegments=1, mergeFactor=2, timestamp=1610187414535}]:[attributes={Lucene87StoredFieldsFormat.mode=BEST_SPEED}] :id=i2dct7nwpvi35aycws4u8gwu _1k(8.7.0):C1:[diagnostics={java.vendor=AdoptOpenJDK, os=Windows 10, java.version=11.0.2, java.vm.version=11.0.2+9, lucene.version=8.7.0, os.arch=amd64, java.runtime.version=11.0.2+9, source=flush, os.version=10.0, timestamp=1610016791080}]:[attributes={Lucene87StoredFieldsFormat.mode=BEST_SPEED}] :id=dop9d815p1kjrk1phi955lbg8 _1l(8.7.0):C2/1:[diagnostics={java.vendor=AdoptOpenJDK, os=Windows 10, java.version=11.0.2, java.vm.version=11.0.2+9, lucene.version=8.7.0, os.arch=amd64, java.runtime.version=11.0.2+9, source=flush, os.version=10.0, timestamp=1610097123034}]:[attributes={Lucene87StoredFieldsFormat.mode=BEST_SPEED}]:delGen=1 :id=dop9d815p1kjrk1phi955lbgh _1m(8.7.0):C2:[diagnostics={java.vendor=AdoptOpenJDK, os=Windows 10, java.version=11.0.2, java.vm.version=11.0.2+9, lucene.version=8.7.0, os.arch=amd64, java.runtime.version=11.0.2+9, source=flush, os.version=10.0, timestamp=1610097143494}]:[attributes={Lucene87StoredFieldsFormat.mode=BEST_SPEED}] :id=dop9d815p1kjrk1phi955lbgg _1n(8.7.0):C1:[diagnostics={java.vendor=AdoptOpenJDK, os=Windows 10, java.version=11.0.2, java.vm.version=11.0.2+9, lucene.version=8.7.0, os.arch=amd64, java.runtime.version=11.0.2+9, source=flush, os.version=10.0, timestamp=1610097253797}]:[attributes={Lucene87StoredFieldsFormat.mode=BEST_SPEED}] :id=dop9d815p1kjrk1phi955lbgl _1p(8.7.0):C1:[diagnostics={java.vendor=AdoptOpenJDK, os=Windows 10, java.version=11.0.2, java.vm.version=11.0.2+9, lucene.version=8.7.0, os.arch=amd64, java.runtime.version=11.0.2+9, source=flush, os.version=10.0, timestamp=1610097594499}]:[attributes={Lucene87StoredFieldsFormat.mode=BEST_SPEED}] :id=dop9d815p1kjrk1phi955lbgt" [6 segments ; isCommit = false] IFD 0 [2021-01-09T10:16:55.457043500Z; main]: 10 msec to checkpoint I was not aware about the need to carry out an commit after this. Please can you show me how to do this. I checked the Index folder before and after running the tool and the number of files reduced – so it seemed to have done some ‘combining’. If I run the tool again it seems to run through similar dialog and does not report that nothing needs correcting. Also please could you confirm if my steps to upgrade a solr database to a new release are correct (just in case what I did caused this issue). * Installed windows solr 8.7.0 on my machine in a different folder * Copied the core related folder (holding conf, data, lib, core.properties) from 7.7.1 to the new 8.7.0 folder * Brought up the solr * Checked that queries work through the Solr Admin Tool and our application Many Thanks Matthew Matthew Flowerday | Consultant | ULEAF Unisys | 01908 774830| <mailto:matthew.flower...@unisys.com> matthew.flower...@unisys.com Address Enigma | Wavendon Business Park | Wavendon | Milton Keynes | MK17 8LX <http://www.unisys.com/> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all devices. <http://www.linkedin.com/company/unisys> <http://twitter.com/unisyscorp> <http://www.youtube.com/theunisyschannel> <http://www.facebook.com/unisyscorp> <https://vimeo.com/unisys> <http://blogs.unisys.com/> From: matthew sporleder <msporle...@gmail.com> Sent: 10 January 2021 21:38 To: solr-user@lucene.apache.org Subject: Re: Re:Query over migrating a solr database from 7.7.1 to 8.7.0 EXTERNAL EMAIL - Be cautious of all links and attachments. I think the general advice is to do a full re-index on a major version upgrade. Also - did you ever commit? On Sun, Jan 10, 2021 at 11:13 AM Flowerday, Matthew J <matthew.flower...@gb.unisys.com <mailto:matthew.flower...@gb.unisys.com> > wrote: Hi There Thanks for contacting me. I carried out this analysis of the solr log from the updates I carried out at the time: Looking at the update requests sent to Solr. The first update of an existing record generated 2021-01-07 06:04:18.958 INFO (qtp1458091526-17) [ x:uleaf] o.a.s.u.p.LogUpdateProcessorFactory [uleaf] webapp=/solr path=/update params={wt=javabin&version=2}{add=[9901020319M01-X11 (1688206792619720704)]} 0 59 2021-01-07 06:04:19.186 INFO (searcherExecutor-15-thread-1-processing-x:uleaf) [ x:uleaf] o.a.s.c.QuerySenderListener QuerySenderListener done. 2021-01-07 06:04:19.196 INFO (searcherExecutor-15-thread-1-processing-x:uleaf) [ x:uleaf] o.a.s.c.SolrCore [uleaf] Registered new searcher autowarm time: 1 ms 2021-01-07 06:04:19.198 INFO (qtp1458091526-23) [ x:uleaf] o.a.s.u.p.LogUpdateProcessorFactory [uleaf] webapp=/solr path=/update params={waitSearcher=true&commit=true&softCommit=false&wt=javabin&version=2}{commit=} 0 228 And the record was duplicated: The next update generated 2021-01-07 06:10:59.786 INFO (qtp1458091526-17) [ x:uleaf] o.a.s.u.p.LogUpdateProcessorFactory [uleaf] webapp=/solr path=/update params={wt=javabin&version=2}{add=[9901020319M01-X11 (1688207212953993216)]} 0 20 2021-01-07 06:10:59.974 INFO (searcherExecutor-15-thread-1-processing-x:uleaf) [ x:uleaf] o.a.s.c.QuerySenderListener QuerySenderListener done. 2021-01-07 06:10:59.982 INFO (searcherExecutor-15-thread-1-processing-x:uleaf) [ x:uleaf] o.a.s.c.SolrCore [uleaf] Registered new searcher autowarm time: 0 ms 2021-01-07 06:10:59.998 INFO (qtp1458091526-26) [ x:uleaf] o.a.s.u.p.LogUpdateProcessorFactory [uleaf] webapp=/solr path=/update params={waitSearcher=true&commit=true&softCommit=false&wt=javabin&version=2}{commit=} 0 208 Which looks the same as the previous command – so no real difference here. And then the records looked like And this shows that the original (7.7.1) item is untouched and only the 8.6.3 item is updated on subsequent updates. A brand new record being sent to solr generate this dialog 2021-01-07 06:20:10.645 INFO (qtp1458091526-25) [ x:uleaf] o.a.s.u.p.LogUpdateProcessorFactory [uleaf] webapp=/solr path=/update params={wt=javabin&version=2}{add=[9901020319M01-X15 (1688207790576762880), 9901020319M01-DI21 (1688207790587248640)]} 0 15 2021-01-07 06:20:10.798 INFO (searcherExecutor-15-thread-1-processing-x:uleaf) [ x:uleaf] o.a.s.c.QuerySenderListener QuerySenderListener done. 2021-01-07 06:20:10.802 INFO (searcherExecutor-15-thread-1-processing-x:uleaf) [ x:uleaf] o.a.s.c.SolrCore [uleaf] Registered new searcher autowarm time: 0 ms 2021-01-07 06:20:10.803 INFO (qtp1458091526-23) [ x:uleaf] o.a.s.u.p.LogUpdateProcessorFactory [uleaf] webapp=/solr path=/update params={waitSearcher=true&commit=true&softCommit=false&wt=javabin&version=2}{commit=} 0 153 And this has a similar update request line as the others – so no differences here. Solr just seems to leave the migrated records as is and just creates a duplicate when they are updated for some reason. I hope this is what you are after. Many Thanks Matthew Matthew Flowerday | Consultant | ULEAF Unisys | 01908 774830| <mailto:matthew.flower...@unisys.com> matthew.flower...@unisys.com Address Enigma | Wavendon Business Park | Wavendon | Milton Keynes | MK17 8LX <http://www.unisys.com/> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all devices. <http://www.linkedin.com/company/unisys> <http://twitter.com/unisyscorp> <http://www.youtube.com/theunisyschannel> <http://www.facebook.com/unisyscorp> <https://vimeo.com/unisys> <http://blogs.unisys.com/> From: xiefengchang < <mailto:fengchang_fi...@163.com> fengchang_fi...@163.com> Sent: 10 January 2021 08:44 To: <mailto:solr-user@lucene.apache.org> solr-user@lucene.apache.org Subject: Re:Query over migrating a solr database from 7.7.1 to 8.7.0 EXTERNAL EMAIL - Be cautious of all links and attachments. can you show the update request? At 2021-01-07 20:25:13, "Flowerday, Matthew J" < <mailto:matthew.flower...@gb.unisys.com> matthew.flower...@gb.unisys.com> wrote: Hi There I have recently upgraded a solr database from 7.7.1 to 8.7.0 and not wiped the database and re-indexed (as this would take too long to run on site). On my local windows machine I have a single solr server 7.7.1 installation I upgraded in the following manner * Installed windows solr 8.7.0 on my machine in a different folder * Copied the core related folder (holding conf, data, lib, core.properties) from 7.7.1 to the new 8.7.0 folder * Brought up the solr * Checked that queries work through the Solr Admin Tool and our application This all worked fine until I tried to update a record which had been created under 7.7.1. Instead of marking the old record as deleted it effectively created a new copy of the record with the change in and left the old image as still visible. When I updated the record again it then correctly updated the new 8.7.0 version without leaving the old image behind. If I created a new record and then updated it the solr record would be updated correctly. The issue only seemed to affect the old 7.7.1 created records. An example of the duplication as follows (the first record is 7.7.1 created version and the second record is the 8.7.0 version after carrying out an update): { "responseHeader":{ "status":0, "QTime":4, "params":{ "q":"id:9901020319M01-N26", "_":"1610016003669"}}, "response":{"numFound":2,"start":0,"numFoundExact":true,"docs":[ { "id":"9901020319M01-N26", "groupId":"9901020319M01", "urn":"N26", "specification":"nominal", "owningGroupId":"9901020319M01", "description":"N26, Yates, Mike, Alan, Richard, MALE", "group_t":"9901020319M01", "nominalUrn_t":"N26", "dateTimeCreated_dtr":"2020-12-30T12:00:53Z", "dateTimeCreated_dt":"2020-12-30T12:00:53Z", "title_t":"Captain", "surname_t":"Yates", "qualifier_t":"Voyager", "forename1_t":"Mike", "forename2_t":"Alan", "forename3_t":"Richard", "sex_t":"MALE", "orderedType_t":"Nominal", "_version_":1687507566832123904}, { "id":"9901020319M01-N26", "groupId":"9901020319M01", "urn":"N26", "specification":"nominal", "owningGroupId":"9901020319M01", "description":"N26, Yates, Mike, Alan, Richard, MALE", "group_t":"9901020319M01", "nominalUrn_t":"N26", "dateTimeCreated_dtr":"2020-12-30T12:00:53Z", "dateTimeCreated_dt":"2020-12-30T12:00:53Z", "title_t":"Captain", "surname_t":"Yates", "qualifier_t":"Voyager enterprise defiant yorktown xx yy", "forename1_t":"Mike", "forename2_t":"Alan", "forename3_t":"Richard", "sex_t":"MALE", "orderedType_t":"Nominal", "_version_":1688224966566215680}] }} I checked the solrconfig.xml file and it does have a uniqueKey set up <field name="id" type="string" indexed="true" stored="true" required="true" multiValued="false" /> <uniqueKey>id</uniqueKey> I was wondering if this behaviour is expected and if there is a way to make sure that records created under a previous version are updated correctly (so that the old data is deleted when updated). Also am I upgrading solr correctly as it could be that the way I have upgraded it might be causing this issue (I tried hunting through the solr documentation online but struggled to find window upgrade notes and the above steps I worked out by trial and error). Many thanks Matthew Matthew Flowerday | Consultant | ULEAF Unisys | 01908 774830| <mailto:matthew.flower...@unisys.com> matthew.flower...@unisys.com Address Enigma | Wavendon Business Park | Wavendon | Milton Keynes | MK17 8LX <http://www.unisys.com/> <http://www.unisys.com/> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all devices. <http://www.unisys.com/>
smime.p7s
Description: S/MIME cryptographic signature
