Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Inconsisted unconfirmed state in memory tables #1 #593

Closed
4miners opened this issue Jun 7, 2017 · 0 comments
Closed

Inconsisted unconfirmed state in memory tables #1 #593

4miners opened this issue Jun 7, 2017 · 0 comments
Assignees
Milestone

Comments

@4miners
Copy link
Contributor

4miners commented Jun 7, 2017

When we have unconfirmed transactions of some type (for example VOTE) waiting in transaction pool and restart node - those transactions will be cleared from transaction pool, but their unconfirmed state will stay. That prevents to resend transaction (because it will not pass unconfirmed checks) and can cause other issues.

Solution:
We should reset unconfirmed tables to confirmed state on node start, query:

BEGIN;

DELETE FROM mem_accounts2u_delegates;
INSERT INTO mem_accounts2u_delegates ("accountId", "dependentId") SELECT "accountId", "dependentId" FROM mem_accounts2delegates;

DELETE FROM mem_accounts2u_multisignatures;
INSERT INTO mem_accounts2u_multisignatures ("accountId", "dependentId") SELECT "accountId", "dependentId" FROM mem_accounts2multisignatures;

COMMIT;
@4miners 4miners added this to the Version 0.9.0 milestone Jun 7, 2017
@4miners 4miners self-assigned this Jun 7, 2017
@diego-G diego-G self-assigned this Jun 7, 2017
@diego-G diego-G removed their assignment Jun 7, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants