I guess the surprising thing was that the count was the same. It should have been smaller, and growing, no? I just redeployed and noting is happening in the log files. SO I presume there is no indexing going on, right?
On Mon, Feb 22, 2016 at 3:12 PM, Tim Donohue <[email protected]> wrote: > Hi Jose, > > The indexing process is quick (within reason). So, you'll never actually > see any numbers hit zero. > > What you should see though is a long list of index messages in your dspace > log file....things like: > > 2016-02-21 00:03:02,750 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Item: 10673/4 to Index > 2016-02-21 00:03:03,374 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Item: 10673/4 to Index > 2016-02-21 00:03:05,280 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Item: 10673/3 to Index > 2016-02-21 00:03:06,506 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Item: 10673/3 to Index > 2016-02-21 00:03:07,602 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Item: 10673/6 to Index > 2016-02-21 00:03:08,448 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Item: 10673/6 to Index > 2016-02-21 00:03:09,528 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Item: 10673/5 to Index > 2016-02-21 00:03:10,427 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Item: 10673/5 to Index > 2016-02-21 00:03:11,678 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Item: 10673/7 to Index > 2016-02-21 00:03:12,050 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Item: 10673/7 to Index > 2016-02-21 00:03:12,062 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Collection: 10673/2 to Index > 2016-02-21 00:03:12,710 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Collection: 10673/2 to Index > 2016-02-21 00:03:12,837 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Collection: 10673/8 to Index > 2016-02-21 00:03:13,142 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Collection: 10673/8 to Index > 2016-02-21 00:03:13,195 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Community: 10673/1 to Index > 2016-02-21 00:03:13,692 INFO org.dspace.discovery.SolrServiceImpl @ Wrote > Community: 10673/1 to Index > > But, as you can tell from the timestamps of those example messages...the > actual indexing process is quite rapid (several objects per second), which > is why you'll never see that zero count. > > It's also worth noting that, as of 5.x, during an upgrade a reindex is > triggered *automatically*. This means that before you run 'index-discovery > -b' you might want to be sure to check your logs to see if the index > process is already occurring. By default, whenever the database changes > (which occurs in most every major release), all content will be > auto-reindexed. > > In summary, check your logs to see if the indexing is going on. If there > are errors there, then pass them along on this list. But, if you are just > seeing those "Wrote __ to Index" messages, then everything is working > correctly. > > - Tim > > > > On 2/22/2016 1:04 PM, Jose Blanco wrote: > > I'm in the middle of an upgrade right now, and any help would be most > welcomed. > > I'm running: > ./dspace index-discovery -b > > and I can see the index being updated in the correct dir > solr/search/data/index > > but the browser is not changing, which confuses me. It still show all the > items, it's as if indexing is not going on. I would expect the counts to > go down to 0 and then increase. Is it possible that the old index segment > is left alone, until the idexing completes and then a swap is done? > > Does it resolve the item using the handle? > > On Fri, Feb 19, 2016 at 5:50 PM, helix84 <[email protected]> wrote: > >> You can only run index-discovery while Solr is up. >> >> -b is the better choice as it will clear and rebuild the index, >> whereas -f reindexes existing items (Solr documents). >> >> >> Regards, >> ~~helix84 >> >> Compulsory reading: DSpace Mailing List Etiquette >> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette >> > > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > > > -- > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
