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 2023/12/22 14:33:00 UTC

[jira] [Created] (GOBBLIN-1979) Pare down TaskStateCollectorService failure logging, to avoid flooding logs during widespread failure, e.g. O(1k)+

Kip Kohn created GOBBLIN-1979:
---------------------------------

             Summary: Pare down TaskStateCollectorService failure logging, to avoid flooding logs during widespread failure, e.g. O(1k)+
                 Key: GOBBLIN-1979
                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1979
             Project: Apache Gobblin
          Issue Type: Bug
          Components: gobblin-core
            Reporter: Kip Kohn
            Assignee: Abhishek Tiwari


Logging Task state collector failure at the granularity of every task is impractical, when tasks number in the 100k's.

This arose because the dest-side volume enforced the namespace quota, which left over 100k+ WUs failing. so while not every day, this is a normal occurrence and therefore deserves graceful handling.



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