Chapter 1. Version 2.2
1.1. Introduction
The DX Content Router provides disaster recovery, backup, and content distribution services among
multiple DX Storage clusters separated by wide area network links. These release notes contain
late-breaking information about DX Content Router 2.2.
1.2. Changes in Release 2.2
This release enhances and extends the previous major release of DX Content Router in the
following ways:
• DX Content Router has been updated to replicate named objects written by a version 5.0 or later
DX Storage cluster. Complete enumeration of named objects across all enumeration types will be
added in a future release; a metadata enumerator will return named objects in version 5.0.
• The UUID and Event enumerators now return the alias UUID for anchor objects rather than the
internal revision UUID returned by previous versions of DX Content Router. The alias UUID may
be returned multiple times in the results for each enumerator if there are update or delete events
for the object after its initial creation.
• DX Content Router is now certified to install and run on Red Hat Enterprise Linux 5.5. Installations
must upgrade to this operating system version prior to installing or upgrading to version 2.2.
• A sync token has been added to the Publisher API that increases transmission reliability by
allowing for Publisher confirmation that the last request was successfully received by the
subscriber prior to the next set of UUIDs being sent. Please reference the 'Enumerator API'
appendix for full details of the added token.
• DX Content Router now supports verification of the DX Storage version at boot time to ensure
version compatibility. This feature requires all new and existing customers to add either the
'scsphosts' parameter (for static location) or the 'cluster' parameter (for dynamic identification).
Please reference the DX Content Router Configuration Appendix for full details of these
parameters.
• Log files are now correctly rotated based on configured parameters when file-based logging is
configured.
• A new Publisher configuration parameter is available that determines whether Enumerator
API query argument syntax is strictly enforced on requests to the Publisher. By default, invalid
arguments and values are tolerated by dropping the value and sending a warning message to
the log. Enabling the checking is helpful when developing new subscribers though as it provides
immediate feedback on error conditions. Please reference the Configuration appendix of the
Setup and Configuration Guide for complete details on the parameter.
1.3. Limitations of this Release
These are the known issues and operational limitations that exist in this release of DX Content
Router.
• Anchor Stream Update Timing Confirmation of an anchor stream update in the Publisher
Console takes longer than a regular stream. The Publisher Console backlog counts will take a
minimum of 5 minutes to reflect an anchor stream update.
Copyright © 2010 Caringo, Inc.
All rights reserved
1
Version 2.2
December 2010
Друкувати сторінку