[
https://issues.apache.org/jira/browse/BEAM-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193246#comment-16193246
]
ASF GitHub Bot commented on BEAM-3013:
--------------------------------------
GitHub user pabloem reopened a pull request:
https://github.com/apache/beam/pull/3936
[BEAM-3013] Prototyping lull-tracking for Python
r: @charlesccychen
cc: @bjchambers
This change is to allow the state sampler in Python to report when too much
time has been spent on the same state (default: 5 minutes). When more than 5
minutes have been spent, the worker will report it.
This change requires the sampling thread (normally a pure-C thread) to
acquire the GIL, to access the logging module. For this, I laid out a
convention to acquire locks in a certain order - to avoid deadlocks.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pabloem/incubator-beam lull-tracking-py
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/3936.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3936
----
commit d41d02e17763c5c7aab6c53d2d9cbf1ba8e6a83a
Author: Pablo <[email protected]>
Date: 2017-10-03T20:49:43Z
Prototyping lull-tracking for Python
commit ee53714c2d108c57ae6fadd92110db81a47acf8b
Author: Pablo <[email protected]>
Date: 2017-10-03T22:17:42Z
Fixing lint issues
----
> The Python worker should report lulls
> -------------------------------------
>
> Key: BEAM-3013
> URL: https://issues.apache.org/jira/browse/BEAM-3013
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-harness
> Reporter: Pablo Estrada
> Assignee: Pablo Estrada
>
> Whenever too much time has been spent on the same state (e.g. > 5 minutes),
> the worker should report it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
