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

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

                Author: ASF GitHub Bot
            Created on: 08/Oct/18 21:14
            Start Date: 08/Oct/18 21:14
    Worklog Time Spent: 10m 
      Work Description: mwylde commented on issue #6593: [BEAM-5633] Adds 
reconnect logic to python logging client
URL: https://github.com/apache/beam/pull/6593#issuecomment-427981382
 
 
   I've updated with the review comments and fixed lint failures. There's an 
open question about what the behavior should be when the logging connection is 
down (e.g., when we're in the process of reconnecting). We can queue up some 
number of logs, but past that point should we block execution or drop logs?
   
   Currently this PR queues up to 1,000 logs and drops past that point. The 
queue size is semi-arbitrary, but to me it makes sense to prioritize pipeline 
execution over capturing 100% of logs. Would be interested in hearing other 
opinions on this, though.

----------------------------------------------------------------
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: 152407)
    Time Spent: 1.5h  (was: 1h 20m)

> 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
>          Time Spent: 1.5h
>  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