Aerospike Server Community Edition 4.7.0.23

Description

• When upgrading the Aerospike Server refer to the Special Upgrades documentation.

Known Issues

• Enterprise & Community
  • Record bins containing (collection data type) Ordered Lists that had operations performed under Aerospike Server versions 3.16.0.1-3.16.0.5 could be incompatible with server versions 4.6 or later due to stricter CDT validation. Also, Unordered Lists created with UDFs under server versions 3.16.0.1-4.5.3.15 could be marked as ordered, even if the application did not explicitly specify this, and would also be incompatible with server versions 4.6 or later. However induced, the incompatibility could also block XDR shipping. The Aerospike CDT Validation Tool is available in the Aerospike Tools 3.24.1 or newer release to identify -and if possible correct- such records. Aerospike recommends the validation tool be run on all namespaces that created or modified List CDTs under a pre-4.6 server. Refer to the Aerospike CDT Validation Tool documentation for steps necessary to run the tool and interpret the output.
  • [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.0.0.37.
  • [AER-6438] - (QUERY) A background operations query may become inaccessible via the job monitor before it completes. Fixed in version 4.9.0.33.
  • [AER-6397] - (BALANCE) For AP namespaces, in very rare cases, distinct subset partitions may be erroneously treated as identical. Fixed in version 4.8.0.29.
  • [AER-6401] - (CDT) When unwinding an index for a nested CDT op which turns out to be a no-op, the index may be corrupted. Fixed in version 4.8.0.29.
  • [AER-6402] - (SINDEX) When iterating through secondary indexes to adjust for changing list bin values, inactive indexes are incorrectly skipped, which may cause a crash. Fixed in version 4.8.0.29.
  • [AER-6339] - (KVS) On certain bitwise blob operations (and, or, xor), an out of bounds byte may be accessed and cause a crash. Fixed in version 4.7.0.26.
  • [AER-6336] - (BATCH) If both filters and bin selection are used in a batch request, proxied sub-transactions are malformed and will fail. Fixed in version 4.7.0.25.
• Enterprise Only
  • A serious flaw has been discovered for HTTP v2 in the library used by change notification. http-version MUST be set to v1 to prevent xdr and change notification from being blocked.
  • [AER-6451] - (KVS) Race condition between sprig element counters and changing sprig roots when rebuilding index during warm restart may cause a crash. Fixed in version 4.9.0.34.
  • [AER-6427] - (KVS) For data-in-index namespaces, durable deletes will cause an unnecessary assertion on a warm restart. Fixed in version 4.9.0.32.
  • [AER-6423] - (LOGGING) For strong-consistency namespaces, non-roster nodes are not always logged when rebalancing. Fixed in version 4.9.0.31.
  • [AER-6413] - (SECURITY) Small memory leak during LDAP login process. Fixed in version 4.8.0.31.
  • [AER-6395] - (SCAN) When using storage or client response compression, scans will leak temporary (de-)compression buffers. Fixed in version 4.8.0.28.
  • [AER-6382] - (SECURITY) When connecting to LDAP server, TLS handshake occasionally fails. Fixed in version 4.8.0.27.
  • [AER-6376] - (SECURITY) Concurrent client logins at server startup time may lead to various symptoms due to lack of thread safety in the LDAP library. Fixed in version 4.8.0.26.
  • [AER-6378] - (SECURITY) When a user's permissions are being assembled from multiple roles, a crash might occur if any of the roles have a whitelist and no privileges. Fixed in version 4.8.0.26.
  • [AER-6363] - (KVS) A write or a UDF that deletes all of a record's bins may result in a tombstone with a non-zero void-time. Fixed in version 4.8.0.25.
  • [AER-6361] - (SECURITY) Concurrent LDAP logins may result in a double-free of the LDAP library's copy of the tls-ca-file configuration item. Fixed in version 4.8.0.25.

New Features

Improvements

Bug Fixes

• Enterprise & Community
  • [AER-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended.

Updates