Dell DX6012S Руководство по установке и настройке - Страница 11

Просмотреть онлайн или скачать pdf Руководство по установке и настройке для Хранение Dell DX6012S. Dell DX6012S 43 страницы. Rack installation instructions — static rails
Также для Dell DX6012S: Дополнительное руководство (4 страниц), Инструкции по установке оборудования (2 страниц), Руководство пользователя (46 страниц), Руководство по установке и настройке (35 страниц), Руководство по началу работы (28 страниц), Уведомление (28 страниц), Уведомление (20 страниц), Обзор (19 страниц), Руководство по конфигурации (9 страниц), Руководство по конфигурации (9 страниц), Примечание к выпуску (8 страниц), Руководство по конфигурации (7 страниц), Примечание к выпуску (6 страниц), Примечание к выпуску (5 страниц), Информация о выпуске (5 страниц), Руководство по началу работы (47 страниц), Установка (2 страниц), Установка стойки (2 страниц)

Dell DX6012S Руководство по установке и настройке
The two optional DX Content Router services are designed and deployed as independent processes
running on a server. We discuss each of these services in more detail in the following sections.

3.1.2. Publisher Service

The Publisher service collects a comprehensive list of all the UUIDs stored in the cluster (as well as
those that have been deleted), filters those UUIDs, and publishes the resulting lists of UUIDs to one
or more remote Subscribers. The Publisher consists of several subcomponents:
1. Simple HTTP server
2. Attached data store
3. Filter Rules Engine
3.1.2.1. Filtering UUIDs for Publication
The Publisher traverses the list of UUIDs and evaluates one or more existence validations or simple
filter expressions against the values of certain headers in the metadata. A set of matching rules can
be configured by the administrator that will determine the topology of the intercluster network. These
rules are specified using an XML syntax, the full definition of which can be found below.
By way of an example, suppose we want to configure our local cluster to remotely replicate all
high and medium priority streams to a primary disaster recovery site, while all other streams get
replicated to a secondary DR site. The General XML rule structure to do this might look like this:
<rule-set>
<publish>
<select name="PrimaryDR"/>
<select name="SecondaryDR"/>
</publish>
Copyright © 2010 Caringo, Inc.
All rights reserved
7
Version 2.2
December 2010