• Replication with Non-default SCSP Ports DX Content Router installations configured either to
use an SCSP Proxy or a source DX Storage cluster with a non-default SCSP port may experience
replication difficulties. The default SCSP port of 80 is recommended when using DX Content
Router version 2.2.
• Anchor Streams in a Mirrored Configuration Updates and/or deletes to the same anchor
streams in both the source cluster and a target cluster simultaneously in a mirrored configuration
are not supported.
• Offline Logging DX Content Router does not currently log an error when the errorOfflineAfter
threshold has been reached for a subscriber. This does not impact the correct reporting of the
offlineAfter or timeout parameters.
• Metadata Enumeration Error Metadata enumeration may return a 500 error on a 'Next' request
if rules filtering has not completed prior to the request being made. Administrators can determine
if filtering has completed by searching an INFO level syslog for a message containing 'unfiltered'
and ensuring it has a count of 0. This limitation will be resolved prior to production release.
• Uninstall/Reinstall Uninstalling the DX Content Router software and then reinstalling it is
not supported, as the configuration files will not get properly reinstalled. Customers wishing
to upgrade their DX Content Router software should either upgrade via the standard OS tools
or uninstall the previous version, move all configuration files (publisher.cfg, replicator.cfg,
and rules.xml) elsewhere on the server, install the new software version and then move the
configuration files back to the correct location.
1.4. Upgrading DX Content Router
The following provides an overview of upgrade instructions. Please reference the Setup and
Configuration Guide for full details.
1.4.1. Upgrading from 1.x
Installations with a previously installed Ubuntu-based version of DX Content Router have two
upgrade options. Administrators with replication downtime tolerance may choose to stop all DX
Content Router processes, install Red Hat Enterprise Linux (RHEL) 5.5 over Ubuntu on the
existing DX Content Router Publisher and Replicator servers and then install and start both DX
Content Router services again on both servers. For environments with no downtime tolerance,
administrators may wish to install Red Hat 5.5 and DX Content Router on a second, parallel set of
Publisher and Replicator servers and then wait for the Publisher 'Stream Events Found' count on the
Publisher console to match the count on the Ubuntu installation. After the counts match, the Ubuntu
Publisher and Replicator servers can be decommissioned.
Regardless of the chosen upgrade path, administrators must upgrade DX Storage to 4.0 or later
prior to upgrading DX Content Router to ensure compatibility. Administrators should temporarily
raise the Multicast Frequency to 50% from the Setting popup on the DX Storage admin console
to support faster population of the Publisher data store. Depending on the size of the source DX
Storage cluster, it may take several days for the Publisher data store to fully populate. Please
contact your designated support resource if you have further questions about upgrading DX Content
Router.
1.4.2. Upgrading from 2.x
Prior to upgrading administrators must upgrade their operating system version to Red Hat 5.5.
Installations with a 2.0 or 2.1.x RedHat-based version of DX Content Router may then install the
new 2.2 rpm over the previous version using the same rpms and install scripts used for initial
Copyright © 2010 Caringo, Inc.
All rights reserved
2
Version 2.2
December 2010
Друкувати сторінку