Aerospike Server Community Edition 4.5.0.20
Description
- The CentOS 7 RPM packages are built with OpenSSL 1.0.2, which is the current shipping package version. If you are running on an older version of CentOS 7 which uses OpenSSL 1.0.1, the installation will not succeed due to a dependency mismatch. Please resolve by either updating CentOS patches (security or whole release) to a point where OpenSSL 1.0.2 is used, or install OpenSSL 1.0.2 using "yum update openssl".
- When upgrading the Aerospike Server refer to the Special Upgrades documentation.
Known Issues
- Enterprise & Community
- [AER-6444] - (CDT) For putItems(), the policy check is skipped for empty ordered maps. Fixed in version 5.0.0.37.
- [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-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-6326] - (KVS) When Aerospike runs as the init process (e.g. in some container scenarios), signals do not stop Aerospike as intended. Fixed in version 4.7.0.23.
- [AER-6309] - (CDT) For ordered lists,
get_all_by_value_list
operation with result type value always returns an empty list. Fixed in version 4.7.0.21. - [AER-6289] - (KVS) Concurrently reading and writing a new bin or set name may access a pointer which crosses a cache line boundary, causing a crash. Fixed in version 4.6.0.21.
- [AER-6190] - (UDF) Ordered lists are not protected from having their order scrambled by a UDF. Fixed in version 4.6.0.13.
- [AER-6228] - (KVS) Theoretical race between replication and migration could cause stale version of record to be migrated. Fixed in version 4.5.3.19.
- [AER-6128] - (BALANCE) For AP namespaces with
prefer-uniform-balance
true, non-optimal masters may be selected. Fixed in version 4.5.3.7. - [AER-6040] - (DEPLOYMENT) Aerospike will not start under systemd as non-root when using
index-type
value 'flash' orauto-pin
value 'numa'. Fixed in version 4.5.3.2. - [AER-6053] - (SCAN) Dynamically decreasing service context configuration items
scan-threads
orsindex-builder-threads
temporarily blocks all (other) dynamic configurations. Fixed in version 4.5.3.2. - [AER-6211] - (KVS) Dynamically increasing both the system file descriptor limit and service context configuration item
proto-fd-max
to a value larger than the system limit at startup may cause an assert. Fixed in version 4.5.2.17. - [AER-6197] - (FABRIC) Incorrect handling of unsupported message types can cause a crash. Fixed in version 4.5.0.24.
- [AER-6198] - (NETWORK) Unnecessary assert on failure to set various socket options, e.g. keep-alive. Fixed in version 4.5.0.24.
- [AER-6194] - (GEO) For namespaces with
data-in-memory true
, GeoJSON particles allocate up to 2KB more than the reported particle size. Fixed in version 4.5.0.24. - [AER-6189] - (UDF) List creation via UDF does not initialize list flags, which may inadvertently flag the list as ordered. Fixed in version 4.5.0.23.
- Enterprise Only
- A serious flaw has been discovered for HTTP v2 in the library used by change notification.
http-version
MUST be set tov1
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-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-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. - [AER-6304] - (BALANCE) When quiescing a node, for AP namespaces, empty partition trees are unnecessarily allocated for unowned partitions. Fixed in version 4.7.0.21.
- [AER-6143] - (BALANCE) For
strong-consistency
namespaces, if quiescing nodes with non-roster nodes in the cluster, the wrong nodes may quiesce. Fixed in version 4.7.0.3. - [AER-6287] - (KVS) When writing over a tombstone with Time-To-Live (TTL) value -2 (i.e. do not update TTL), the write fails to apply the namespace
default-ttl
. Fixed in version 4.6.0.21. - [AER-6250] - (UDF) Race between a background UDF scan/query internal transaction and a durable delete may cause a deadlock. Fixed in 4.5.3.22.
- [AER-6227] - (BALANCE) When applying uniform balance, a misused stack variable may cause an inaccurate balance and prevent migrations from completing. Fixed in version 4.5.2.18.
- [AER-6035] - (BALANCE) For AP namespaces with
prefer-uniform-balance
true, there may be redundant migrations after shutting down a quiesced node. Fixed in version 4.5.2.1. - [AER-6041] - (XDR) Honor compression threshold configuration for http destination. Fixed in version 4.5.2.1.
- [AER-6195] - (MIGRATION) Theoretical race condition may cause delta migration to complete without sending all records. Fixed in version 4.5.0.24.
- [AER-6178] - (STORAGE) Setting storage context configuration item
compression
dynamically forstorage-engine memory
namespaces is not prevented and may cause a crash. Fixed in version 4.5.0.23. - [AER-6175] - (BALANCE) For
strong-consistency
namespaces, appeal subsystem leaks memory, and has rare races which may cause crash or deadlock. Fixed in version 4.5.0.22. - [AER-6169] - (SECURITY) Reporting of login failures erroneously requires setting security log/syslog context configuration item
report-authentication
true. Fixed in version 4.5.0.21.
- A serious flaw has been discovered for HTTP v2 in the library used by change notification.
New Features
Improvements
Bug Fixes
- Enterprise & Community
- [AER-6120] - (CLUSTERING) No heartbeat retries after DNS resolution failure.