-
Notifications
You must be signed in to change notification settings - Fork 52
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
Failed getting block number for transaction #581
Comments
Hi @bkravi73 , when the node restarts, the commit pipeline of the fabric platform tries to restart from the last block processed before the shutdown. To do this, the stack asks the vault what was the last transaction committed. Then the ask queries the peer to learn the block this transaction belongs to. If an error happens here, then the stack simply restart from the genesis block. Could you post the entire log line? I want to understand which transaction id fails and with what error. Thanks for reporting this :) |
Thanks for the details @adecaro . Please find below the logs: INFO badger 2024/05/28 06:03:12 INFO: ttxdb.SetStatus Streaming about 209 KiB of uncompressed data (60 KiB on disk) |
Hi @bkravi73 , it looks like that the transaction is not on the ledger. Is that a transaction that failed before reaching the ordering service? |
@adecaro - Actually, this error is seen whenever a withdrawal is done(not during node start up). We looked for this txID in fabric ledger, and it is the transaction Id which got committed into ledger just a couple of seconds before. So, probably a look up for latest or last transaction is happening, before tx is even committed into ledger. A possible read-write conflict. Please let us know if this is true. |
When we integrated FSC with our application, we are seeing "Failed getting block number for transaction " error being logged very frequently. However, no error is thrown and invocations are successful.
We would like to know if this is a valid scenario and why transaction doesn't have a block number.
Thanks for your help
The text was updated successfully, but these errors were encountered: