Versions Compared

Version Old Version 9 New Version 10
Changes made by

Kyle Miller (Deactivated)

Kyle Miller (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel2

...

ID (existing feeds)

Read-only; system-assigned identifier

Status (existing feeds)

Read-only; the current feed processing state.

Name

The name you attached to a feed.

Scope

The feed filters that selected for the replication feed. The object is only replicated to the domain(s) indicated in this field.

Info

Gateway adminDomain

Never create the same domain in two clusters: always create it in the source cluster and then replicate it to the target. A Gateway must use an independent adminDomain, at least temporarily, if the Gateway is in front of the target cluster. (CLOUD-2785)
If you choose to replicate specific domains, ensure that the source cluster’s adminDomain is included in the list of replicated domains.

  • Entire source cluster (global) — To replicate all objects in the source cluster, leave the default selection of Entire source cluster (global)

  • Only objects in select domain(s) — To replicate only the objects in one or more domains, select the 'Only objects in select domain(s) option. In the text box that appears, enter one or more domains:

    • To replicate only the objects within a specific domain, enter that domain.

    • To replicate only the objects within multiple domains, enter those domains separated by commas and/or use pattern matching.

    • To exclude domains from replication, enter them. (v10.0)

The field value allows pattern matching with the Python regular expression (RE) syntax so that multiple domain names can be matched. The exception to the RE matching is that the "{m,n}" repetitions qualifier may not be used.

An example domain list value using RE is: .*\.example\.com
This matches both of these domains: accounting.example.com, engineering.example.com.

  • Include objects without a domain — To replicate any unnamed objects that are not tenanted in any domain, enable the option.

Target Remote Cluster Name

The configuration setting for your target cluster (for example, the cluster.name parameter in the .cfg file of the target cluster).

configure the Gateway setting allowSwarmAdminIP when using Gateway as target. See Gateway Configuration

Proxy or Host(s)

The IP address(es) or host name(s) of either:

  • One or more nodes in the target cluster.

  • A reverse proxy host that routes to the target cluster.

To enter two or more node IP addresses, enter each address separated by a comma or spaces.

Port

Defaults to 80. Allows specifying a custom port for the remote cluster.

Replication Mode

Defaults to Direct POST. Choose replication via direct POST (recommended) or bidirectional GET. Switching modes does not require a feed restart. (v1.2)

For best performance, choose direct POST replication, which can go through Gateway. GET replication is the legacy method, which may be needed for application compatibility or networking requirements.

Threads

Replication via direct POST only. The default replication speed (6 simultaneous threads) is best for same-sized clusters with minimal replication backlog. (v1.2)

Reduce the threads to avoid overwhelming a smaller target cluster. For faster replication against a backlog, increase the threads temporarily, monitor bandwidth and cluster performance, as boosting the speed stresses both clusters.

SSL Server

Replication via direct POST only. Defaults to none. If you are replicating over an untrusted network, enable Require trusted SSL; Allow untrusted SSL is available but not intended for production systems. (v2.0)

Remote Admin Name/Password

Inherit from source cluster: Uncheck the enabled box, only if  the remote cluster user name is different from the source cluster name in the same realm. Then enter:

User/Password credentials

  • The administrative user name of the target cluster.

  • The administrative password of the target cluster.

...

Info

Propagate Deletes

The legacy option Propagate Deletes is deprecated; it existed to let you set allow setting a target cluster to preserve all deleted objects. This need is now covered by Object Versioning; you can access historical versions of deleted objects to recover content that was deleted by mistake. You can also limit versioning to the target cluster that is serving as your archive, to minimize space usage. (v11.1)

If you have an existing feed that still has this option specified, note these restrictions and behaviors:

  • With Versioning — Always propagate deletes when using Object Versioning in your cluster.

  • Without Versioning — If this option is disabled, be aware that you are having your The target cluster maintain maintains deleted content that carries carrying no verifiable indication of its the deleted status if this option is disabled.


Excerpt

Using Feed Actions

For an existing feed, clicking on it in the Feeds list opens its Feed Settings page, with the existing settings populated. The Actions (gear) icon menu at the top right supports multiple feed actions, appropriate to the type of feed:

Pause / Resume

You may occasionally wish to pause feed processing in order to perform system maintenance. For example, when upgrading an Elasticsearch cluster, pause the search feed before stopping the Elasticsearch service in the search cluster. After completing your system maintenance, return to the action menu and select the Resume action to resume feed processing.

Refresh

As objects are written or updated, their data is sent to the feed target in near real-time (NRT). Any objects that cannot be processed immediately are retried each HP cycle until they succeed, at which point they are marked as complete and are never resent. If a data loss failure occurs on your remote feed target and you cannot restore from backup, select the Refresh option from the feed action menu, which verifies and rehydrates all of the previously sent content to a remote cluster. This process takes some time, as it must revisit all objects in the cluster.

Delete

When you delete a feed, it frees source cluster resources. This process does not affect the objects previously pushed to the remote target. To delete a feed, select the Delete option from the feed action menu and confirm you intend to permanently delete the feed. The deleted feed is removed from the remaining cluster nodes within 60 seconds. 

View feed table

Displays the SNMP Repository Dump for the selected node, for feed diagnostics (see below).

Troubleshooting Feeds

  • Feed diagnostics — To troubleshoot blocked feed, double-click it to open its settings page, click the gear icon, and select View feed table, which displays the SNMP Repository Dump for the selected node. (v2.0)

    Review the feedPluginState status to identify the blockage. 
    Example: feedPluginState blocked: Destination cluster onyx1 reports invalid request: Castor-System-Cluster value must refer to a remote cluster on RETRIEVE request

  • Idle feeds — A feed can appear to be idle with items still queued for processing. Plan for the fact that feed status reporting is a best-effort snapshot, not a low-latency or guaranteed transaction mechanism.

  • Feed prioritization — Domain and bucket context objects are prioritized for all types of feeds; this improves usability when you initiate remote sites.

  • Retries for blocked feeds — Blocked feeds are retried every 20 minutes, but if you change the definition for a blocked feed, it triggers an immediate attempt with the new definition, which might clear the blockage. (v10.1)

...