During batch updates, if there is a large amount of data, occasional database locking issues may occur
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17.3k
- Forks
- 1.6k
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 28
Description
To reproduce
During batch updates, if there is a large amount of data, occasional database locking issues may occur. The database can only be updated normally after restarting. How can this problem be avoided.
QuestDB version:
8.1
OS, in case of Docker specify Docker and the Host OS:
Centos docker
File System, in case of Docker specify Host File System:
ext4
Full Name:
jianpeng
Affiliation:
guo
Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?
- Yes, I have
Additional context
logs:
[table=jobs, thread=45, ex=cannot lock table: /var/lib/questdb/db/jobs, errno=11]
2025-02-04T18:03:36.250095Z E i.q.c.TableUtils cannot lock '/var/lib/questdb/db/jobs.lock' [errno=11, fd=38226244199283]
2025-02-04T18:03:36.250116Z C i.q.c.p.WriterPool could not open [table=jobs, thread=46, ex=cannot lock table: /var/lib/questdb/db/jobs, errno=11]
2025-02-04T18:03:36.252286Z E i.q.c.TableUtils cannot lock '/var/lib/questdb/db/jobs.lock' [errno=11, fd=38226244199284]
2025-02-04T18:03:36.252306Z C i.q.c.p.WriterPool could not open [table=jobs, thread=46, ex=cannot lock table: /var/lib/questdb/db/jobs, errno=11]
2025-02-04T18:03:36.254423Z E i.q.c.TableUtils cannot lock '/var/lib/questdb/db/jobs.lock' [errno=11, fd=38226244199285]
2025-02-04T18:03:36.254443Z C i.q.c.p.WriterPool could not open [table=jobs, thread=46, ex=cannot lock table: /var/lib/questdb/db/jobs, errno=11]
2025-02-04T18:03:36.256857Z E i.q.c.TableUtils cannot lock '/var/lib/questdb/db/jobs.lock' [errno=11, fd=38226244199286]
2025-02-04T18:03:36.256878Z C i.q.c.p.WriterPool could not open [table=jobs, thread=45, ex=cannot lock table: /var/lib/questdb/db/jobs, errno=11]
2025-02-04T18:03:36.258997Z E i.q.c.TableUtils cannot lock '/var/lib/questdb/db/jobs.lock' [errno=11, fd=38226244199287]
2025-02-04T18:03:36.259025Z C i.q.c.p.WriterPool could not open [table=jobs, thread=47, ex=cannot lock table: /var/lib/questdb/db/jobs, errno=11]
2025-02-04T18:03:36.261115Z E i.q.c.TableUtils cannot lock '/var/lib/questdb/db/jobs.lock' [errno=11, fd=38226244199288]
2025-02-04T18:03:36.261134Z C i.q.c.p.WriterPool could not open [table=jobs, thread=46, ex=cannot lock table: /var/lib/questdb/db/jobs, errno=11]
2025-02-04T18:03:36.263262Z E i.q.c.TableUtils cannot lock '/var/lib/questdb/db/jobs.lock' [errno=11, fd=38226244199289]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the TableUtils and WriterPool errors in the supplied logs, then reproduce large batch updates against QuestDB 8.1 in Docker on CentOS with ext4. Trace why jobs.lock remains unavailable after the failures and document a reproducible validation that database updates recover without restarting.
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