[
https://issues.apache.org/jira/browse/GOBBLIN-1830?focusedWorklogId=861846&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-861846
]
ASF GitHub Bot logged work on GOBBLIN-1830:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 19/May/23 21:35
Start Date: 19/May/23 21:35
Worklog Time Spent: 10m
Work Description: ZihanLi58 merged PR #3693:
URL: https://github.com/apache/gobblin/pull/3693
Issue Time Tracking
-------------------
Worklog Id: (was: 861846)
Time Spent: 0.5h (was: 20m)
> Improving Container Transition Tracking in Streaming Data Ingestion
> -------------------------------------------------------------------
>
> Key: GOBBLIN-1830
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1830
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Zihan Li
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, we rely on the flushing event to indicate when a container
> transition occurs. However, if the ingestion process fails to successfully
> flush the data, we won't know which container is responsible. This becomes
> problematic when the pipeline restarts, as we won't be able to identify the
> root cause without manually reviewing the logs of thousands of containers. To
> avoid this issue, we need to develop a more reliable way of tracking
> container transitions that doesn't rely solely on the flushing event.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
