# TranslogTooLargeException: translog size [2.5gb] exceeds maximum size [1.0gb]

- **ID:** `elasticsearch/translog-too-large`
- **Domain:** elasticsearch
- **Category:** resource_error
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

The translog has grown beyond the configured maximum size (default 1GB), often due to slow flushing or high write rate.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| elasticsearch 8.11 | active | — | — |
| elasticsearch 8.12 | active | — | — |
| elasticsearch 7.17 | active | — | — |
| opensearch 2.9 | active | — | — |

## Workarounds

1. **Manually flush the index to clear translog: POST my_index/_flush** (85% success)
   ```
   Manually flush the index to clear translog: POST my_index/_flush
   ```
2. **Increase translog threshold and perform flush: PUT my_index/_settings { "index.translog.flush_threshold_size": "2gb", "index.translog.sync_interval": "5s" }** (80% success)
   ```
   Increase translog threshold and perform flush: PUT my_index/_settings { "index.translog.flush_threshold_size": "2gb", "index.translog.sync_interval": "5s" }
   ```
3. **Reduce indexing rate temporarily to allow translog to flush naturally, then increase flush threshold permanently.** (75% success)
   ```
   Reduce indexing rate temporarily to allow translog to flush naturally, then increase flush threshold permanently.
   ```

## Dead Ends

- **** — Corrupts the index; Elasticsearch will fail to recover and may lose data. (95% fail)
- **** — Delays flush but does not reduce existing translog size; may cause OOM on large translog. (50% fail)
- **** — Force merge does not affect translog size; translog is separate from segments. (80% fail)