[jira] [Updated] (TEZ-4106) Add Exponential Smooth RuntimeEstimator to the speculator
[ https://issues.apache.org/jira/browse/TEZ-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ahmed Hussein updated TEZ-4106: --- Description: Tez speculator implements start-end runtime estimator. Similar to [MAPREDUCE-7208|https://issues.apache.org/jira/browse/MAPREDUCE-7208], we need to implement an adaptive estimator based on smooth Exponential > Add Exponential Smooth RuntimeEstimator to the speculator > - > > Key: TEZ-4106 > URL: https://issues.apache.org/jira/browse/TEZ-4106 > Project: Apache Tez > Issue Type: Improvement >Reporter: Ahmed Hussein >Assignee: Ahmed Hussein >Priority: Major > > Tez speculator implements start-end runtime estimator. Similar to > [MAPREDUCE-7208|https://issues.apache.org/jira/browse/MAPREDUCE-7208], we > need to implement an adaptive estimator based on smooth Exponential -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (TEZ-4106) Add Exponential Smooth RuntimeEstimator to the speculator
Ahmed Hussein created TEZ-4106: -- Summary: Add Exponential Smooth RuntimeEstimator to the speculator Key: TEZ-4106 URL: https://issues.apache.org/jira/browse/TEZ-4106 Project: Apache Tez Issue Type: Improvement Reporter: Ahmed Hussein Assignee: Ahmed Hussein -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEZ-4098) tez-tools improvements: log-split, swimlane
[
https://issues.apache.org/jira/browse/TEZ-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16991440#comment-16991440
]
TezQA commented on TEZ-4098:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue} 0m
0s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:orange}-0{color} | {color:orange} pylint {color} | {color:orange} 0m
4s{color} | {color:orange} The patch generated 45 new + 256 unchanged - 1 fixed
= 301 total (was 257) {color} |
| {color:red}-1{color} | {color:red} shellcheck {color} | {color:red} 0m
1s{color} | {color:red} The patch generated 12 new + 0 unchanged - 4 fixed = 12
total (was 4) {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch 6 line(s) with tabs. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
8s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 0m 54s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.5 Server=19.03.5 Image:yetus/tez:d4a62deee |
| JIRA Issue | TEZ-4098 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12988304/TEZ-4098.02.patch |
| Optional Tests | dupname asflicense pylint shellcheck shelldocs |
| uname | Linux 012216d98c05 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6
11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | master / 1af0897 |
| maven | version: Apache Maven 3.3.9 |
| shellcheck | v0.4.6 |
| pylint | v1.9.2 |
| pylint |
https://builds.apache.org/job/PreCommit-TEZ-Build/214/artifact/out/diff-patch-pylint.txt
|
| shellcheck |
https://builds.apache.org/job/PreCommit-TEZ-Build/214/artifact/out/diff-patch-shellcheck.txt
|
| whitespace |
https://builds.apache.org/job/PreCommit-TEZ-Build/214/artifact/out/whitespace-tabs.txt
|
| Max. process+thread count | 47 (vs. ulimit of 5500) |
| modules | C: tez-tools U: tez-tools |
| Console output |
https://builds.apache.org/job/PreCommit-TEZ-Build/214/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> tez-tools improvements: log-split, swimlane
> ---
>
> Key: TEZ-4098
> URL: https://issues.apache.org/jira/browse/TEZ-4098
> Project: Apache Tez
> Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Attachments: TEZ-4098.01.patch, TEZ-4098.02.patch
>
>
> While using tez-tools for analyzing application logs, I'm about to improve
> them a little bit. Details will be added here to the description.
> 1. Support swimlane.sh to consume local file
> 2. Create a log splitter, which is able to split the aggregated log file into
> separate container directories, like below:
> {code}
> ├── container_e02_1572948601374_0004_01_01
> │ ├── container-localizer-syslog
> │ ├── dag_1572948601374_0004_1.dot
> │ ├── prelaunch.err
> │ ├── prelaunch.out
> │ ├── stderr
> │ ├── stdout
> │ ├── syslog
> │ ├── syslog_dag_1572948601374_0004_1
> │ └── syslog_dag_1572948601374_0004_1_post
> ├── container_e02_1572948601374_0004_01_02
> │ ├── prelaunch.err
> │ ├── prelaunch.out
> │ ├── stderr
> │ ├── stdout
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (TEZ-4098) tez-tools improvements: log-split, swimlane
[
https://issues.apache.org/jira/browse/TEZ-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16991421#comment-16991421
]
László Bodor edited comment on TEZ-4098 at 12/9/19 9:47 AM:
thanks [~rajesh.balamohan] for the idea, I just simply appended hostname to
container folder's name, like this:
{code}
├── container_e10_1575565459633_0004_01_01_vc0525.halxg.cloudera.com_8041
│ ├── container-localizer-syslog
│ ├── dag_1575565459633_0004_1-tez-dag.pb.txt
│ ├── dag_1575565459633_0004_1.dot
│ ├── prelaunch.err
│ ├── prelaunch.out
│ ├── stderr
│ ├── stdout
│ ├── syslog
│ ├── syslog_dag_1575565459633_0004_1
│ └── syslog_dag_1575565459633_0004_1_post
├── container_e10_1575565459633_0004_01_02_vc0528.halxg.cloudera.com_8041
│ ├── container-localizer-syslog
│ ├── prelaunch.err
│ ├── prelaunch.out
│ ├── stderr
│ ├── stdout
│ ├── syslog
│ └── syslog_attempt_1575565459633_0004_1_00_00_0
├── container_e10_1575565459633_0004_01_03_vc0536.halxg.cloudera.com_8041
│ ├── container-localizer-syslog
│ ├── prelaunch.err
│ ├── prelaunch.out
│ ├── stderr
│ ├── stdout
│ ├── syslog
│ └── syslog_attempt_1575565459633_0004_1_00_00_1
├── container_e10_1575565459633_0004_01_04_vc0526.halxg.cloudera.com_8041
│ ├── container-localizer-syslog
│ ├── prelaunch.err
│ ├── prelaunch.out
│ ├── stderr
│ ├── stdout
│ ├── syslog
│ └── syslog_attempt_1575565459633_0004_1_00_00_2
└── container_e10_1575565459633_0004_01_05_vc0529.halxg.cloudera.com_8041
├── container-localizer-syslog
├── prelaunch.err
├── prelaunch.out
├── stderr
├── stdout
├── syslog
└── syslog_attempt_1575565459633_0004_1_00_00_3
{code}
(maybe you meant to introduce a top level folder stucture for machine names,
that could work as well, not sure which is better)
was (Author: abstractdog):
thanks [~rajesh.balamohan] for the idea, I just simply appended hostname to
container folder's name, like this:
{code}
├── container_e10_1575565459633_0004_01_01_vc0525.halxg.cloudera.com_8041
│ ├── container-localizer-syslog
│ ├── dag_1575565459633_0004_1-tez-dag.pb.txt
│ ├── dag_1575565459633_0004_1.dot
│ ├── prelaunch.err
│ ├── prelaunch.out
│ ├── stderr
│ ├── stdout
│ ├── syslog
│ ├── syslog_dag_1575565459633_0004_1
│ └── syslog_dag_1575565459633_0004_1_post
├── container_e10_1575565459633_0004_01_02_vc0528.halxg.cloudera.com_8041
│ ├── container-localizer-syslog
│ ├── prelaunch.err
│ ├── prelaunch.out
│ ├── stderr
│ ├── stdout
│ ├── syslog
│ └── syslog_attempt_1575565459633_0004_1_00_00_0
├── container_e10_1575565459633_0004_01_03_vc0536.halxg.cloudera.com_8041
│ ├── container-localizer-syslog
│ ├── prelaunch.err
│ ├── prelaunch.out
│ ├── stderr
│ ├── stdout
│ ├── syslog
│ └── syslog_attempt_1575565459633_0004_1_00_00_1
├── container_e10_1575565459633_0004_01_04_vc0526.halxg.cloudera.com_8041
│ ├── container-localizer-syslog
│ ├── prelaunch.err
│ ├── prelaunch.out
│ ├── stderr
│ ├── stdout
│ ├── syslog
│ └── syslog_attempt_1575565459633_0004_1_00_00_2
└── container_e10_1575565459633_0004_01_05_vc0529.halxg.cloudera.com_8041
├── container-localizer-syslog
├── prelaunch.err
├── prelaunch.out
├── stderr
├── stdout
├── syslog
└── syslog_attempt_1575565459633_0004_1_00_00_3
{code}
> tez-tools improvements: log-split, swimlane
> ---
>
> Key: TEZ-4098
> URL: https://issues.apache.org/jira/browse/TEZ-4098
> Project: Apache Tez
> Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Attachments: TEZ-4098.01.patch, TEZ-4098.02.patch
>
>
> While using tez-tools for analyzing application logs, I'm about to improve
> them a little bit. Details will be added here to the description.
> 1. Support swimlane.sh to consume local file
> 2. Create a log splitter, which is able to split the aggregated log file into
> separate container directories, like below:
> {code}
> ├── container_e02_1572948601374_0004_01_01
> │ ├── container-localizer-syslog
> │ ├── dag_1572948601374_0004_1.dot
> │ ├── prelaunch.err
> │ ├── prelaunch.out
> │ ├── stderr
> │ ├── stdout
> │ ├── syslog
> │ ├── syslog_dag_1572948601374_0004_1
> │ └── syslog_dag_1572948601374_0004_1_post
> ├── container_e02_1572948601374_0004_01_02
> │ ├── prelaunch.err
> │ ├── prelaunch.out
> │ ├── stderr
> │ ├── stdout
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (TEZ-4098) tez-tools improvements: log-split, swimlane
[
https://issues.apache.org/jira/browse/TEZ-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated TEZ-4098:
--
Attachment: TEZ-4098.02.patch
> tez-tools improvements: log-split, swimlane
> ---
>
> Key: TEZ-4098
> URL: https://issues.apache.org/jira/browse/TEZ-4098
> Project: Apache Tez
> Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Attachments: TEZ-4098.01.patch, TEZ-4098.02.patch
>
>
> While using tez-tools for analyzing application logs, I'm about to improve
> them a little bit. Details will be added here to the description.
> 1. Support swimlane.sh to consume local file
> 2. Create a log splitter, which is able to split the aggregated log file into
> separate container directories, like below:
> {code}
> ├── container_e02_1572948601374_0004_01_01
> │ ├── container-localizer-syslog
> │ ├── dag_1572948601374_0004_1.dot
> │ ├── prelaunch.err
> │ ├── prelaunch.out
> │ ├── stderr
> │ ├── stdout
> │ ├── syslog
> │ ├── syslog_dag_1572948601374_0004_1
> │ └── syslog_dag_1572948601374_0004_1_post
> ├── container_e02_1572948601374_0004_01_02
> │ ├── prelaunch.err
> │ ├── prelaunch.out
> │ ├── stderr
> │ ├── stdout
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (TEZ-4098) tez-tools improvements: log-split, swimlane
[
https://issues.apache.org/jira/browse/TEZ-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16991421#comment-16991421
]
László Bodor commented on TEZ-4098:
---
thanks [~rajesh.balamohan] for the idea, I just simply appended hostname to
container folder's name, like this:
{code}
├── container_e10_1575565459633_0004_01_01_vc0525.halxg.cloudera.com_8041
│ ├── container-localizer-syslog
│ ├── dag_1575565459633_0004_1-tez-dag.pb.txt
│ ├── dag_1575565459633_0004_1.dot
│ ├── prelaunch.err
│ ├── prelaunch.out
│ ├── stderr
│ ├── stdout
│ ├── syslog
│ ├── syslog_dag_1575565459633_0004_1
│ └── syslog_dag_1575565459633_0004_1_post
├── container_e10_1575565459633_0004_01_02_vc0528.halxg.cloudera.com_8041
│ ├── container-localizer-syslog
│ ├── prelaunch.err
│ ├── prelaunch.out
│ ├── stderr
│ ├── stdout
│ ├── syslog
│ └── syslog_attempt_1575565459633_0004_1_00_00_0
├── container_e10_1575565459633_0004_01_03_vc0536.halxg.cloudera.com_8041
│ ├── container-localizer-syslog
│ ├── prelaunch.err
│ ├── prelaunch.out
│ ├── stderr
│ ├── stdout
│ ├── syslog
│ └── syslog_attempt_1575565459633_0004_1_00_00_1
├── container_e10_1575565459633_0004_01_04_vc0526.halxg.cloudera.com_8041
│ ├── container-localizer-syslog
│ ├── prelaunch.err
│ ├── prelaunch.out
│ ├── stderr
│ ├── stdout
│ ├── syslog
│ └── syslog_attempt_1575565459633_0004_1_00_00_2
└── container_e10_1575565459633_0004_01_05_vc0529.halxg.cloudera.com_8041
├── container-localizer-syslog
├── prelaunch.err
├── prelaunch.out
├── stderr
├── stdout
├── syslog
└── syslog_attempt_1575565459633_0004_1_00_00_3
{code}
> tez-tools improvements: log-split, swimlane
> ---
>
> Key: TEZ-4098
> URL: https://issues.apache.org/jira/browse/TEZ-4098
> Project: Apache Tez
> Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Attachments: TEZ-4098.01.patch
>
>
> While using tez-tools for analyzing application logs, I'm about to improve
> them a little bit. Details will be added here to the description.
> 1. Support swimlane.sh to consume local file
> 2. Create a log splitter, which is able to split the aggregated log file into
> separate container directories, like below:
> {code}
> ├── container_e02_1572948601374_0004_01_01
> │ ├── container-localizer-syslog
> │ ├── dag_1572948601374_0004_1.dot
> │ ├── prelaunch.err
> │ ├── prelaunch.out
> │ ├── stderr
> │ ├── stdout
> │ ├── syslog
> │ ├── syslog_dag_1572948601374_0004_1
> │ └── syslog_dag_1572948601374_0004_1_post
> ├── container_e02_1572948601374_0004_01_02
> │ ├── prelaunch.err
> │ ├── prelaunch.out
> │ ├── stderr
> │ ├── stdout
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
