[Pdl] Product Distribution Layer - Indexing Problems

[Martinez, Eric]

We recently discovered a problem in PDL that may be causing some
installations to stop processing incoming information. This issue only
affects you if you are running an indexer (typically to automatically
trigger some process when new event information arrives) and if your
installation limits which products the indexer processes. In general, you
can check your PDL logs to see if you have SQLExceptions being thrown about
duplicate source + sourceCode rows. If this does not apply to you, you can
safely ignore this message.

We are working to correct this in the source code, but we have a
work-around available you can implement in the interim.

(1) Stop PDL
(2) Reset your receiver and indexer indexes/data. This depends on your
installation a bit, but may include the following...
   - Remove the receiver_index.dat file
   - Remove the indexer_storage data directory (configurable location)
   - Remove the receiver_storage data directory (configurable location)
   - Remove receiver_index.db (for SQLite installations)
   - Drop and re-create database (for MySQL installations)
(3) Re-configure PDL
   - If you are running an archive policy to archive superseded products,
remove that policy.
   - Ensure your indexer instance is accepting "geoserve" and
"nearby-cities" products.

Following these steps essentially clears your entire index/catalog and then
prevents the problem from re-occurring. If you are running long-term
catalogs, you will want to be much more precise with your data purges.

Specifically, you will want to purge products back as far as July 5, 2016.
Please note that depending on if/when you implement this work-around you
may not recover all purged data as PDL only recovers the past 7 days of
data.

We're sorry for this inconvenience.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://geohazards.usgs.gov/pipermail/pdl/attachments/20160711/91c7bc7a/attachment.html>