hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Szita (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-18212) Make sure Yetus check always has a full log
Date Mon, 04 Dec 2017 11:38:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-18212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Adam Szita updated HIVE-18212:
------------------------------
    Status: Patch Available  (was: In Progress)

> Make sure Yetus check always has a full log
> -------------------------------------------
>
>                 Key: HIVE-18212
>                 URL: https://issues.apache.org/jira/browse/HIVE-18212
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Adam Szita
>            Assignee: Adam Szita
>         Attachments: HIVE-18212.0.patch
>
>
> Some yetus log files are left incomplete, and in these same runs {{tee}} subprocesses
are left running and dangling on the ptest server.
> This is because of a bug in the yetus runner velocity template script where we make a
redirection of stdout:
> {code}
> ./dev-support/test-patch.sh ${patchFile} ..... 2>&1 | tee ${logFile}
> {code}
> If the yetus output is big enough (>62K) tee will stop writing the log file and is
left running even after {{test-patch.sh}} finished successfully. This because we don't make
anything consume the stdout and most probably some buffers get full on Linux side.
> We should also make sure that yetus runs(since they are executed parallel to ptest test
phase) are not interfering with each other in case they run very long and overlap.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message