You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually whenever the validation of a transaction has error or not, we send the replication message to the storage nodes.
But if there is an error in the validation, the storage nodes will not replicate the transaction. So we send a message for nothing because we already know that the replication will fail
Describe the solution you'd like
In the distributed workflow, if there is an error in the validation stamp or in the cross validation stamp, then do not send the replication message to the storage node, and directly notify the error to the welcome node.
The text was updated successfully, but these errors were encountered:
Describe the problem you discovered
Actually whenever the validation of a transaction has error or not, we send the replication message to the storage nodes.
But if there is an error in the validation, the storage nodes will not replicate the transaction. So we send a message for nothing because we already know that the replication will fail
Describe the solution you'd like
In the distributed workflow, if there is an error in the validation stamp or in the cross validation stamp, then do not send the replication message to the storage node, and directly notify the error to the welcome node.
The text was updated successfully, but these errors were encountered: