-
Notifications
You must be signed in to change notification settings - Fork 377
INDY-2032: Fix phantom transactions in audit ledger #1151
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
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
e118a3c
add test for a catchup for the new view
ashcherbakov a16851f
fix problem with phantom transactions during the view change
ashcherbakov 6d94993
Merge branch 'master' of https://github.com/hyperledger/indy-plenum i…
ashcherbakov e3455a4
new tests and get rid of stashedOrderedRequest
ashcherbakov c14ee26
change logs
ashcherbakov 012aa93
fix tests; process code review
ashcherbakov e8e35a3
fix tests
ashcherbakov d8b78b1
fix tests
ashcherbakov f9b0661
extend logs
ashcherbakov e4e9781
fix tests
ashcherbakov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,4 @@ | ||
from plenum.common.messages.node_messages import Commit | ||
from plenum.common.types import f | ||
from plenum.common.util import compare_3PC_keys | ||
from plenum.server.replica_validator_enums import DISCARD, INCORRECT_INSTANCE, PROCESS, ALREADY_ORDERED, FUTURE_VIEW, \ | ||
|
@@ -43,6 +44,8 @@ def validate_3pc_msg(self, msg): | |
if view_no < self.replica.viewNo - 1: | ||
return DISCARD, OLD_VIEW | ||
if view_no == self.replica.viewNo - 1: | ||
if not isinstance(msg, Commit): | ||
return DISCARD, OLD_VIEW | ||
if not node.view_change_in_progress: | ||
return DISCARD, OLD_VIEW | ||
if self.replica.last_prepared_before_view_change is None: | ||
|
@@ -52,7 +55,7 @@ def validate_3pc_msg(self, msg): | |
if view_no == self.replica.viewNo and node.view_change_in_progress: | ||
return STASH_VIEW, FUTURE_VIEW | ||
|
||
# If Catchup in View Change finished then process a message | ||
# If Catchup in View Change finished then process Commit messages | ||
if node.is_synced and node.view_change_in_progress: | ||
return PROCESS, None | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Explicit check that this is a really commit message would be good here. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The explicit check is already done above. |
||
|
||
|
@@ -94,3 +97,25 @@ def validate_checkpoint_msg(self, msg): | |
return STASH_CATCH_UP, CATCHING_UP | ||
|
||
return PROCESS, None | ||
|
||
def can_send_3pc_batch(self): | ||
if not self.replica.isPrimary: | ||
return False | ||
if not self.replica.node.isParticipating: | ||
return False | ||
if self.replica.node.pre_view_change_in_progress: | ||
return False | ||
if self.replica.viewNo < self.replica.last_ordered_3pc[0]: | ||
return False | ||
if self.replica.viewNo == self.replica.last_ordered_3pc[0] and \ | ||
self.replica.lastPrePrepareSeqNo < self.replica.last_ordered_3pc[1]: | ||
return False | ||
return True | ||
|
||
def can_order(self): | ||
node = self.replica.node | ||
if node.isParticipating: | ||
return True | ||
if node.is_synced and node.view_change_in_progress: | ||
return True | ||
return False |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could it happen so that
uncommittedRootHash
is not None but due to other batch in flight, so that we still need to manually apply transactions?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think no, because here we always have apply-commit cycle, so that even if this is an Ordered msg came in between catchup rounds during view change, each Ordered will be re-applied and committed immediately, so that it always end up with empty uncommitted state if the audit ledger.