# ERR stream entry size exceeds server limits

- **ID:** `redis/stream-entry-too-large`
- **Domain:** redis
- **Category:** data_error
- **Error Code:** `ERM`
- **Verification:** ai_generated
- **Fix Rate:** 88%

## Root Cause

A single stream entry exceeds the configured stream-node-max-bytes limit, preventing insertion.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| 7.0 | active | — | — |
| 7.2 | active | — | — |
| 7.4 | active | — | — |

## Workarounds

1. **Break the data into multiple stream entries, each under stream-node-max-bytes (default 4KB). Example: 'XADD mystream * field1 value1' then 'XADD mystream * field2 value2'.** (92% success)
   ```
   Break the data into multiple stream entries, each under stream-node-max-bytes (default 4KB). Example: 'XADD mystream * field1 value1' then 'XADD mystream * field2 value2'.
   ```
2. **Run 'CONFIG SET stream-node-max-bytes 65536' to allow 64KB entries, then retry XADD.** (85% success)
   ```
   Run 'CONFIG SET stream-node-max-bytes 65536' to allow 64KB entries, then retry XADD.
   ```

## Dead Ends

- **** — Only masks the issue; large entries cause memory fragmentation and slow replication. (65% fail)
- **** — The entry remains too large; retry will fail repeatedly. (95% fail)
- **** — Removes protection; can lead to out-of-memory crashes and replication lag. (80% fail)