You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "Kip Kohn (Jira)" <ji...@apache.org> on 2024/12/10 20:37:00 UTC
[jira] [Updated] (GOBBLIN-2179) Provide observability about how much work a Gobblin-on-Temporal job will (and already has) performed
[ https://issues.apache.org/jira/browse/GOBBLIN-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kip Kohn updated GOBBLIN-2179:
------------------------------
Summary: Provide observability about how much work a Gobblin-on-Temporal job will (and already has) performed (was: Provide observability about how much work remains for a job)
> Provide observability about how much work a Gobblin-on-Temporal job will (and already has) performed
> ----------------------------------------------------------------------------------------------------
>
> Key: GOBBLIN-2179
> URL: https://issues.apache.org/jira/browse/GOBBLIN-2179
> Project: Apache Gobblin
> Issue Type: Bug
> Components: gobblin-core
> Reporter: Kip Kohn
> Assignee: Abhishek Tiwari
> Priority: Major
>
> Provide observability about how much work remains for a job. In addition, enable measurement and analysis about how long sub-tasks (`WorkUnit`s) take while processing some amount of data.
> We wish this info to feed into the analysis for Gobblin-on-Temporal (GoT) auto-scaling and right-sizing, based on Dynamic Scaling - https://issues.apache.org/jira/browse/GOBBLIN-2170
> e.g. in `GenerateWorkUnits`' result, capture the total number of `MultiWorkUnit`s and constituent sub-`WorkUnit`s, their total size in bytes, as well as the size distribution across all WUs.
> also, in the `WorkUnitClaimCheck` argument to each `ProcessWorkUnit` activity, capture the total size of the possibly `MultiWorkUnit` as well as an abbreviated characterization of the size of any constituent `WorkUnit`s.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)