HarperFast / HarperFast/harper

RocksTransactionLogStore: uncaughtException 'Log already bound to a transaction id' crashes process

Open
#1,162 0 comments 0 reactions 0 assignees View on GitHub
area:storage bug
Dominant language
JavaScript
Stars
89
Forks
10
Avg merge
2d 6h
Merged PRs (30d)
200

Description

## Summary

An unhandled exception has been observed in production with the message:

```
Error: Log already bound to a transaction id
```

thrown from `RocksTransactionLogStore.put`. The error propagates as an uncaughtException and crashes the process.

## Impact

Process crash; requires restart to recover.

## Known details

- Surfaced in `#development` channel logs
- Occurs in `RocksTransactionLogStore.put`
- Root cause and reliable reproduction steps not yet established — needs investigation

## Next step

Add a test or logging to `RocksTransactionLogStore.put` that captures the state when a double-bind is detected, and determine whether the caller is violating a contract or whether the store allows a race.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.