Dell DX6004S Panduan Penyiapan dan Konfigurasi - Halaman 24

Jelajahi secara online atau unduh pdf Panduan Penyiapan dan Konfigurasi untuk Penyimpanan Dell DX6004S. Dell DX6004S 43 halaman. Document
Juga untuk Dell DX6004S: Panduan Tambahan (4 halaman), Panduan Pengguna (46 halaman), Panduan Instalasi dan Konfigurasi (35 halaman), Panduan Memulai (28 halaman), Pemberitahuan (28 halaman), Pemberitahuan (20 halaman), Ikhtisar (19 halaman), Panduan Konfigurasi (9 halaman), Panduan Konfigurasi (9 halaman), Catatan Rilis (8 halaman), Panduan Konfigurasi (7 halaman), Catatan Rilis (6 halaman), Catatan Rilis (5 halaman), Catatan Rilis (5 halaman), Panduan Memulai (49 halaman)

• Working: the subscriber is available and actively processing streams

• Offline: the subscriber has not contacted the DX Content Router Publisher node within the

expected configurable frequency

• Idle: the subscriber is available but is not currently processing any streams

• Busy: the subscriber is currently processing a republish action and is not available for

additional republish actions

• Paused: the subscriber is actively processing streams and is not taking additional input

• Context: the descriptive name for an subscriber instance of a particular channel. For Replicator

Subscribers this name is always the same but it is customizable for other types of Subscribers.

• Host: the subscriber client's server IP address; Note if using an alias IP address the displayed

IP will be for the host server, not the alias on the server.

• Version: the DX Content Router software version for the enumerator client

• Uptime: the amount of time elapsed since the subscriber's last reboot

• Stream Events Matched: the number of stream events (writes, updates, and deletes including

retries) that match the subscriber's specification, including channel and start/end interval if

applicable. This will be a subset of the Publisher's Stream Events Found, depending on which

of the stream events match the configured filter rules.

• Backlog: The total number of found streams events that a subscriber may be interested in but

has not completed processing yet. If there is a non-zero backlog, this is broken down further as

follows:

• Transmit Queue: the number of stream events (writes, updates, and deletes) that have been

identified but have not yet been retrieved by the subscriber

• Subscriber Queue: the number of stream events (writes, updates, and deletes) that have

been retrieved by the subscriber but not yet processed.

• Subscriber in Progress: the number of stream events (writes, updates, and deletes) that are

currently being processed by the subscriber.

• Dropped: the number of stream events that could not be processed by the subscriber. For

Replicator, events may end up with a Dropped status if:

• The source cluster is unavailable or unreachable due to configuration or network connectivity

issues and objects cannot be replicated

• An object has been deleted in the source cluster so it is no longer available for replication, but

the delete event has not yet been processed by the Publisher/Replicator

• A lifepoint has deleted the object in the source cluster so it is no longer available for

replication

In all these cases, Replicator will keep attempting to replicate streams for a configurable

amount of time (4 days by default) and only consider events dropped after that time. If there is

known delete activity that accounts for the Dropped events, no further action is necessary. If

Version 2.2

December 2010