got IllegalArgumentException when writer.close, with 100,000,000 keys
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 939
- Forks
- 180
- PR merge metrics
- No merged PRs in 30d
Description
I am building a paldb with 100,000,000 keys.
Exception as below, with all default value config:
java.lang.IllegalArgumentException: null
at java.nio.Buffer.position(Buffer.java:244) ~[na:1.8.0_171]
at com.linkedin.paldb.impl.StorageWriter.buildIndex(StorageWriter.java:311) ~[paldb-1.2.0.jar!/:na]
at com.linkedin.paldb.impl.StorageWriter.close(StorageWriter.java:185) ~[paldb-1.2.0.jar!/:na]
at com.linkedin.paldb.impl.WriterImpl.close(WriterImpl.java:96) ~[paldb-1.2.0.jar!/:na]
while db with 10,000,000 keys in same program is OK.
Contributor guide
No contributing guide indexed for this repository
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 StorageWriter.buildIndex at line 311 and the close path through StorageWriter.close and WriterImpl.close, using the reported Java 8 failure as the initial trace. Reproduce the difference between 10,000,000 and 100,000,000 keys with default configuration, then verify that closing the writer completes successfully at the larger scale without the IllegalArgumentException.
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
- Mostly clear
- Newbie friendliness
- 38/100