Note: this is an abstract component, that cannot be instantiated.
The Distribution Partition defines a partition for a distribution algorithm.
A distribution algorithm splits a subtree into several partitions. Each partition has an identifier which is unique throughout all the topology of servers. This means that when two distributions are configured on two servers and they are referring to the same data partition, they must refer to that partition using the same partition identifier. This is a requirement because indexes can be replicated between servers. Each partition has its own parameters. The partition parameters depend on the type of the partition. For example, partition parameters for a numeric distribution consist of a lower boundary and upper boundary. Each partition is mapped to a workflow element. The workflow element mapped to the partition can be of any type (load balancer, final workflow element) but from the partition perspective the workflow element is a data container.
The following Distribution Partitions are available in the server :
These Distribution Partitions inherit from the properties described below.
The following components have a direct AGGREGATION relation FROM Distribution Partitions :
The following components have a direct COMPOSITION relation TO Distribution Partitions :
A description of each property follows.
| Basic Properties: | Advanced Properties: |
|---|---|
| ↓ partition-id | ↓ criticality |
| ↓ workflow-element |
| Description | Identifies the partition. The partition identifier is unique for a given data partition. The identifier is an integer. |
|---|---|
| Default Value | None |
| Allowed Values | An integer value. Lower value is 0. |
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | None |
| Advanced Property | No |
| Read-only | Yes |
| Description | The workflow element which contains the partition. |
|---|---|
| Default Value | None |
| Allowed Values | The DN of any Workflow Element. |
| Multi-valued | No |
| Required | Yes |
| Admin Action Required | None |
| Advanced Property | No |
| Read-only | Yes |
| Description | The criticality determines whether a partition must be up, or if it is acceptable to have it down during search operations. This parameter is meaningful only for search requests. If the partition's workflow element is fully saturated, the behavior is based on the criticality parameter: - TRUE: the partition is critical, the search operation is stopped and an UNAVAILABLE result code is returned to the client. - PARTIAL: the partition is partially critical, the search operation continues with other partitions involved in the search. The entries which are retrieved from healthy partitions are returned to the client. A result code of ADMIN_LIMIT_EXCEEDED is returned to the client, which indicates that the entries returned may be incomplete because one or more partitions are fully saturated. - FALSE: the partition is not critical, the search operation continues with other partitions involved in the search. The entries which are retrieved from healthy partitions are returned to the client. No special result code is returned to the client. |
|---|---|
| Default Value | true |
| Allowed Values | false - The partition is not critical. partial - The partition is partially critical. true - The partition is critical. |
| Multi-valued | No |
| Required | No |
| Admin Action Required | None |
| Advanced Property | Yes |
| Read-only | No |