Record, Write Block Size & LDT



Normal records in Aerospike cannot be larger than the write block size, which is typically between 128 KB and 2 MB. Large data types allow a group of objects to be stored in a single bin of an Aerospike record.

In case LDT are used for storage how will they be able to store more information if the record size is limited to 2MB ?


Actually the write-block-size is between 128KB and 1MB. In the case of Large Ordered List, each object in the LList is at most the write block size, because LDTs store the list across multiple physical sub-records. You can’t have an object that is larger than a physical record. You can actually set the max object size for elements of the LList to something under that limit.

The main difference from a complex data type list is that an LList can span more than one record’s worth of storage, where a list must fit in one record.



Thank you for posting about LDTs in our forum. Please see the LDT Feature Guide for current LDT recommendations and best practices.



Effective immediately, we will no longer actively support the LDT feature and will eventually remove the API. The exact deprecation and removal timeline will depend on customer and community requirements. Instead of LDTs, we advise that you use our newer List and SortedMap APIs, which are now available in all Aerospike-supported clients at the General Availability level. Read our blog post for details.