-
Notifications
You must be signed in to change notification settings - Fork 751
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
[GOBBLIN-1969] Increase Visibility for Flow Compilation Failures #3840
Open
umustafi
wants to merge
5
commits into
apache:master
Choose a base branch
from
umustafi:addVisibilityIntoCompilationFailure
base: master
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 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
99769c4
Add logging and metrics for flow compilation validation
37654ff
Change metric to count successful flow compilations
33ada42
Initialize FlowCatalog before DagManager started
028e21b
Revert "Initialize FlowCatalog before DagManager started"
ebbdad3
Rename metrics to be uniform
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -86,10 +86,16 @@ public Optional<Dag<JobExecutionPlan>> createExecutionPlanIfValid(FlowSpec flowS | |
Map<String, String> flowMetadata = TimingEventUtils.getFlowMetadata(flowSpec); | ||
|
||
if (!jobExecutionPlanDagOptional.isPresent()) { | ||
log.warn("No dag execution plan created for flowGroup: {} flowName: {}", | ||
flowMetadata.get(TimingEvent.FlowEventConstants.FLOW_GROUP_FIELD), | ||
flowMetadata.get(TimingEvent.FlowEventConstants.FLOW_NAME_FIELD)); | ||
Comment on lines
+90
to
+91
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. if we do anything other than logging the value, I recommend a default (even when it should always be set). for logging only, it's safe enough to print |
||
return Optional.absent(); | ||
} | ||
|
||
if (jobExecutionPlanDagOptional.get() == null || jobExecutionPlanDagOptional.get().isEmpty()) { | ||
log.warn("Null or empty dag execution plan created for flowGroup: {} flowName: {}", | ||
flowMetadata.get(TimingEvent.FlowEventConstants.FLOW_GROUP_FIELD), | ||
flowMetadata.get(TimingEvent.FlowEventConstants.FLOW_NAME_FIELD)); | ||
populateFlowCompilationFailedEventMessage(eventSubmitter, flowSpec, flowMetadata); | ||
return Optional.absent(); | ||
} | ||
|
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.
I'm not too familiar w/ Guice... but are you sure the call to
binder.bind
is guaranteed to synchronously carryout "initializing the flow catalog" (so that finishes before the later call tobinder.bind(DagManager.class)
)?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.
The order does matter here but this is actually the wrong class initialization and won't fix the problem so leaving out of this PR.