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

Posted to issues@hive.apache.org by "RuiChen (Jira)" <ji...@apache.org> on 2020/04/17 09:15:00 UTC

[jira] [Assigned] (HIVE-23233) Using default operation logs location cause hive service session testing failed

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

RuiChen reassigned HIVE-23233:
------------------------------

    Assignee: RuiChen

> Using default operation logs location cause hive service session testing failed
> -------------------------------------------------------------------------------
>
>                 Key: HIVE-23233
>                 URL: https://issues.apache.org/jira/browse/HIVE-23233
>             Project: Hive
>          Issue Type: Bug
>            Reporter: RuiChen
>            Assignee: RuiChen
>            Priority: Minor
>
> TestSessionCleanup and TestSessionManagerMetrics tests apply the default operation logs location "ConfVars.*HIVE_SERVER2_LOGGING_OPERATION_LOG_LOCATION*", it's same OS path, in TestSessionManagerMetrics SessionManager will delete the operation logs directory on testing exit, and in TestSessionCleanup the file count will be checked in operation logs directory, so if these test cases are executed in parrallel, they will impact each other.
> I run Hive tests in my local machine and enable maven parallel mode to run tests with option "-T 4 -DforkCount=4", it will run test class in separeted processes and execute test class in parallel, you can try to run tests several times, this issue should happen.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)