[
https://issues.apache.org/jira/browse/BEAM-6170?focusedWorklogId=171774&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-171774
]
ASF GitHub Bot logged work on BEAM-6170:
----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Dec/18 00:45
Start Date: 04/Dec/18 00:45
Worklog Time Spent: 10m
Work Description: scwhittle opened a new pull request #7191: [BEAM-6170]
Change Nexmark stuckness warnings to not fail pipeline
URL: https://github.com/apache/beam/pull/7191
The monitoring in the NexmarkLauncher watches the pipeline results and
source for events. If no events are consumed from the source or published to
the output for over
STUCK_WARNING_DELAY it prints an warning message:
"WARNING: streaming query appears to have been stuck for %d min.",
However it also adds this to the errors list, which causes the pipeline to
terminate with an exception. There is a separate STUCK_TERMINATE_DELAY which
is used to terminate the pipeline. It seems inconsistent to cause the pipeline
to fail with the warning timeout. It is also not entirely accurate to say the
pipeline is stuck since it may be busy processing stages other than the input
or output.
R: @echauchot
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 171774)
Time Spent: 10m
Remaining Estimate: 0h (was: 10m)
> NexmarkLauncher stall warning causes benchmark failure
> ------------------------------------------------------
>
> Key: BEAM-6170
> URL: https://issues.apache.org/jira/browse/BEAM-6170
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: Sam Whittle
> Assignee: Sam Whittle
> Priority: Trivial
> Original Estimate: 10m
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The monitoring in the NexmarkLauncher watches the pipeline results and source
> for events. If no events are consumed from the source or published to the
> output for over
> STUCK_WARNING_DELAY it prints an warning message:
> "WARNING: streaming query appears to have been stuck for %d min.",
> However it also adds this to the errors list, which causes the pipeline to
> terminate by throwing an exception. There is a separate
> STUCK_TERMINATE_DELAY which is used to terminate the pipeline. It seems
> inconsistent to cause the pipeline to fail with the warning timeout. It is
> also not 100% accurrate because the pipeline may be busy processing stages
> other than the input or output.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
