Recovery / Allocation error with hybrid log
See original GitHub issueI get consistent allocation error in object log when using hybrid log checkpoint. Recover fails due to this error in Generic Allocator. I can reproduce the error. Please let me know if you want more details on the issue.
Process terminated. Assertion failed. at FASTER.core.GenericAllocator`2.AsyncReadPageWithObjectsCallback[TContext](UInt32 errorCode, UInt32 numBytes, Object context) in D:\code\modern\arge\FASTER-2.0.0-preview.1.2\cs\src\core\Allocator\GenericAllocator.cs:line 629
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Recovering from allocation problems with the archive log
The RECOVER utility executes and requires an archive log. If neither archive log can be found or used, recovery fails. · The active...
Read more >Troubleshoot backup errors with Azure VMs
In this article, learn how to troubleshoot errors encountered with backup and restore of Azure virtual machines.
Read more >How to recover from BTRFS errors | Support
Quota issues seen during normal operation: run 'btrfs quota rescan' Only if everything else fails, run 'btrfs check' and research if repair ...
Read more >KB1857: Unable to allocate processing resources
This article attempts to document the most common permutations of the Unable to allocate processing resources error.
Read more >Incorrect message displayed while accessing the menu "Design"
While accessing Main Menu > Plan > Design, an incorrect message of Login name or password is incorrect is displayed instead of Unauthorized ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you very much for awesome and quick fix.
This should be fixed with the linked PR. We have merged it to main branch, and also updated the v2 branch. You can use it from sources until the next NuGet release. Note that in the latest v2, there is a breaking change in the IFunctions API: all functions return bool, and
ref RecordInfo
is no longer a part of the parameter list.