apache / apache/iotdb

[Bug] Error WALBuffer....WAL-Recover Fail to allocate wal node....OutOfMemoryError: Cannot reserve 16777216 bytes of direct buffer memory (allocated: 469771426, limit: 471859200)

Open
#12,714 7 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
6.4k
Forks
1.2k
Avg merge
1d 23h
Merged PRs (30d)
115

Description

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar.

### Version

1.3.0
3C3D

### Describe the bug and provide the minimal reproduce step

image

We upped the JVM memory and still reported this error

### What did you expect to see?

Cluster running properly

### What did you see instead?

We can expand the memory

### Anything else?

_No response_

### Are you willing to submit a PR?

- [X] I'm willing to submit a PR!

Contributor guide

Open the contributing guide

Research direction

Start by reproducing WAL recovery on IoTDB 1.3.0 in the reported 3C3D setup and trace the WAL node allocation that fails with the direct-buffer OutOfMemoryError. Done means the cluster recovers and runs properly without the WAL allocation failure, including when JVM memory is increased.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.