---
metadata:
  - name: generator
    content: Diplodoc Platform v5.50.4
alternate:
  - https://ydb.tech/docs/en/troubleshooting/spilling.md
  - https://ydb.tech/docs/ru/troubleshooting/spilling.md
sourcePath: en/core/troubleshooting/spilling/index.md
---
> **Documentation Index:** Fetch the complete configuration index at https://ydb.tech/docs/en/llms.txt

# Spilling Troubleshooting

This section provides troubleshooting information for common spilling issues in YDB. Spilling is a memory management mechanism that temporarily saves intermediate computation data to disk when the system runs out of RAM. These errors can occur during query execution when the system attempts to use spilling functionality and can be observed in logs and query responses.

## Common Issues

- [Permission denied](https://ydb.tech/docs/en/troubleshooting/spilling/permission-denied.md) - Insufficient access permissions to the spilling directory
- [Spilling Service not started](https://ydb.tech/docs/en/troubleshooting/spilling/service-not-started.md) - Attempt to use spilling when the Spilling Service is disabled
- [Total size limit exceeded](https://ydb.tech/docs/en/troubleshooting/spilling/total-size-limit-exceeded.md) - Maximum total size of spilling files exceeded
- [Can not run operation](https://ydb.tech/docs/en/troubleshooting/spilling/can-not-run-operation.md) - I/O thread pool operation queue overflow

## See Also

- [Spilling Configuration](https://ydb.tech/docs/en/reference/configuration/table_service_config.md)
- [Spilling Concept](https://ydb.tech/docs/en/concepts/query_execution/spilling.md)
- [Memory Controller Configuration](https://ydb.tech/docs/en/reference/configuration/memory_controller_config.md)
- [YDB Monitoring](https://ydb.tech/docs/en/devops/observability/monitoring.md)
- [Performance Diagnostics](https://ydb.tech/docs/en/troubleshooting/performance/index.md)
