-
Notifications
You must be signed in to change notification settings - Fork 108
Comparing changes
Open a pull request
base repository: rabbitmq/ra
base: v3.0.1
head repository: rabbitmq/ra
compare: v3.0.2
- 9 commits
- 5 files changed
- 3 contributors
Commits on Mar 12, 2026
-
When a segment qualified for compaction (had < 50% live entries or data) but its live_size exceeded max_size (or NumLive exceeded max_count), and no segments have been accumulated yet, the function returned {[], All} where All still contains the problematic segment.Configuration menu - View commit details
-
Copy full SHA for 188ecb9 - Browse repository at this point
Copy the full SHA 188ecb9View commit details
Commits on Mar 13, 2026
-
Merge pull request #590 from rabbitmq/fix-infinte-loop
compaction: fix infinite loop
Configuration menu - View commit details
-
Copy full SHA for 7d933d6 - Browse repository at this point
Copy the full SHA 7d933d6View commit details -
Segment writer: read the full snapshot state ETS record atomically.
The current approoch of reading the snapshot index then the live indexes is prone to a race condition where the snapshot state is updated in betweeen reading the snapshot index and the live indexes. E.g. Snapshot is taken at index 10 with [7, 5, 3, 1] Snapshot is taken at index 15 with [13, 11, 5, 3, 1] Segment writer reads live indexes [7, 5, 3, 1] but snapshot index 15. 13 and 11 will not be written but 7 will be unnecesarily.
Configuration menu - View commit details
-
Copy full SHA for d59d6a3 - Browse repository at this point
Copy the full SHA d59d6a3View commit details -
Merge pull request #591 from rabbitmq/snapshot-write-snapshot-state-fix
Segment writer: read the full snapshot state ETS record atomically.
Configuration menu - View commit details
-
Copy full SHA for 7fd1e17 - Browse repository at this point
Copy the full SHA 7fd1e17View commit details
Commits on Mar 17, 2026
-
Report errors on segment close instead of silently discarding them
ra_log_segment:close/1 in append mode now propagates errors from sync and file:close instead of ignoring them. The segment writer asserts close succeeds when flushing mem tables and defers pivot file deletion until after the successor segment is opened.
Configuration menu - View commit details
-
Copy full SHA for f035238 - Browse repository at this point
Copy the full SHA f035238View commit details -
Configuration menu - View commit details
-
Copy full SHA for add7965 - Browse repository at this point
Copy the full SHA add7965View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0204366 - Browse repository at this point
Copy the full SHA 0204366View commit details -
Merge pull request #592 from rabbitmq/report-errors-on-segment-close
Report errors on segment close instead of silently discarding them
Configuration menu - View commit details
-
Copy full SHA for 1a2e9b5 - Browse repository at this point
Copy the full SHA 1a2e9b5View commit details
Commits on Mar 18, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 13a01fc - Browse repository at this point
Copy the full SHA 13a01fcView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v3.0.1...v3.0.2