You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Sam Whittle (JIRA)" <ji...@apache.org> on 2019/01/22 22:42:00 UTC
[jira] [Resolved] (BEAM-6170) NexmarkLauncher stall warning causes
benchmark failure
[ https://issues.apache.org/jira/browse/BEAM-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Whittle resolved BEAM-6170.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.10.0
> 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
> Fix For: 2.10.0
>
> Original Estimate: 10m
> Time Spent: 1.5h
> 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)