[
https://issues.apache.org/jira/browse/RANGER-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673900#comment-16673900
]
Pradeep Agrawal commented on RANGER-2275:
-----------------------------------------
Committed in:
master branch:
[https://github.com/apache/ranger/commit/ac1b1bdf39b96e53282ba989c865cd819d5d4b68]
ranger-1.2 branch:
https://github.com/apache/ranger/commit/a337dd8bc13584d52914c76723b952b931c8e48a
ranger-1.1 branch:
https://github.com/apache/ranger/commit/186a07bd928726b0d55419fb358ad401514f3422
ranger-1
branch:https://github.com/apache/ranger/commit/051d2e988ef3ddd461df70bf9f9631771305b398
> Make db_setup retry delay configurable
> --------------------------------------
>
> Key: RANGER-2275
> URL: https://issues.apache.org/jira/browse/RANGER-2275
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Pradeep Agrawal
> Assignee: Pradeep Agrawal
> Priority: Major
> Fix For: 1.0.1, 2.0.0, 1.1.1, 1.2.1
>
>
> In an HA setup, Ranger Admin on both master nodes attempts to create/patch
> the DB and change passwords. If one of them detects contention for an
> operation, it sleeps and re-checks later. The length of sleep is fixed at 120
> seconds
> It would be better to make this delay configurable (in seconds) so that user
> can adjust the delay value as per his environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
