[
https://issues.apache.org/jira/browse/BEAM-6190?focusedWorklogId=173724&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-173724
]
ASF GitHub Bot logged work on BEAM-6190:
----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Dec/18 18:16
Start Date: 10/Dec/18 18:16
Worklog Time Spent: 10m
Work Description: dustin12 opened a new pull request #7240: [BEAM-6190]
Add processing stuck message to Pantheon.
URL: https://github.com/apache/beam/pull/7240
This PR adds an indication visible on the Pantheon page of a streaming
Dataflow job to indicate when processing on a worker has become stuck.
Currently exceptions in the workers are clearly visible on the Pantheon landing
page but stuck worker messages are only viewable in the worker logs.
@pabloem @lukecwik
------------------------
Follow this checklist to help us incorporate your contribution quickly and
easily:
- [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA
issue, if applicable. This will automatically link the pull request to the
issue.
- [ ] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
It will help us expedite review of your Pull Request if you tag someone
(e.g. `@username`) to look at it.
Post-Commit Tests Status (on master branch)
------------------------------------------------------------------------------------------------
Lang | SDK | Apex | Dataflow | Flink | Gearpump | Samza | Spark
--- | --- | --- | --- | --- | --- | --- | ---
Go | [](https://builds.apache.org/job/beam_PostCommit_Go_GradleBuild/lastCompletedBuild/)
| --- | --- | --- | --- | --- | ---
Java | [](https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Apex_Gradle/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow_Gradle/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Flink_Gradle/lastCompletedBuild/)
[](https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Gearpump_Gradle/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Samza_Gradle/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark_Gradle/lastCompletedBuild/)
Python | [](https://builds.apache.org/job/beam_PostCommit_Python_Verify/lastCompletedBuild/)
| --- | [](https://builds.apache.org/job/beam_PostCommit_Py_VR_Dataflow/lastCompletedBuild/)
</br> [](https://builds.apache.org/job/beam_PostCommit_Py_ValCont/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Python_VR_Flink/lastCompletedBuild/)
| --- | --- | ---
----------------------------------------------------------------
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: 173724)
Time Spent: 10m
Remaining Estimate: 23h 50m (was: 24h)
> "Processing stuck" messages should be visible on Pantheon
> ---------------------------------------------------------
>
> Key: BEAM-6190
> URL: https://issues.apache.org/jira/browse/BEAM-6190
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Affects Versions: 2.8.0
> Environment: Running on Google Cloud Dataflow
> Reporter: Dustin Rhodes
> Assignee: Dustin Rhodes
> Priority: Minor
> Fix For: Not applicable
>
> Original Estimate: 24h
> Time Spent: 10m
> Remaining Estimate: 23h 50m
>
> When user processing results in an exception, it is clearly visible on the
> Pantheon landing page for a streaming Dataflow job. But when user processing
> becomes stuck, there is no indication, even though the worker logs it. Most
> users don't check worker logs and it is not that convenient to check for most
> users. Ideally a stuck worker would result in a visible error on the
> Pantheon landing page.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
