-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
missing cache entry #173
Comments
For the reference, my node has that example missing entry.
|
I just observed this situation today while looking at:
My hivemind node has a |
@inertia186 could you try running the |
|
It looks like in these cases, We should throw failed inserts back into the queue to try again next round. |
Fix was merged in #224 and |
There are occasionally posts missing in
hive_posts_cache
. This condition is rare but concerning. Fortunately it does not affect thehive_posts
table so it's easily recoverable. Identifying the cause is important because it touches core operating assumptions.The latest example:
missing: {'id': 68799912, 'author': 'jeffjagoe', 'permlink': 'survey-blockchain-developer-salaries-have-increased-over-the-past-six-months-via-the-block', 'depth': 0, 'created_at': datetime.datetime(2019, 1, 14, 13, 31, 39), 'is_deleted': False}
. There's a handful of others dated around December 20th; they could have been explained by a different bug, but not this last case.The post originated in 9fd5a440e16572662ab6b5f35827f41f19a794db @ 29,449464.
Logs do not show anything particularly suspect. It shows 1 post and 1 edit for this block, which is accurate. The record in question was a new post, not an edit, and has not been edited since. It was registered in
hive_posts
yet somehow eludedhive_posts_cache
. The sync process appears to be completely uninterrupted.Logs from a different node which did cache the post correctly:
"block not available" messages should not be relevant to this issue because they are an artifact of the follower's block queue (pre-processing).
The text was updated successfully, but these errors were encountered: