# What is the meaning of "special-errors" "key-busy" "record-too-big" entries in log

**URL:** <https://discuss.aerospike.com/t/what-is-the-meaning-of-special-errors-key-busy-record-too-big-entries-in-log/10247>\
**Category:** Operations\
**Created:** [June 1, 2023, 11:02pm UTC](https://discuss.aerospike.com/t/what-is-the-meaning-of-special-errors-key-busy-record-too-big-entries-in-log/10247 "2023-06-01T23:02:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![shan.p](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/shan.p/32/1990_2.png) [@shan.p](https://discuss.aerospike.com/u/shan.p)\
**Post date:** [June 1, 2023, 11:02pm UTC](https://discuss.aerospike.com/t/what-is-the-meaning-of-special-errors-key-busy-record-too-big-entries-in-log/10247/1 "2023-06-01T23:02:28Z")

</div>

I am investigating a spike in `aerospike.namespace.client_write_error` Datadog metrics in an Aerospike cluster (version 5.7.0.10). In the Aerospike server logs, I see several INFO level entries that have the message `record-too-big`.

```auto
Jun 01 2023 22:48:59 GMT: INFO (info): (ticker.c:976) {<my namespace>} special-errors: key-busy 578312 record-too-big 0 lost-conflict (0,0)

```

The namespace configuration is this:

```auto
namespace <my namespace> {
        replication-factor 2
        memory-size 238G
        high-water-memory-pct 70
        high-water-disk-pct 60
        default-ttl 4d 
        nsup-period 120
        partition-tree-sprigs 4096
        storage-engine memory
}

```

What is the significance of these errors? Are these related to the write errors?

---

<div class="post-metadata">

**Author:** ![meher](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/meher/32/1644_2.png) [@meher](https://discuss.aerospike.com/u/meher)\
**Post date:** [June 5, 2023, 10:09pm UTC](https://discuss.aerospike.com/t/what-is-the-meaning-of-special-errors-key-busy-record-too-big-entries-in-log/10247/2 "2023-06-05T22:09:45Z")

</div>

For the `key-busy` errors, this article should help understand them: [Why does my client return Error code 14 Hotkey](https://support.aerospike.com/s/article/Why-does-my-client-return-Error-code-14-Hot-key).

The `record-too-big` refers to records that are (or become after update) larger than the configured [`write-block-size`](https://docs.aerospike.com/reference/configuration#write-block-size) but you don’t seem to have hit this error.

You could of course directly monitor those specific statistics without having to look at the logs:

- [fail\_key\_busy](https://docs.aerospike.com/reference/metrics#fail_key_busy)
- [fail\_record\_too\_big](https://docs.aerospike.com/reference/metrics#fail_record_too_big)

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/system/32/2274_2.png) [@system](https://discuss.aerospike.com/u/system)\
**Post date:** [June 4, 2024, 10:10pm UTC](https://discuss.aerospike.com/t/what-is-the-meaning-of-special-errors-key-busy-record-too-big-entries-in-log/10247/3 "2024-06-04T22:10:17Z")

</div>

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.