github aerospike/aerospike-server 5.3.0.2

latest releases: 7.2.0.3, 7.1.0.9, 7.0.0.18...
2 years ago

Aerospike Server Community Edition 5.3.0.2

Description

  • Downgrading from Aerospike Database version 5.2 or newer to a version previous to 5.2 (where XDR bin shipping has been used). Refer to Special Upgrades.
  • The Cross-Datacenter Replication (XDR) feature now includes the ability to filter using Expressions.
  • ATTENTION: Debian/Ubuntu users - if python2 is not installed, see the Python Package Dependency for .deb Installers article.
  • Support for the XDR bin-policy value 'only-specified', has been removed. Users of 'only-specified' will likely want to switch to 'changed-and-specified'.
  • Aerospike Server version 5.1 or later requires the operating system distribution's libcurl shared object library.
  • Before upgrading to 5.0.0.4 or later, customers already running 5.0.0.3 in a cluster which is an active XDR destination (i.e. an XDR destination also acting as a source XDR or that may in the future act as a source XDR), may want to consider stopping all XDR traffic to the cluster. (Enterprise Only)
    • In the unlikely case of an upgraded 5.0.0.4 or newer node going down while 5.0.0.3 nodes are still running, those nodes would mistakenly ship XDR writes even if forward has not been explicitly enabled. 
    • Enterprise Licensees may contact Aerospike Support for any questions before upgrading.
  • Cross-Datacenter Replication (XDR) running in Aerospike Server version 5.0 or newer can only connect to XDR destination clusters running versions 4.1 or newer.
  • All nodes must be upgraded to Aerospike Server version 4.9.0.7 or newer. Please upgrade to the latest 4.9.0.x release prior to upgrading to Aerospike Server version 5.0 or newer.
    • Aerospike Server version 5.0 or newer will not form a cluster with version 4.8 nodes or earlier.
    • When upgrading the Aerospike Server refer to the Special Upgrades documentation.
  • The Aerospike Server will not start if obsolete configuration parameters are set in the Aerospike configuration file (aerospike.conf).
  • ATTENTION: As of Aerospike Server version 4.9, expirations and evictions are disabled by default.

New Features

  • Enterprise Only
    • [AER-6300] - (XDR) Added expression filtering for XDR.

Improvements

  • Enterprise & Community
    • [AER-6329] - (BALANCE) Clear irrelevant cluster-related information on non-roster and orphaned nodes.
    • [AER-6296] - (CDT) Added check for duplicate keys in unordered maps.
    • [AER-5852] - (CLUSTERING) tip-clear info command must specify seed as it was configured (DNS name or IP address).
    • [AER-6297] - (CLUSTERING) Added heartbeat context configuration item connect-timeout-ms to enable multi-site clustering with round trip latency more than 100 ms.
    • [AER-6333] - (CLUSTERING) Stop heartbeat on shutdown, to get node kicked out of the cluster in case it was not quiesced and shutdown takes a long time.
    • [AER-6342] - (CLUSTERING) Periodically re-resolve inactive seeds that were configured by DNS name.
    • [AER-6320] - (EXPRESSIONS) Added as_exp_memory_size() operation to use a record's data-in-memory size in expressions.
    • [AER-6344] - (SCAN) Scans now reuse threads from a pool instead of always using fresh system threads.
    • [AER-6345] - (SINDEX) Added storage context configuration item sindex-startup-device-scan to build secondary indexes at startup by scanning devices.
    • [AER-3284] - (STATS) Added object size histograms for storage-engine memory namespaces.
    • [AER-6317] - (UDF) Implemented record.memory_size().
  • Enterprise Only
    • [AER-6349] - (DEPLOYMENT) Added cluster-nodes-limit feature key to restrict cluster size.
    • [AER-6324] - (KVS) Added support for fetching configuration items specified via file path from environment variables.
    • [AER-6337] - (STATS) Included tomb raider device reads and commit-to-device writes in storage benchmark histograms.
    • [AER-6346] - (STATS) Added nodes count in XDR DC stats and log ticker line.
    • [AER-6305] - (XDR) Removed support for 'only-specified' value of DC namespace context configuration item bin-policy.
    • [AER-6319] - (XDR) Added throttling to limit how often SMD saves XDR information to file.
    • [AER-6321] - (XDR) Changed default value of namespace context configuration item xdr-bin-tombstone-ttl to 24 hours.
    • [AER-6328] - (XDR) Added DC context configuration item max-used-service-threads to limit the number of connections to the DC.
    • [AER-6331] - (XDR) When selecting service threads for XDR transactions, ensure all versions of a record ship on the same service thread.

Bug Fixes

Known Issues

Updates

Don't miss a new aerospike-server release

NewReleases is sending notifications on new releases.