tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "TezQA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEZ-4028) Events not visible from proto history logging for s3a filesystem until dag completes.
Date Thu, 10 Jan 2019 06:59:00 GMT

    [ https://issues.apache.org/jira/browse/TEZ-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739126#comment-16739126
] 

TezQA commented on TEZ-4028:
----------------------------

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 14s{color} | {color:blue}
Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {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:green}+1{color} | {color:green} test4tests {color} | {color:green}  0m  0s{color}
| {color:green} The patch appears to include 1 new or modified test files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 50s{color} | {color:blue}
Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 45s{color}
| {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 46s{color} |
{color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 54s{color}
| {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  1m 20s{color} |
{color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 47s{color} |
{color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 17s{color} | {color:blue}
Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 48s{color}
| {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 42s{color} |
{color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 24s{color} | {color:green}
tez-api in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 18s{color} | {color:green}
tez-plugins_tez-protobuf-history-plugin generated 0 new + 0 unchanged - 2 fixed = 0 total
(was 2) {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}  0m 28s{color}
| {color:orange} tez-api: The patch generated 8 new + 689 unchanged - 3 fixed = 697 total
(was 692) {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}  0m 16s{color}
| {color:orange} tez-plugins/tez-protobuf-history-plugin: The patch generated 5 new + 45 unchanged
- 0 fixed = 50 total (was 45) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m  0s{color}
| {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  1m 33s{color} |
{color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 47s{color} |
{color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  1m 44s{color} | {color:green}
tez-api in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  0m 24s{color} | {color:green}
tez-protobuf-history-plugin in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 25s{color}
| {color:green} The patch does not generate ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 18m  7s{color} | {color:black}
{color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/tez:d4a62de |
| JIRA Issue | TEZ-4028 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12954394/TEZ-4028.02.patch
|
| Optional Tests |  dupname  asflicense  javac  javadoc  unit  findbugs  checkstyle  compile
 |
| uname | Linux 42c05da354fa 4.4.0-138-generic #164~14.04.1-Ubuntu SMP Fri Oct 5 08:56:16
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | master / a031817 |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_191 |
| findbugs | v3.0.1 |
| checkstyle | https://builds.apache.org/job/PreCommit-TEZ-Build/78/artifact/out/diff-checkstyle-tez-api.txt
|
| checkstyle | https://builds.apache.org/job/PreCommit-TEZ-Build/78/artifact/out/diff-checkstyle-tez-plugins_tez-protobuf-history-plugin.txt
|
|  Test Results | https://builds.apache.org/job/PreCommit-TEZ-Build/78/testReport/ |
| Max. process+thread count | 242 (vs. ulimit of 10000) |
| modules | C: tez-api tez-plugins/tez-protobuf-history-plugin U: . |
| Console output | https://builds.apache.org/job/PreCommit-TEZ-Build/78/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> Events not visible from proto history logging for s3a filesystem until dag completes.
> -------------------------------------------------------------------------------------
>
>                 Key: TEZ-4028
>                 URL: https://issues.apache.org/jira/browse/TEZ-4028
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Harish Jaiprakash
>            Assignee: Harish Jaiprakash
>            Priority: Major
>         Attachments: TEZ-4028.01.patch, TEZ-4028.02.patch
>
>
> The events are not visible in the files because  s3 filesystem
> * flush writes to local disk and only upload/commit to s3 on close.
> * does not support append
> As an initial fix we log the dag submitted, initialized and started events into a file
and these can be read to get the dag plan, config from the AM. The counters are anyways not
available until the dag completes.
> The in-progress information cannot be read, this can be obtained from the AM once we
have the above events.



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

Mime
View raw message