Particle flat size error in Aerospike.log

The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.

Particle flat size errors in Aerospike.log

Problem Description

Client writes fail and the following message is displayed in the /var/log/aerospike.log.

Jul 29 2016 13:33:58 GMT: WARNING (rw): (thr_rw.c::4094) {test} write_local: a24982daef26ee63 too big - 1 bins, particles flat size 20485

Explanation

This error will be seen in the server logs when records larger than the write-block-size are inserted. It is not possible to insert records larger than the write_block_size as records cannot span multiple write-blocks.

Solution

Incoming client data should be correctly profiled. If records exceed the configured write-block-size this can be managed on the client or write-block-size can be increased, but this requires a node restart. If the cluster is sized correctly, correct write-block-size should not be a problem.

Notes

  • How to increase write-block-size
  • Detail on write-block-size parameter

Keywords

PARTICLE WRITE LOCAL BLOCK SIZE CLIENT WRITE ERROR AEROSPIKE LOG

Timestamp

7/29/16