-
Notifications
You must be signed in to change notification settings - Fork 851
Forward port for: print on violated block ordering (#21743) #21773
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
Open
mchacki
wants to merge
1
commit into
devel
Choose a base branch
from
bug-fix-devel/print-on-violated-block-ordering
base: devel
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -272,10 +272,40 @@ ExecutionEngine::~ExecutionEngine() { | |
// tasks running on any dependent which could start another on the | ||
// current block. | ||
// The blocks are pushed in a reversed topological order. | ||
for (auto it = _blocks.rbegin(); it != _blocks.rend(); ++it) { | ||
(*it)->stopAsyncTasks(); | ||
{ | ||
// Note: We can use raw pointers here because we are not taking | ||
// any responsibilty of the pointer. It is still managed by the _blocks | ||
// vector. Also we are in the destructor here, so we have guaranteed, | ||
// that no one else is cleaning up the blocks. | ||
std::unordered_set<ExecutionBlock*> seenBlocks; | ||
bool needToPrintViolation = false; | ||
for (auto it = _blocks.rbegin(); it != _blocks.rend(); ++it) { | ||
auto block = it->get(); | ||
if (ExecutionBlock* seenDependency = | ||
block->isDependencyInList(seenBlocks); | ||
seenDependency != nullptr && | ||
block->getPlanNode()->getType() != ExecutionNode::GATHER) { | ||
// We have a dependency that has already been seen, we need to log this | ||
// situation in theory this could lead to deadlocks. Some Blocks are | ||
// fine we just want to see those here. | ||
// Gather Nodes are known to violate this, but they are safe. | ||
LOG_TOPIC("a6c2b", WARN, Logger::AQL) | ||
<< "ALERT Stopping async tasks for " << block->printBlockInfo() | ||
<< " but have already stopped dependency " | ||
<< seenDependency->printBlockInfo(); | ||
Comment on lines
+292
to
+295
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. I think this could actually be bumped to ERROR. 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. Fine with me. |
||
needToPrintViolation = true; | ||
} | ||
block->stopAsyncTasks(); | ||
seenBlocks.insert(block); | ||
} | ||
if (needToPrintViolation) { | ||
for (auto it2 = _blocks.rbegin(); it2 != _blocks.rend(); ++it2) { | ||
LOG_TOPIC("a6c2d", WARN, Logger::AQL) | ||
<< (*it2)->printBlockAndDependenciesInfo(); | ||
} | ||
TRI_ASSERT(false) << "Triggered violation in ExecutionBlock ordering"; | ||
} | ||
} | ||
|
||
if (_sharedState) { // ensure no async task is working anymore | ||
_sharedState->invalidate(); | ||
} | ||
|
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.
These should not be on
WARN
, but probably onDEBUG
.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.
If they are DEBUG, then we do not see them in production, or?