On Mon, Jun 3, 2013 at 2:49 PM, LifeH2O <[email protected]> wrote: > Got it! Thank you @helix :) Also can we run index-init anytime? or it is used > only one time after installation. We have enough data after upgrade.
You can run it at any time, just remember that you need to stop Tomcat to run index-init. index-init can take a long time to run, from dozens of minutes up to hours, depending on the number of your items and quantity of metadata. In case anything goes wrong, you can keep a backup of your current copy of the index, which is in [dspace]/search/. Remember, that it must correspond to your index configuration in dspace.cfg (if you didn't customize it, you're fine). There's an advanced trick you can use to reduce downtime - make a clone of your DSpace installation (especially pay attention to the mentioned browse index configuration) and do the indexing on this clone, while the live instance is running. When the indexing is complete, copy over the [dspace]/search/ directory to the production instance, which should result in a much shorter downtime. Then run index-update to add any new or changed items in the production instance to the index (since the copy was made). Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
