You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Andras Piros (JIRA)" <ji...@apache.org> on 2018/11/09 12:55:00 UTC

[jira] [Created] (OOZIE-3381) [coordinator] Enhance logging of CoordElFunctions.coord_latestRange_sync

Andras Piros created OOZIE-3381:
-----------------------------------

             Summary: [coordinator] Enhance logging of CoordElFunctions.coord_latestRange_sync
                 Key: OOZIE-3381
                 URL: https://issues.apache.org/jira/browse/OOZIE-3381
             Project: Oozie
          Issue Type: Task
          Components: coordinator
    Affects Versions: 5.1.0
            Reporter: Andras Piros
            Assignee: Andras Piros


When using [{{$\{coord:latest(n)}}} coordinator EL function|https://oozie.apache.org/docs/5.0.0/CoordinatorFunctionalSpec.html#a6.6.6._coord:latestint_n_EL_Function_for_Synchronous_Datasets] inside an input dataset dependency, it's often the case that more information is needed how many HDFS URIs are being checked for each {{<data-in/>}}.

Right now we don't have this information. While debugging and fine tuning parameters like {{dataset frequency}}, {{initial-instance}}, and {{data-in}} {{instance}}, it would be very useful to know how many HDFS roundtrips are issues by the current settings {{CoordELFunctions#coord_latestRange_sync()}} having called {{DFSClient#exists()}}. We need appropriate logging there.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)