mirror of
https://codeberg.org/forgejo/forgejo
synced 2024-11-24 10:46:10 +01:00
84c8ab9fd1
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.
|
||
|---|---|---|
| .. | ||
| lqinternal | ||
| backoff.go | ||
| base.go | ||
| base_channel.go | ||
| base_channel_test.go | ||
| base_dummy.go | ||
| base_levelqueue.go | ||
| base_levelqueue_common.go | ||
| base_levelqueue_test.go | ||
| base_levelqueue_unique.go | ||
| base_redis.go | ||
| base_redis_test.go | ||
| base_test.go | ||
| config.go | ||
| manager.go | ||
| manager_test.go | ||
| queue.go | ||
| testhelper.go | ||
| workergroup.go | ||
| workerqueue.go | ||
| workerqueue_test.go | ||