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

ASF GitHub Bot logged work on GOBBLIN-2000:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Feb/24 21:54
            Start Date: 06/Feb/24 21:54
    Worklog Time Spent: 10m 
      Work Description: Will-Lo merged PR #3875:
URL: https://github.com/apache/gobblin/pull/3875




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

            Worklog Id:     (was: 903967)
    Remaining Estimate: 0h
            Time Spent: 10m

> Add logging around concurrent flow status check in GaaS
> -------------------------------------------------------
>
>                 Key: GOBBLIN-2000
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-2000
>             Project: Apache Gobblin
>          Issue Type: Improvement
>          Components: gobblin-service
>            Reporter: William Lo
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In GaaS, it is difficult to debug scenarios where fetching flow status to 
> check if another concurrent execution is safe to kick off. We want to add 
> logging around this area.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to