Child pages
  • Viewing Cluster Feeds
Skip to end of metadata
Go to start of metadata


When you click Feeds in the Admin Console, the Cluster Feeds page appears. Feeds is an object routing mechanism in the Netmail Store storage cluster that uses intermittent channel connections to distribute data to one or more targeted storage clusters.

On this page:

 

Using Feeds, you can replicate:

  • Indexing content from the source cluster to the indexer.
  • Objects from the source cluster or a particular domain to a targeted cluster.

See Implementing Feeds for more information about Feeds.

The following table describes the columns on the Cluster Feeds page.

ColumnDescription
Feed Name / Feed ID

The name of the feed and its corresponding number that uniquely identifies the feed.

Max Estimated Processing Time

The estimated time required to process and clear the current backlog of replication feeds based on the last 60 minutes.

This estimate assumes that conditions do not change.

Avg Objects / Min

The average number of objects processed per minute based on the processing rate during the last 60 minutes.

Nodes ReportingThe number of cluster nodes that sent feed reports to be aggregated.

Each feed provides color status indicators that shows its current state. The following table describes the status colors and corresponding states for indexing and replication feeds.

ColorStateDescription
GreenOK

The feed replicated successfully to the targeted indexer server or cluster node.

GrayPausedThe feed is suspended because of an ongoing FVR on the node.
OrangeBlocked

The destination node or cluster is offline or not accepting feeds.

For Indexing feeds, the Indexing Service may be offline. For Replication feeds, the remote cluster may be offline.

RedConfig ErrorThe feed is misconfigured.

Indexing Feed

The Indexing Feed window provides the statistics for feeds sent to the Indexing cluster nodes. A typical configuration will only have one Indexing feed.

When an issue occurs for a particular Indexing feed, Netmail Store logs a critical message and updates the status color and state in the window so you can quickly identify a problem.

The following table describes the boxes and fields that appear in the maximized Indexing Feed window. See Configuring Feeds for information about configuring Indexing feeds in your cluster.

ColumnDescription
Node Feed State

The current feed processing state to the Indexing cluster nodes. The state can be:

  • OK. Operating normally.
  • Paused. Temporarily paused due to volume recovery.
  • Blocked. Blocked due to a transient condition. The Node Plugin State will indicate Blocked as well (see below).
Node Plugin State

The HTTP transaction state to the indexing server.

Nodes Reporting

The number of nodes and their corresponding IP address that contributes to the aggregate report.
If the Indexing nodes reported successfully, they appear together as a group. If one or more nodes did not report successfully, they appear in separate rows with their corresponding feed state.
Each IP address hyperlinks to the SNMP Repository Dump page for the reporting node, which provides node-specific detail for each feed.

Aggregated Object Processing

Provides the aggregated statistics for new or updated objects. These statistics include:

  • Pending Evaluation. Objects that must be evaluated before they are assigned to the indexing feed.
  • Unprocessed. Objects queued for processing by the indexer.
  • Successes. Objects indexed by the indexer.
  • Retrying. Objects that were rejected by the indexer server due to a server or network problem. These objects will continue to be transmitted until they are accepted by the indexer.
Aggregated Delete Processing

Provides the aggregated statistics for deleted objects. These statistics include:

  • Pending Evaluation. Object deletes that do not belong to the indexing feed.
  • Unprocessed. Object deletes queued for processing by the indexer.
  • Successes. Object deletes indexed by the indexer.
  • Retrying. Object deletes that were not processed by the indexer due to a server or network problem. The object deletes will continue to be transmitted until they are processed by the indexer.

Replication Feed

The Replication Feed window provides the statistics for a replication feed to a targeted cluster. A typical configuration can have more than one replication feed, depending on your configuration.

When an issue occurs for a particular Replication feed, Netmail Store logs a critical message and updates the status color and state in the window so you can quickly identify a problem.

The following table describes the boxes and fields in the Replication Feed window. See Configuring Replication Feeds for information about configuring Replication feeds in your cluster.

ColumnDescription
Node Feed State

The current feed processing state to the Replication cluster.

  • OK. Operating normally.
  • Paused. Temporarily paused due to volume recovery.
  • Blocked. Blocked due to a transient condition. The Node Plugin State will indicate Blocked as well (see below).
Node Plugin State

The HTTP transaction state to the Replication cluster. The state can be:

  • Idle. No pending work or replication at this time.
  • Gathering. Gathering replication entries for a future request.
  • Replicating. Processing ongoing requests to the destination cluster.
  • Blocked. Waiting for a transient error to clear. (See below.)
  • Permanent Error. Permanently stuck due to configuration errors.
Nodes Reporting

The IP addresses of each reporting node that contributes to the aggregate report.
If all target cluster nodes reported successfully, they appear together as a group. If one or more nodes did not report successfully, they appear in separate rows with their corresponding feed state.
Each IP address hyperlinks to the SNMP Repository Dump  page for the reporting node, which provides node-specific detail for each feed.

Aggregated Object Processing

Provides the aggregated statistics for new or updated objects. These statistics include:

  • Pending Evaluation. Objects that must be evaluated before they are assigned to the replication feed.
  • Unprocessed. Objects queued for processing by the target cluster.
  • Successes. Objects replicated by the target cluster.
  • Retrying. Objects rejected by the target cluster due to a server or network problem. These objects will continue to be transmitted until they are accepted by the target cluster.
Aggregated Delete Processing

Provides the aggregated statistics for deleted objects. These statistics include:

  • Pending Evaluation. Object deletes received but not evaluated by the target cluster.
  • Unprocessed. Object deletes queued for processing by the target cluster.
  • Successes. Object deletes replicated by the target cluster.
  • Retrying. Object deletes that were not processed by the target cluster due to a server or network problem. The object deletes will continue to be transmitted until they are processed by the target cluster.
  • No labels