-
Notifications
You must be signed in to change notification settings - Fork 18
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
Tickets/dm 45548 #884
Draft
jgates108
wants to merge
25
commits into
tickets/DM-43715
Choose a base branch
from
tickets/DM-45548
base: tickets/DM-43715
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.
Draft
Tickets/dm 45548 #884
Changes from 1 commit
Commits
Show all changes
25 commits
Select commit
Hold shift + click to select a range
0d07782
Removed QueryRequest and XrdSsiMocks.
jgates108 85461dc
Removed unnecessary code.
jgates108 5bb2b08
Added ActiveWorker.
jgates108 74c3a57
Added unit test for query status message.
jgates108 ac9afad
Added cancellation code and for queries, uberjobs, and czar restart.
jgates108 68d591a
More cancellation code added.
jgates108 43a894e
Added query retries.
jgates108 61f1a9b
Added worker believed czar was dead handling.
jgates108 0cff54a
Added dead message handling.
jgates108 5e3642a
Fixed problems with rowlimit and WorkerCzarComIssue.
jgates108 662e5aa
Rebase.
jgates108 82811de
Added comments and removed dead code.
jgates108 769affb
Fixed dead worker check.
jgates108 fa16b4f
Created protojson namespace.
jgates108 831b5ec
clang-format
fritzm 9c4c602
Added unit test.
jgates108 d51fa7d
Reworked the UberJob json message.
jgates108 e1fea4b
Enabled chunk Id replacement, and added connection pools.
jgates108 8ad73c1
Rearranged UberJob building and removed chunkResultName.
jgates108 816da25
Removed TaskMsgFactory.
jgates108 d4bf9e9
Changed Czar to catch 5GB limit.
jgates108 055702f
Improved Job creation performance.
jgates108 fd9df34
Contention testing.
jgates108 2277f63
The blocking version of the FQDN retrieval function
jgates108 ccab87c
Some cleanup.
jgates108 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 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 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 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 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 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 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
Oops, something went wrong.
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.
This is a bit confusing. Shouldn't the user query object be constructed with a valid pointer to the "executive"? And if so then why is this test? What makes the pointer to suddenly disappear?
I'm also seeing the very same pattern of checking for the validity of a pointer all around the code of the PR. Perhaps there is a safer way of constructing objects to avoid polutting the code with these tests?
My other worry is that if there is such an uncertainty (with the elusive pointer) then such code must be really hard to debug.
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.
_executive being null at this point should really never happen, so the check can be removed, but the check is harmless and consistent with other UserQuerySelect methods. UserQuerySelect::discard() sets _executive to null (this has been around for a very long time) so the _executive pointer isn't safe to use directly and must be copied. Changing discard() to not reset _executive had side effects, so I'd rather not mess with it at this time.