diff options
| author | wxiaoguang <wxiaoguang@gmail.com> | 2023-05-29 10:52:32 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-05-29 10:52:32 +0800 |
| commit | 84c8ab9fd109145d04d0c58cadd46160f1ee9263 (patch) | |
| tree | eebfb67c7414bae68b08ba3adca2dbb1f68a61cc /docs/content/doc/installation | |
| parent | 8faf9465b3913137d3470151a678857c319625a5 (diff) | |
| download | gitea-84c8ab9fd109145d04d0c58cadd46160f1ee9263.tar.gz gitea-84c8ab9fd109145d04d0c58cadd46160f1ee9263.zip | |
Help to recover from corrupted levelqueue (#24912)
gitea.com experienced the corrupted LevelQueue bug again.
I think the problem is clear now: if the keys in LevelDB went
out-of-sync, the LevelQueue itself doesn't have the ability to recover,
eg:
* LevelQueue.Len() reports 100
* LevelQueue.LPop() reports ErrNotFound = errors.New("no key found")
So it needs to dive into the LevelDB to remove all keys to recover the
corrupted LevelQueue.
More comments are in TestCorruptedLevelQueue.
Diffstat (limited to 'docs/content/doc/installation')
0 files changed, 0 insertions, 0 deletions