[jira] [Updated] (OOZIE-3381) [coordinator] Enhance logging of CoordElFunctions
[
https://issues.apache.org/jira/browse/OOZIE-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-3381:
Attachment: OOZIE-3381.002.patch
> [coordinator] Enhance logging of CoordElFunctions
> -
>
> 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
>Priority: Major
> Attachments: OOZIE-3381.001.patch, OOZIE-3381.002.patch
>
>
> 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
> {{}}.
> 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()}}
> and {{CoordELFunctions#coord_futureRange_sync()}} having called
> {{DFSClient#exists()}}. We need appropriate logging there.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OOZIE-3381) [coordinator] Enhance logging of CoordElFunctions
[
https://issues.apache.org/jira/browse/OOZIE-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-3381:
Attachment: OOZIE-3381.001.patch
> [coordinator] Enhance logging of CoordElFunctions
> -
>
> 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
>Priority: Major
> Attachments: OOZIE-3381.001.patch
>
>
> 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
> {{}}.
> 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()}}
> and {{CoordELFunctions#coord_futureRange_sync()}} having called
> {{DFSClient#exists()}}. We need appropriate logging there.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OOZIE-3381) [coordinator] Enhance logging of CoordElFunctions
[
https://issues.apache.org/jira/browse/OOZIE-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-3381:
Summary: [coordinator] Enhance logging of CoordElFunctions (was:
[coordinator] Enhance logging of CoordElFunctions.coord_latestRange_sync)
> [coordinator] Enhance logging of CoordElFunctions
> -
>
> 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
>Priority: Major
>
> 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
> {{}}.
> 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)
[jira] [Updated] (OOZIE-3381) [coordinator] Enhance logging of CoordElFunctions
[
https://issues.apache.org/jira/browse/OOZIE-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-3381:
Description:
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 {{}}.
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()}}
and {{CoordELFunctions#coord_futureRange_sync()}} having called
{{DFSClient#exists()}}. We need appropriate logging there.
was:
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 {{}}.
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.
> [coordinator] Enhance logging of CoordElFunctions
> -
>
> 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
>Priority: Major
>
> 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
> {{}}.
> 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()}}
> and {{CoordELFunctions#coord_futureRange_sync()}} having called
> {{DFSClient#exists()}}. We need appropriate logging there.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
