Skip to content
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

Transaction not found in one of the high-availability multiple nodes setup #544

Open
shun0309-zz opened this issue Jan 29, 2018 · 1 comment

Comments

@shun0309-zz
Copy link

shun0309-zz commented Jan 29, 2018

I am running two nodes of bitcore-node with insight API. When I query a transaction on both nodes using the API, one of them returning "not found" while the other one returns the info about the transaction without any error. The transaction indeed has "confirmations: 0".

After tracing the code from insight API to bitcore-node, the reason of the API returning "not found" is the db doesn't contain the transaction record at all.

May I ask

  1. What is the expected behaviour when the bitcore-node encounters some unconfirmed or possibly orphaned transactions?
  2. How could it be possibly ended up into the situation of one node contains the record but the other doesn't? Given that the transaction was received two months ago.
  3. If one of the node fails somehow hence resulting in corrupted database records, how can I fix or reset the node? downloading the whole blockchain again?

Thanks.

@shun0309-zz
Copy link
Author

To clarify, the nodes start at the same time. They synchronise at roughly the same time across their history.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant