You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/05/26 00:39:00 UTC

[jira] [Work logged] (BEAM-14481) ScopedState can not be re-entered (regression caused by Batched DoFn worker changes)

     [ https://issues.apache.org/jira/browse/BEAM-14481?focusedWorklogId=774859&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-774859 ]

ASF GitHub Bot logged work on BEAM-14481:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/May/22 00:38
            Start Date: 26/May/22 00:38
    Worklog Time Spent: 10m 
      Work Description: robertwb commented on code in PR #17761:
URL: https://github.com/apache/beam/pull/17761#discussion_r882222407


##########
sdks/python/apache_beam/runners/worker/operations.py:
##########
@@ -1214,9 +1213,9 @@ def __init__(
 
   def setup(self):
     # type: () -> None
+    _LOGGER.debug('Setup called for %s', self)

Review Comment:
   We can probably get rid of this line for consistency. 





Issue Time Tracking
-------------------

    Worklog Id:     (was: 774859)
    Time Spent: 2h 50m  (was: 2h 40m)

> ScopedState can not be re-entered (regression caused by Batched DoFn worker changes)
> ------------------------------------------------------------------------------------
>
>                 Key: BEAM-14481
>                 URL: https://issues.apache.org/jira/browse/BEAM-14481
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-core
>            Reporter: Brian Hulette
>            Assignee: Brian Hulette
>            Priority: P1
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> We've observed some regressions in internal pipelines. We've narrowed the root cause down to [https://github.com/apache/beam/pull/17384] - the worker changes for Batched DoFns.
> I still don't understand the root cause, but given this change can lead to a regression in pipelines that don't use the feature I think we should roll it back.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)