You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (Jira)" <ji...@apache.org> on 2023/08/28 22:07:00 UTC
[jira] [Created] (KUDU-3508) Increase Ranger start timeout to 120 seconds
Alexey Serbin created KUDU-3508:
-----------------------------------
Summary: 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
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)