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

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

                Author: ASF GitHub Bot
            Created on: 19/Apr/19 22:32
            Start Date: 19/Apr/19 22:32
    Worklog Time Spent: 10m 
      Work Description: angoenka commented on issue #6593: [BEAM-5633] Adds 
reconnect logic to python logging client
URL: https://github.com/apache/beam/pull/6593#issuecomment-485029539
 
 
   We fixed keep alive issue by explicitly setting the keep alive time on 
server and clients in pr https://github.com/apache/beam/pull/7415
   
   I am planning to revisit the reconnect logic as I see that the connect 
method is called multiple times on pipeline termination causing hang of the sdk 
harness container.
 
----------------------------------------------------------------
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: 230292)
    Time Spent: 3h 40m  (was: 3.5h)

> Python SDK harness logging client failure
> -----------------------------------------
>
>                 Key: BEAM-5633
>                 URL: https://issues.apache.org/jira/browse/BEAM-5633
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-harness
>            Reporter: Thomas Weise
>            Assignee: Micah Wylde
>            Priority: Major
>              Labels: portability-flink
>             Fix For: 2.8.0
>
>          Time Spent: 3h 40m
>  Remaining Estimate: 0h
>
> After running a test with synthetic source for a few minutes, the logging 
> client fails and all subsequent log output is not forwarded to the runner.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to