[
https://issues.apache.org/jira/browse/BEAM-9789?focusedWorklogId=425457&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425457
]
ASF GitHub Bot logged work on BEAM-9789:
----------------------------------------
Author: ASF GitHub Bot
Created on: 20/Apr/20 20:26
Start Date: 20/Apr/20 20:26
Worklog Time Spent: 10m
Work Description: lostluck commented on issue #11468:
URL: https://github.com/apache/beam/pull/11468#issuecomment-616789253
R: @youngoli
cc: @robertwb
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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: 425457)
Time Spent: 20m (was: 10m)
> Locking error in harness.go
> ---------------------------
>
> Key: BEAM-9789
> URL: https://issues.apache.org/jira/browse/BEAM-9789
> Project: Beam
> Issue Type: Bug
> Components: sdk-go
> Reporter: Robert Burke
> Assignee: Robert Burke
> Priority: Major
> Fix For: Not applicable
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When there's an error on lookup or construction of an execution plan, the
> lock is accidentally held causing the worker to freeze.
> Shouldn't be user affecting, as most plans and lookups are correct without
> error, but if there's a transient GRPC issue on lookup, that might cause an
> otherwise healthy worker to deadlock.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
