• DX Storage guarantees data integrity during named object updates by computing an internal
signature for each part of the fully qualified path and comparing it to the old signature for the
object. If the signatures do not match, DX Storage returns an error and rejects the change.
• Read response time has been significantly improved from the previous release.
• The time required to retire a volume has significantly improved.
• DX Storage is compatible with jumbo frames using the networkMTU parameter in node.cfg. For
more information, see the DX Object Storage Administration Guide.
• The unused SNMP volMaxstreams variable has been deprecated from the SNMP Management
Information Base (MIB).
• Traceback errors reported in the log due to incorrect processing of hardware monitoring results
have been resolved.
• An issue that reported retired or unavailable volumes as stale has been resolved.
• The embedded Linux kernel configuration has been upgraded to version 2.6.33.7. Drivers that are
marked as "experimental" or "highly experimental" are excluded.
• An issue with SCSP COPY using integrity seals has been resolved.
• False announcement level messages related to errors installing the volPlugin during multi-server
configuration have been removed.
• Multiple, disjoint range reads are now supported. See the DX Object Storage Application Guide
for more information.
• Fixed an issue with automatic volume scanning on certain desktop hardware. These desktop
systems had with multimedia card slots that appeared as disk drives when no media was loaded.
1.3. Upgrading from the Previous Version
This section discusses available upgrade strategies:
• To speed updates and accesses to anchor streams and named objects, DX Storage version 5.0
uses 28% more RAM for its UUID index. Using the default memory configuration parameters, a
node with 1GB of RAM can store up to about 14 million objects.
• You cannot downgrade DX Storage after you upgrade from a pre-5.0 release and create named
objects. Named objects include tenants, buckets, or objects. You cannot downgrade even if you
delete all objects first.
• To upgrade to a DX Storage release 4.0 or later on a cluster with nodes running a DX Storage
version earlier than 4.0, you must upgrade all nodes in the cluster and reboot the cluster.
This is due to the introduction in version 4.0 of persistent settings, which is not compatible with a
mixed-version cluster.
• If any node in your cluster runs a DX Storage version earlier than 5.0, do not create a domain in
that cluster. Doing so results in unpredictable performance because of various internal changes
made in version 5.0.
• To upgrade from version 4.0 to a later 4.x version, a single cluster can contain nodes running
mixed 4.x versions. In addition, data stored with the previous version is completely compatible
with version 5.0; no data conversion is necessary.
Copyright © 2010 Caringo, Inc.
All rights reserved
2
Version 5.0
December 2010
Sayfayı Yazdır