Versions Compared

Old Version 1

changes.mady.by.user Armin Franke

Saved on

compared with

New Version Current

changes.mady.by.user Armin Franke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Although a root folder may not be currently selected, tia Content Server may write to it: All component files (ArchiveLink) belonging to the same document id get stored in the same folder on the same root, for . For existing document id folders, write operations are so still possible. It does not matter, if the root is isn’t currently selected, free disc space limitation is exceeded or even the root is configured as non-selectable.

For that reason, recommendation is to configured with minimum of free disc space for each root folder, so creation of new folders stops leaving space for component file files being added latelater.

Parent

Parameter

Description

Default

<repo>.contentservice.<type>

root.<n>

These parameters set the root folders.

<n> is a sequential number starting with 1, so . So multiple root folders can be set up. (n=>0)

Each parameter must be set to a unique file system path.

Info

In order to add a new root folder, just use the next higher sequential number.

Removing a root.<n> parameter, however, results in inaccessibility of the data stored in this location.

-

<repo>.contentservice.<type>.root.<n>

freespacegb

The root folder with With this value it is possible to control the behavior of the selecting the root folderalgorithm.
-1 means the that this root folder will be skipped , (expect the one with the highest number.)
For any other value > 0 the folder will be checked if enough free disk space is available then this folder will be used. space left is checked.

The folder with the smallest number and enough free space will be used.

see also https://kgs-software.atlassian.net/wiki/spaces/DOCUEN/pages/3526557741/Multi+root+configuration+splitfilesystemv3+netappv3+icasv3#Root-Folder-Selection-Rules

-1

<repo>.contentservice.<type>.root.<n>

rootSelectionIntervalH

Time interval in hours to find a new root directory, when free space on disk is smaller than freespacegb. . The algorithm is also triggered, when an IOException occures.

see https://kgs-software.atlassian.net/wiki/spaces/DOCUEN/pages/3526557741/Multi+root+configuration+splitfilesystemv3+netappv3+icasv3#Root-Folder-Selection-Rules

12

...

Root Folder Selection Rules

Starting with smallest root.1, each configured root folder:

  1. If freespacegb for the root is -1, it is blocked by configuration for creation of new doc Id’s.

  2. If enough free space is found on the root, it is selected and selection process ends.

  3. If not enought frees pace enough free space is found, the next root folder is inspected.In case there is no other root to be processed, the last root with freespacegb limit of -1 will be written until the device is full

Note

If after inspection of all root folders no root record is selected, new documents cannot be created.

Example:

Code Block
<repo>.contentservice.splitfilesystemv3.root.1 = C:/Doc_Base 
<repo>.contentservice.splitfilesystemv3.root.2 = C:/Doc_Base_Disk2 
<repo>.contentservice.splitfilesystemv3.root.2.freespacegb=-1 
<repo>.contentservice.splitfilesystemv3.root.3 = C:/Doc_Base_Disk3 
<repo>.contentservice.splitfilesystemv3.root.3.freespacegb=10 
<repo>.contentservice.splitfilesystemv3.root.4 = C:/Doc_Base_Disk4 
<repo>.contentservice.splitfilesystemv3.root.4.freespacegb=50

...

root.3 is only used when C:/Doc_Base_Disk3 has more than 10 GB of disc space available.
root.4 is only used when C:/Doc_Base_Disk4 has more than 50 GB of disc space available and root.3 has no more space left..
In case the remaining free space on root.3 and root.4 falls below the limit configured, storing documents will no longer be possiblean exception is thrown and logged. No content can be stored.