By MicroStrategy Sdobbs
There are two types of fences:
- User Fence: used to process requests from a list of specified users or user groups.
User fences can be further limited by specifying applicable projects. - Workload Fence: used to run subscriptions triggered by an event or time-based
schedule for specified projects. Note that on-demand event subscriptions such as run
immediately, preview, or personal view are not included. For more information on
subscriptions, see Scheduling reports and documents: Subscriptions, page 490.
For example, a user fence could be configured for users who require more processing
power or high availability. Conversely, a workload fence, could be configured to limit the
resources for lower priority subscriptions.
Typically, the majority of the nodes in a cluster will not be part of a fence, making them
available for general use. All configured fences are defined in a single list ordered by
precedence. When a request is received, the ordered list of all fences and their
configurations are assessed to determine if the request matches any fence configuration.
A request will be processed by the first fence found with an available node in the ordered
list where the request matches the fence criteria.
Note the following:
power or high availability. Conversely, a workload fence, could be configured to limit the
resources for lower priority subscriptions.
Typically, the majority of the nodes in a cluster will not be part of a fence, making them
available for general use. All configured fences are defined in a single list ordered by
precedence. When a request is received, the ordered list of all fences and their
configurations are assessed to determine if the request matches any fence configuration.
A request will be processed by the first fence found with an available node in the ordered
list where the request matches the fence criteria.
Note the following:
- When all nodes in the cluster are part of the fence list, the request will be sent to
node in the last fence in the ordered list. - Fencing is not supported with legacy clients which includes MicroStrategy
Developer and administration tools such as Command Manager.
Consider the following figure which shows a clustered implementation with eight nodes:
- Nodes 7 and 8 are defined in the “CXO” user fence, meaning that these nodes are reserved for requests from users in the CXO group.
- Nodes 5 and 6 are defined in the “DistSvcs” workload fence, meaning that these nodes are
reserved for processing subscriptions that are not on-demand events. - Nodes 1, 2, 3, and 4 are not defined in a fence, meaning that they are available to
process requests that do not meet the criteria of either fence.
When user fences are configured with a cluster that has projects that are only loaded on
specific nodes, users are always sent to a node that supports the project. The first fence
found in the priority list that includes a node where the requested project is loaded will
be used.
specific nodes, users are always sent to a node that supports the project. The first fence
found in the priority list that includes a node where the requested project is loaded will
be used.
Configuring fences
Using Command Manager, you can modify, create, list, and delete fences without restating the clustered Intelligence Servers. In order to configure your fences, you must have properly configured your Intelligence Server and all the modes in the cluster must user the same server definition.
You can login to Command Manager as a user that has the DssPriviliedgesConfigureServerBasic privilege, which is a default privilege for the Server Resource Setting Administrators group.
To configure fences, use the script outlines that are provided in Command Manager to assist with the configuration. The scripts can be found in the Fences_Outline folder.
For detailed information about clustering MicroStrategy Servers, see Clustering several MicroStrategy Servers in the System Administration Guide.
New in 10.4: Reserving nodes with Work Fences: There are two types of fences: User Fence: used to process requests from a list of specified users or user groups. User fences can be further limited by specifying applicable projects. Workload Fence: used to run subscriptions triggered by an event or time-based schedule for specified projects. Not…