[
https://issues.apache.org/jira/browse/KUDU-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760123#comment-17760123
]
ASF subversion and git services commented on KUDU-3508:
-------------------------------------------------------
Commit ecb51af801bd1bf40d0216b0697bf7e5765461d5 in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=ecb51af80 ]
KUDU-3508 increase Ranger start timeout to 120 seconds
The motivation behind this update was seeing too many failures of the
corresponding tests scenarios from master_authz-itest when running those
concurrently with a few other tests at machines with modest amount
of memory.
I20230828 11:54:03.676172 3469 mini_ranger.cc:169] Time spent starting
Ranger: real 95.987s user 0.047s sys 0.184s
src/kudu/integration-tests/external_mini_cluster-itest-base.cc:66: Failure
Failed
Change-Id: I3b3a9a8dc595c55bfe3fdcf003632a670f1142d5
Reviewed-on: http://gerrit.cloudera.org:8080/20432
Tested-by: Kudu Jenkins
Reviewed-by: Abhishek Chennaka <achenn...@cloudera.com>
> Increase Ranger start timeout to 120 seconds
> --------------------------------------------
>
> Key: KUDU-3508
> URL: https://issues.apache.org/jira/browse/KUDU-3508
> Project: Kudu
> Issue Type: Test
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Priority: Minor
>
> Ranger, being a Java application, consumes a lot of is a memory and CPU,
> especially during the startup phase. Due to that, it often cannot start
> within 90 seconds on machines with modest amount of memory, in the presence
> of other concurrent activity (e.g., if several tests are being run
> concurrently). In most cases, the following error is reported because the
> current allowance for Ranger's start up is 90 seconds:
>
> I20230828 11:54:03.676172 3469 mini_ranger.cc:169] Time spent starting
> Ranger: real 95.987s user 0.047s sys 0.184s
> src/kudu/integration-tests/external_mini_cluster-itest-base.cc:66: Failure
> Failed
> Let's increase the startup allowance up to 120 seconds, so corresponding test
> scenarios in {{master_authz-itest}} wont fail so often in such test
> environments.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
