...
If the root folder is configured as /opt/fews/ the catalogue data will be stored in /opt/fews/catalogue.
I a lot of cases this will be Usually this is a folder on a mounted drive. If the connection between the mounted drive and archive server fails to often this might result in "all shards failed errors"
...
This will usually resolve the errors, but if the connection between the mounted drive and the archive is still to too unreliable the errors will return.
...
Below an configuration example (archiveServerConfig.xml) is shown.
| Code Block |
|---|
<arc:archiveServer xmlns:arc="http://www.wldelft.nl/fews/archive" xsi:schemaLocation="http://www.wldelft.nl/fews/archive http://fews.wldelft.nl/schemas//version1.0/archive-schemas/archiveServer.xsd" xmlns="http://www.wldelft.nl/fews/archive" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<archiveEnvironmentName>My environment</archiveEnvironmentName>
<catalogueIndexFolder>d:\archive\cataloguefolder</catalogueIndexFolder>
<arc:baseUrlFileServer>http://localhost:8080/thredds/fileServer/Archive</arc:baseUrlFileServer>
<arc:baseUrlArchiveRootFolder>file:///d:\fews\archive</arc:baseUrlArchiveRootFolder>
</arc:archiveServer>
|
The tag catalogueIndexFolder can be used to configure a custom location for storing the archive data.
If the all shards failed error occur too often it is better to store the catalogue data at a local disk.
By using the option catalogueIndexFolder a custom folder at a local disk can be configured.
The following steps are required to apply solution 2:
- stop the archive server,
- remove the old catalogue folder (root folder/catalogue),
- configure a custom (local) location for the catalogue folder,
- create the folder which is configured in the archiveServerConfig.xml and check that the user which runs the archive server has read/write access to this folder,
- start the archive server,
- start the clean catalogue task,
- rebuild the archive build by running the harvester.