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

Zoltan Haindrich commented on HIVE-23563:
-----------------------------------------

yesterday I misconfigured a container and noticed that kubernetes is 
agressively takes away cpu if I hit the cpulimit...I've also raised the 
cpulimit and run the tests twice  - since it came back good I left it in this 
patch


> Early abort the build in case new commits are added to the PR
> -------------------------------------------------------------
>
>                 Key: HIVE-23563
>                 URL: https://issues.apache.org/jira/browse/HIVE-23563
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Build Infrastructure
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> if the job is waiting for a long to acquire the lock for a long time; it 
> would be favourable to do a quick check after lock acqusition wether there 
> are new triggers
> https://github.com/apache/hive/pull/948#discussion_r432093713



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

Reply via email to