Re: Review Request 73884: RANGER-3632 log improve, cherry-pick from master to ranger-2.3

[bhavik patel]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73884/#review224300
---


Ship it!




Ship It!

- bhavik patel


On March 2, 2022, 3:33 p.m., Kirby Zhou wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73884/
> ---
> 
> (Updated March 2, 2022, 3:33 p.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-3632
> https://issues.apache.org/jira/browse/RANGER-3632
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> See https://reviews.apache.org/r/73857/
> 
> 
> Diffs
> -
> 
>   dev-support/ranger-docker/scripts/ranger-admin-install-postgres.properties 
> 53563e2fd 
>   embeddedwebserver/scripts/ranger-admin-services.sh 54ac41056 
>   
> embeddedwebserver/src/main/java/org/apache/ranger/server/tomcat/EmbeddedServer.java
>  f5636e180 
>   
> embeddedwebserver/src/main/java/org/apache/ranger/server/tomcat/EmbeddedServerUtil.java
>  b05db77e6 
>   ranger-tools/scripts/README.txt 81b5b6678 
>   security-admin/scripts/changepasswordutil.py c9c4edcb6 
>   security-admin/scripts/changeusernameutil.py 45c0ef748 
>   security-admin/scripts/db_setup.py db6983e17 
>   security-admin/scripts/install.properties f162e4fd7 
>   security-admin/scripts/rolebasedusersearchutil.py f9feddce2 
>   security-admin/scripts/setup.sh e8b94f0d6 
>   security-admin/scripts/updateUserAndGroupNamesInJson.py b115d2241 
>   security-admin/src/bin/ranger_install.py 90ac92a0e 
>   security-admin/src/main/resources/conf.dist/ranger-admin-default-site.xml 
> ebc00628c 
>   security-admin/src/main/webapp/WEB-INF/db_patch.logback.xml PRE-CREATION 
>   security-admin/src/main/webapp/WEB-INF/logback.xml  
>   security-admin/src/test/resources/logback-test.xml PRE-CREATION 
>   tagsync/scripts/setup.py d11facaf8 
>   unixauthservice/scripts/setup.py 708a2105a 
> 
> 
> Diff: https://reviews.apache.org/r/73884/diff/2/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Kirby Zhou
> 
>

[jira] [Commented] (RANGER-3702) RANGER - Export policy in excel is failing.

[Bhavik Patel (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520922#comment-17520922
 ] 

Bhavik Patel commented on RANGER-3702:
--

master branch commit link: 
[https://github.com/apache/ranger/commit/8b98899ce42e989523e50f450b9b21a8c9a559a4]

Not able apply the same patch on ranger-2.3 branch. Please check and create new 
RR.

> RANGER - Export policy in excel is failing.
> ---
>
> Key: RANGER-3702
> URL: https://issues.apache.org/jira/browse/RANGER-3702
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Mateen N Mansoori
>Assignee: Mateen Mansoori
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> Export policy in excel is failing with the below error : 
>  
> {code:java}
> java.lang.NoClassDefFoundError: org/apache/logging/log4j/LogManager
>   at org.apache.poi.POIDocument.(POIDocument.java:65)
>   at 
> org.apache.ranger.biz.ServiceDBStore.writeExcel(ServiceDBStore.java:3991)
>   at 
> org.apache.ranger.biz.ServiceDBStore.getPoliciesInExcel(ServiceDBStore.java:2428)
>   at 
> org.apache.ranger.rest.ServiceREST.getPoliciesInExcel(ServiceREST.java:1985) 
> {code}
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3693) Ranger - Upgrade tomcat to 8.5.78

[Bhavik Patel (Jira)]

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

Bhavik Patel updated RANGER-3693:
-
Affects Version/s: 2.3.0

> Ranger - Upgrade tomcat to 8.5.78
> -
>
> Key: RANGER-3693
> URL: https://issues.apache.org/jira/browse/RANGER-3693
> Project: Ranger
>  Issue Type: Task
>  Components: Ranger
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Mateen N Mansoori
>Assignee: Mateen Mansoori
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> Currently ranger is pulling tomcat - 8.5.76, This task is to upgrade tomcat 
> version to 8.5.78.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (RANGER-3693) Ranger - Upgrade tomcat to 8.5.78

[Bhavik Patel (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520919#comment-17520919
 ] 

Bhavik Patel commented on RANGER-3693:
--

ranger-2.3 branch commit link: 
https://github.com/apache/ranger/commit/3bcfe85a5dbcfa7825fc500ac3b5e945a9c44ef1

> Ranger - Upgrade tomcat to 8.5.78
> -
>
> Key: RANGER-3693
> URL: https://issues.apache.org/jira/browse/RANGER-3693
> Project: Ranger
>  Issue Type: Task
>  Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Mateen N Mansoori
>Assignee: Mateen Mansoori
>Priority: Major
> Fix For: 3.0.0
>
>
> Currently ranger is pulling tomcat - 8.5.76, This task is to upgrade tomcat 
> version to 8.5.78.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3693) Ranger - Upgrade tomcat to 8.5.78

[Bhavik Patel (Jira)]

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

Bhavik Patel updated RANGER-3693:
-
Fix Version/s: 2.3.0

> Ranger - Upgrade tomcat to 8.5.78
> -
>
> Key: RANGER-3693
> URL: https://issues.apache.org/jira/browse/RANGER-3693
> Project: Ranger
>  Issue Type: Task
>  Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Mateen N Mansoori
>Assignee: Mateen Mansoori
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> Currently ranger is pulling tomcat - 8.5.76, This task is to upgrade tomcat 
> version to 8.5.78.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (RANGER-3693) Ranger - Upgrade tomcat to 8.5.78

[Mateen N Mansoori (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520916#comment-17520916
 ] 

Mateen N Mansoori commented on RANGER-3693:
---

[~bpatel] please merge in 2.3 branch also, Thanks.

> Ranger - Upgrade tomcat to 8.5.78
> -
>
> Key: RANGER-3693
> URL: https://issues.apache.org/jira/browse/RANGER-3693
> Project: Ranger
>  Issue Type: Task
>  Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Mateen N Mansoori
>Assignee: Mateen Mansoori
>Priority: Major
> Fix For: 3.0.0
>
>
> Currently ranger is pulling tomcat - 8.5.76, This task is to upgrade tomcat 
> version to 8.5.78.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: Review Request 73941: RANGER-3705: Improve logging messages to help debug potential issues

[Ramesh Mani]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73941/#review224299
---


Ship it!




Ship It!

- Ramesh Mani


On April 11, 2022, 8:52 p.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73941/
> ---
> 
> (Updated April 11, 2022, 8:52 p.m.)
> 
> 
> Review request for ranger, Madhan Neethiraj and Ramesh Mani.
> 
> 
> Bugs: RANGER-3705
> https://issues.apache.org/jira/browse/RANGER-3705
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Add/improve logging messages to help debugging potential issues.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerServiceResourceMatcher.java
>  7b02dd6e1 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerResourceTrie.java
>  331d6371d 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java
>  12fecd030 
> 
> 
> Diff: https://reviews.apache.org/r/73941/diff/2/
> 
> 
> Testing
> ---
> 
> Built clean and passed all unit tests.
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>

Re: Review Request 73941: RANGER-3705: Improve logging messages to help debug potential issues

[Madhan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73941/#review224298
---


Ship it!




Ship It!

- Madhan Neethiraj


On April 11, 2022, 8:52 p.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73941/
> ---
> 
> (Updated April 11, 2022, 8:52 p.m.)
> 
> 
> Review request for ranger, Madhan Neethiraj and Ramesh Mani.
> 
> 
> Bugs: RANGER-3705
> https://issues.apache.org/jira/browse/RANGER-3705
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Add/improve logging messages to help debugging potential issues.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerServiceResourceMatcher.java
>  7b02dd6e1 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerResourceTrie.java
>  331d6371d 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java
>  12fecd030 
> 
> 
> Diff: https://reviews.apache.org/r/73941/diff/2/
> 
> 
> Testing
> ---
> 
> Built clean and passed all unit tests.
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>

Re: Review Request 73941: RANGER-3705: Improve logging messages to help debug potential issues

[Abhay Kulkarni]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73941/
---

(Updated April 11, 2022, 8:52 p.m.)


Review request for ranger, Madhan Neethiraj and Ramesh Mani.


Changes
---

Addressed review comment


Bugs: RANGER-3705
https://issues.apache.org/jira/browse/RANGER-3705


Repository: ranger


Description
---

Add/improve logging messages to help debugging potential issues.


Diffs (updated)
-

  
agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerServiceResourceMatcher.java
 7b02dd6e1 
  
agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerResourceTrie.java
 331d6371d 
  
agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java
 12fecd030 


Diff: https://reviews.apache.org/r/73941/diff/2/

Changes: https://reviews.apache.org/r/73941/diff/1-2/


Testing
---

Built clean and passed all unit tests.


Thanks,

Abhay Kulkarni

Re: Review Request 73941: RANGER-3705: Improve logging messages to help debug potential issues

[Abhay Kulkarni]

> On April 11, 2022, 7:34 p.m., Ramesh Mani wrote:
> > agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java
> > Line 1125 (original), 1135 (patched)
> > 
> >
> > should we consider auditPolicyId() also for this override?

Chained plugins, in the current form, are used to re-evaluate access policies 
across multiple component services. Perhaps considering audit policies with 
chained plugins can be addressed in another functional JIRA. This JIRA is 
mainly to consider improving log messages for help during debugging.


- Abhay


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73941/#review224295
---


On April 11, 2022, 5:58 p.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73941/
> ---
> 
> (Updated April 11, 2022, 5:58 p.m.)
> 
> 
> Review request for ranger, Madhan Neethiraj and Ramesh Mani.
> 
> 
> Bugs: RANGER-3705
> https://issues.apache.org/jira/browse/RANGER-3705
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Add/improve logging messages to help debugging potential issues.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerServiceResourceMatcher.java
>  7b02dd6e1 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerResourceTrie.java
>  331d6371d 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java
>  12fecd030 
> 
> 
> Diff: https://reviews.apache.org/r/73941/diff/1/
> 
> 
> Testing
> ---
> 
> Built clean and passed all unit tests.
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>

Re: Review Request 73941: RANGER-3705: Improve logging messages to help debug potential issues

[Madhan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73941/#review224296
---




agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java
Line 1103 (original), 1113 (patched)


result.policyId could be -1 when isAccessDetermined=true, for example when 
user is a superuser. And Solr plugin has a differnt scenario which would have 
policyId=-1 and isAccessDetermined=true.

With this update, such decisions would be overwritten by chained plugin. 
Please review.


- Madhan Neethiraj


On April 11, 2022, 5:58 p.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73941/
> ---
> 
> (Updated April 11, 2022, 5:58 p.m.)
> 
> 
> Review request for ranger, Madhan Neethiraj and Ramesh Mani.
> 
> 
> Bugs: RANGER-3705
> https://issues.apache.org/jira/browse/RANGER-3705
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Add/improve logging messages to help debugging potential issues.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerServiceResourceMatcher.java
>  7b02dd6e1 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerResourceTrie.java
>  331d6371d 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java
>  12fecd030 
> 
> 
> Diff: https://reviews.apache.org/r/73941/diff/1/
> 
> 
> Testing
> ---
> 
> Built clean and passed all unit tests.
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>

[jira] [Commented] (RANGER-3691) Upgrade spring to 5.3.18 CVE-2022-22965

[Ramesh Mani (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520784#comment-17520784
 ] 

Ramesh Mani commented on RANGER-3691:
-

[~kirbyzhou]  [~z0ltrix]  could you please provide your opinion on the  above 
comment?

> Upgrade spring to 5.3.18 CVE-2022-22965
> ---
>
> Key: RANGER-3691
> URL: https://issues.apache.org/jira/browse/RANGER-3691
> Project: Ranger
>  Issue Type: Bug
>  Components: admin, kms
>Reporter: kirby zhou
>Assignee: kirby zhou
>Priority: Blocker
> Fix For: 3.0.0
>
>
> [https://tanzu.vmware.com/security/cve-2022-22965|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22965]
> [https://github.com/spring-projects/spring-framework/releases]
>  
> Spring has a new 0day Remote-Code-Execution problem, related to spring-beans 
> and JDK9+
> Fixed at spring 5.3.18 / 5.2.20
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: Review Request 73941: RANGER-3705: Improve logging messages to help debug potential issues

[Ramesh Mani]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73941/#review224295
---




agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java
Line 1125 (original), 1135 (patched)


should we consider auditPolicyId() also for this override?


- Ramesh Mani


On April 11, 2022, 5:58 p.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73941/
> ---
> 
> (Updated April 11, 2022, 5:58 p.m.)
> 
> 
> Review request for ranger, Madhan Neethiraj and Ramesh Mani.
> 
> 
> Bugs: RANGER-3705
> https://issues.apache.org/jira/browse/RANGER-3705
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Add/improve logging messages to help debugging potential issues.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerServiceResourceMatcher.java
>  7b02dd6e1 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerResourceTrie.java
>  331d6371d 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java
>  12fecd030 
> 
> 
> Diff: https://reviews.apache.org/r/73941/diff/1/
> 
> 
> Testing
> ---
> 
> Built clean and passed all unit tests.
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>

Review Request 73941: RANGER-3705: Improve logging messages to help debug potential issues

[Abhay Kulkarni]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73941/
---

Review request for ranger, Madhan Neethiraj and Ramesh Mani.


Bugs: RANGER-3705
https://issues.apache.org/jira/browse/RANGER-3705


Repository: ranger


Description
---

Add/improve logging messages to help debugging potential issues.


Diffs
-

  
agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerServiceResourceMatcher.java
 7b02dd6e1 
  
agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerResourceTrie.java
 331d6371d 
  
agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java
 12fecd030 


Diff: https://reviews.apache.org/r/73941/diff/1/


Testing
---

Built clean and passed all unit tests.


Thanks,

Abhay Kulkarni

[jira] [Created] (RANGER-3705) Improve logging messages to help debug potential issues

[Abhay Kulkarni (Jira)]

Abhay Kulkarni created RANGER-3705:
--

 Summary: Improve logging messages to help debug potential issues
 Key: RANGER-3705
 URL: https://issues.apache.org/jira/browse/RANGER-3705
 Project: Ranger
  Issue Type: Improvement
  Components: Ranger
Reporter: Abhay Kulkarni


Add/improve logging messages to help debugging potential issues.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Assigned] (RANGER-3705) Improve logging messages to help debug potential issues

[Abhay Kulkarni (Jira)]

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

Abhay Kulkarni reassigned RANGER-3705:
--

Assignee: Abhay Kulkarni

> Improve logging messages to help debug potential issues
> ---
>
> Key: RANGER-3705
> URL: https://issues.apache.org/jira/browse/RANGER-3705
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Abhay Kulkarni
>Assignee: Abhay Kulkarni
>Priority: Minor
>
> Add/improve logging messages to help debugging potential issues.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: (was: ranger database volume.png)

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger log.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> For example, the related table of Ranger has been created before, and another 
> docker container is started to execute the setup.sh script. However, due to 
> network problems, the criterion fails and the reconstruction operation is 
> being triggered.The initialization log is as follows，
> !ranger log.png!
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Description: 
In the docker container or distributed nodes, the initialization 
script(setup.sh) may be executed many times. Ranger controls the initialization 
process through database table（x_db_version_h）. However, when the number of 
database connections is too large or the network is abnormal, the 
initialization script will judge abnormally, the script will trigger 
reconstruction, and the data will be lost.So is it reasonable to drop tables in 
script(ranger_core_db_XX.sql).

For example, the related table of Ranger has been created before, and another 
docker container is started to execute the setup.sh script. However, due to 
network problems, the criterion fails and the reconstruction operation is being 
triggered.The initialization log is as follows，

!ranger log.png!

 

 

  was:
In the docker container or distributed nodes, the initialization 
script(setup.sh) may be executed many times. Ranger controls the initialization 
process through database table（x_db_version_h）. However, when the number of 
database connections is too large or the network is abnormal, the 
initialization script will judge abnormally, the script will trigger 
reconstruction, and the data will be lost.So is it reasonable to drop tables in 
script(ranger_core_db_XX.sql).

The initialization log is as follows，

!ranger log.png!

The data volume in the Ranger database is as follows，

!ranger database volume.png|width=957,height=360!

 


> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger log.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> For example, the related table of Ranger has been created before, and another 
> docker container is started to execute the setup.sh script. However, due to 
> network problems, the criterion fails and the reconstruction operation is 
> being triggered.The initialization log is as follows，
> !ranger log.png!
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (RANGER-3704) remove semicolon from c3P0 preferredTestQuery

[Pradeep Agrawal (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520606#comment-17520606
 ] 

Pradeep Agrawal commented on RANGER-3704:
-

No, I checked with previous versions also.

> remove semicolon from c3P0 preferredTestQuery
> -
>
> Key: RANGER-3704
> URL: https://issues.apache.org/jira/browse/RANGER-3704
> Project: Ranger
>  Issue Type: Wish
>  Components: Ranger
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: 
> 0001-RANGER-3704-remove-semicolon-from-c3P0-preferredTest.patch
>
>
> Error message:
> {code:java}
> java.sql.SQLSyntaxErrorException: ORA-00933: SQL command not properly ended
>   at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)
>   at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:446)
>   at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1054)
>   at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:623)
>   at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252)
>   at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:612)
>   at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:213)
>   at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:37)
>   at 
> oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:733)
>   at 
> oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:904)
>   at 
> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1082)
>   at 
> oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1276)
>   at 
> oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:366)
>   at 
> com.mchange.v2.c3p0.impl.NewProxyStatement.executeQuery(NewProxyStatement.java:220)
>   at 
> com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:286)
>   at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:510)
>   at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.finerLoggingTestPooledConnection(C3P0PooledConnectionPool.java:452)
>   at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.finerLoggingTestPooledConnection(C3P0PooledConnectionPool.java:444)
>   at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.refurbishIdleResource(C3P0PooledConnectionPool.java:434)
>   at 
> com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask.run(BasicResourcePool.java:2211)
>   at 
> com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)
> Caused by: Error : 933, Position : 18, Sql = select 1 from dual;, OriginalSql 
> = select 1 from dual;, Error Msg = ORA-00933: SQL command not properly ended
>   at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:498)
>   ... 20 more
> 2022-04-11 12:38:45,538 
> [C3P0PooledConnectionPoolManager[identityToken->1br54owao6u0q6i172od24|1f0ea3d4]-HelperThread-#2]
>  DEBUG com.mchange.v2.log.slf4j.Slf4jMLog$Slf4jMLogger$DebugLogger 
> (Slf4jMLog.java:207) - com.mchange.v2.c3p0.impl.NewPooledConnection@5f00a319 
> handling a throwable. {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (RANGER-3704) remove semicolon from c3P0 preferredTestQuery

[Bhavik Patel (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520599#comment-17520599
 ] 

Bhavik Patel commented on RANGER-3704:
--

This issue observed after merging 
[RANGER-3692|https://github.com/apache/ranger/commit/a93571daedaa45ffc98869410148cf1c55a90eaf]
 ?

> remove semicolon from c3P0 preferredTestQuery
> -
>
> Key: RANGER-3704
> URL: https://issues.apache.org/jira/browse/RANGER-3704
> Project: Ranger
>  Issue Type: Wish
>  Components: Ranger
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: 
> 0001-RANGER-3704-remove-semicolon-from-c3P0-preferredTest.patch
>
>
> Error message:
> {code:java}
> java.sql.SQLSyntaxErrorException: ORA-00933: SQL command not properly ended
>   at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)
>   at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:446)
>   at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1054)
>   at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:623)
>   at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252)
>   at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:612)
>   at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:213)
>   at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:37)
>   at 
> oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:733)
>   at 
> oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:904)
>   at 
> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1082)
>   at 
> oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1276)
>   at 
> oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:366)
>   at 
> com.mchange.v2.c3p0.impl.NewProxyStatement.executeQuery(NewProxyStatement.java:220)
>   at 
> com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:286)
>   at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:510)
>   at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.finerLoggingTestPooledConnection(C3P0PooledConnectionPool.java:452)
>   at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.finerLoggingTestPooledConnection(C3P0PooledConnectionPool.java:444)
>   at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.refurbishIdleResource(C3P0PooledConnectionPool.java:434)
>   at 
> com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask.run(BasicResourcePool.java:2211)
>   at 
> com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)
> Caused by: Error : 933, Position : 18, Sql = select 1 from dual;, OriginalSql 
> = select 1 from dual;, Error Msg = ORA-00933: SQL command not properly ended
>   at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:498)
>   ... 20 more
> 2022-04-11 12:38:45,538 
> [C3P0PooledConnectionPoolManager[identityToken->1br54owao6u0q6i172od24|1f0ea3d4]-HelperThread-#2]
>  DEBUG com.mchange.v2.log.slf4j.Slf4jMLog$Slf4jMLogger$DebugLogger 
> (Slf4jMLog.java:207) - com.mchange.v2.c3p0.impl.NewPooledConnection@5f00a319 
> handling a throwable. {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3704) remove semicolon from c3P0 preferredTestQuery

[Pradeep Agrawal (Jira)]

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

Pradeep Agrawal updated RANGER-3704:

Attachment: 0001-RANGER-3704-remove-semicolon-from-c3P0-preferredTest.patch

> remove semicolon from c3P0 preferredTestQuery
> -
>
> Key: RANGER-3704
> URL: https://issues.apache.org/jira/browse/RANGER-3704
> Project: Ranger
>  Issue Type: Wish
>  Components: Ranger
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: 
> 0001-RANGER-3704-remove-semicolon-from-c3P0-preferredTest.patch
>
>
> Error message:
> {code:java}
> java.sql.SQLSyntaxErrorException: ORA-00933: SQL command not properly ended
>   at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)
>   at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:446)
>   at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1054)
>   at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:623)
>   at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252)
>   at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:612)
>   at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:213)
>   at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:37)
>   at 
> oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:733)
>   at 
> oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:904)
>   at 
> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1082)
>   at 
> oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1276)
>   at 
> oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:366)
>   at 
> com.mchange.v2.c3p0.impl.NewProxyStatement.executeQuery(NewProxyStatement.java:220)
>   at 
> com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:286)
>   at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:510)
>   at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.finerLoggingTestPooledConnection(C3P0PooledConnectionPool.java:452)
>   at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.finerLoggingTestPooledConnection(C3P0PooledConnectionPool.java:444)
>   at 
> com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.refurbishIdleResource(C3P0PooledConnectionPool.java:434)
>   at 
> com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask.run(BasicResourcePool.java:2211)
>   at 
> com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)
> Caused by: Error : 933, Position : 18, Sql = select 1 from dual;, OriginalSql 
> = select 1 from dual;, Error Msg = ORA-00933: SQL command not properly ended
>   at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:498)
>   ... 20 more
> 2022-04-11 12:38:45,538 
> [C3P0PooledConnectionPoolManager[identityToken->1br54owao6u0q6i172od24|1f0ea3d4]-HelperThread-#2]
>  DEBUG com.mchange.v2.log.slf4j.Slf4jMLog$Slf4jMLogger$DebugLogger 
> (Slf4jMLog.java:207) - com.mchange.v2.c3p0.impl.NewPooledConnection@5f00a319 
> handling a throwable. {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Review Request 73940: RANGER-3704: remove semicolon from c3P0 preferredTestQuery

[Pradeep Agrawal]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73940/
---

Review request for ranger, bhavik patel, Abhay Kulkarni, Madhan Neethiraj, 
Ramesh Mani, Sailaja Polavarapu, and Velmurugan Periasamy.


Repository: ranger


Description
---

**Problem Statement:** While checking c3p0 debug logs for oracle db flavor 
found that 'preferredTestQuery' config of c3p0 does not understand sql 
termination character ; and throws logs. I also suspect that it affectes 
application performance and connection pool management.

**Proposed statement:** removal of ; from the test connection sql stops the 
exception logs.


Diffs
-

  security-admin/scripts/setup.sh 7dc11d8f8 
  security-admin/src/main/resources/conf.dist/logback.xml 997f3bc59 
  security-admin/src/main/resources/conf.dist/ranger-admin-default-site.xml 
e2bfc8fff 


Diff: https://reviews.apache.org/r/73940/diff/1/


Testing
---

Tested the patch and verfied the c3p0 debug logs with mysql,postgres and oracle 
db flavor.


Thanks,

Pradeep Agrawal

Re: Review Request 73882: RANGER-3600: Ranger service tags import request failure

[Pradeep Agrawal]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73882/
---

(Updated April 11, 2022, 1:17 p.m.)


Review request for ranger, Abhay Kulkarni, Madhan Neethiraj, Ramesh Mani, 
Sailaja Polavarapu, and Velmurugan Periasamy.


Bugs: RANGER-3600
https://issues.apache.org/jira/browse/RANGER-3600


Repository: ranger


Description (updated)
---

**Problem Statement:** Ranger service tag import request may fail if 
RangerServiceResource objects of ServiceTags objects does not have ranger 
service name attribute values. 

**Proposed Solution:** 
1) Use service name avaiable in the parent object(Servicetag object)
2) Do not prune service name field while populating the RangerServiceResource 
objects of the ServiceTag object.


Diffs
-

  
agents-common/src/main/java/org/apache/ranger/plugin/util/RangerServiceTagsDeltaUtil.java
 76d5fd989 
  security-admin/src/main/java/org/apache/ranger/rest/ServiceTagsProcessor.java 
3897f48e2 


Diff: https://reviews.apache.org/r/73882/diff/2/


Testing (updated)
---

Tested the patch and able to import ServiceTags even if ServiceTags json does 
not have service names in RangerServiceResource objects.
Tested for mysql, oracle and postgres db flavor.


Thanks,

Pradeep Agrawal

[jira] [Created] (RANGER-3704) remove semicolon from c3P0 preferredTestQuery

[Pradeep Agrawal (Jira)]

Pradeep Agrawal created RANGER-3704:
---

 Summary: remove semicolon from c3P0 preferredTestQuery
 Key: RANGER-3704
 URL: https://issues.apache.org/jira/browse/RANGER-3704
 Project: Ranger
  Issue Type: Wish
  Components: Ranger
Reporter: Pradeep Agrawal
Assignee: Pradeep Agrawal
 Fix For: 3.0.0, 2.3.0


Error message:
{code:java}
java.sql.SQLSyntaxErrorException: ORA-00933: SQL command not properly ended


at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)
at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:446)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1054)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:623)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:612)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:213)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:37)
at 
oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:733)
at 
oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:904)
at 
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1082)
at 
oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1276)
at 
oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:366)
at 
com.mchange.v2.c3p0.impl.NewProxyStatement.executeQuery(NewProxyStatement.java:220)
at 
com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:286)
at 
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:510)
at 
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.finerLoggingTestPooledConnection(C3P0PooledConnectionPool.java:452)
at 
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.finerLoggingTestPooledConnection(C3P0PooledConnectionPool.java:444)
at 
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.refurbishIdleResource(C3P0PooledConnectionPool.java:434)
at 
com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask.run(BasicResourcePool.java:2211)
at 
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)
Caused by: Error : 933, Position : 18, Sql = select 1 from dual;, OriginalSql = 
select 1 from dual;, Error Msg = ORA-00933: SQL command not properly ended


at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:498)
... 20 more
2022-04-11 12:38:45,538 
[C3P0PooledConnectionPoolManager[identityToken->1br54owao6u0q6i172od24|1f0ea3d4]-HelperThread-#2]
 DEBUG com.mchange.v2.log.slf4j.Slf4jMLog$Slf4jMLogger$DebugLogger 
(Slf4jMLog.java:207) - com.mchange.v2.c3p0.impl.NewPooledConnection@5f00a319 
handling a throwable. {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: Review Request 73922: RANGER-3687: Password Policy Best Practices for Strong Security

[bhavik patel]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73922/
---

(Updated April 11, 2022, 12:42 p.m.)


Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Kirby Zhou, Abhay 
Kulkarni, Madhan Neethiraj, Mateen Mansoori, Mehul Parikh, Pradeep Agrawal, 
Ramesh Mani, and Velmurugan Periasamy.


Bugs: RANGER-3687
https://issues.apache.org/jira/browse/RANGER-3687


Repository: ranger


Description
---

Password history should be configured to restrict users from reusing their last 
4 or 5 passwords.


Diffs (updated)
-

  security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql 26282f770 
  security-admin/db/mysql/patches/059-update-x-portal-user-table.sql 
PRE-CREATION 
  security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql 
e2475cfbd 
  security-admin/db/oracle/patches/059-update-x-portal-user-table..sql 
PRE-CREATION 
  security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 
f5c6ed8f5 
  security-admin/db/postgres/patches/059-update-x-portal-user-table.sql 
PRE-CREATION 
  
security-admin/db/sqlanywhere/optimized/current/ranger_core_db_sqlanywhere.sql 
1887d6da9 
  security-admin/db/sqlanywhere/patches/059-update-x-portal-user-table.sql 
PRE-CREATION 
  security-admin/db/sqlserver/optimized/current/ranger_core_db_sqlserver.sql 
642e54cd5 
  security-admin/db/sqlserver/patches/059-update-x-portal-user-table.sql 
PRE-CREATION 
  security-admin/src/main/java/org/apache/ranger/biz/UserMgr.java 0e61038d5 
  security-admin/src/main/java/org/apache/ranger/entity/XXPortalUser.java 
d0451b4d2 
  security-admin/src/main/resources/conf.dist/ranger-admin-default-site.xml 
e2bfc8fff 
  security-admin/src/test/java/org/apache/ranger/biz/TestUserMgr.java f43b30196 


Diff: https://reviews.apache.org/r/73922/diff/6/

Changes: https://reviews.apache.org/r/73922/diff/5-6/


Testing
---

1. Verified the basic functionality of "/passwordchange" api
2. Verified "/secure/users" & "/secure/users/{id}" API’s

3. Once the basic review/discussion is done will fix the Test-cases


Thanks,

bhavik patel

[jira] [Commented] (RANGER-3231) Ranger should use kafka Authorizer from KIP-504

[alain pellegrino (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520535#comment-17520535
 ] 

alain pellegrino commented on RANGER-3231:
--

I saw that you have merged to master branch, but if I'm not wrong this branch 
is still in SNAPSHOT and when I install it I compile it I got the version 
3.0.0-SNAPSHOT.

Do you think that I can use this version for production ?

If not, is there another solution ? Because I really need your modification to 
use ranger with kafka 3.x

> Ranger should use kafka Authorizer from KIP-504
> ---
>
> Key: RANGER-3231
> URL: https://issues.apache.org/jira/browse/RANGER-3231
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>Reporter: Ismael Juma
>Assignee: Andras Katona
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ranger_kafka.zip
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> As described in the KIP, `org.apache.kafka.server.authorizer.Authorizer` is 
> an improvement over `kafka.security.auth.Authorizer` and it's a pure Java 
> interface (instead of Scala).
> `kafka.security.auth.Authorizer` has been deprecated since December 2019 and 
> it will be removed in Apache Kafka 3.0 (roughly planned for July/August).
> See the KIP for more details:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-504+-+Add+new+Java+Authorizer+Interface



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: Review Request 72024: RANGER-2704 : Support browser login using kerberized authentication.

[Dhaval Shah]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72024/#review224293
---


Ship it!




Ship It!

- Dhaval Shah


On April 5, 2022, 12:24 p.m., Vishal Suvagia wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/72024/
> ---
> 
> (Updated April 5, 2022, 12:24 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Dhaval Shah, Dineshkumar Yadav, 
> Gautam Borad, Jayendra Parab, Kishor Gollapalliwar, Abhay Kulkarni, Madhan 
> Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, 
> and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2704
> https://issues.apache.org/jira/browse/RANGER-2704
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Need to support browser login using kerberos authentication. Added a logout 
> for an unauthenticated user to redirect to the login page.
> 
> 
> Diffs
> -
> 
>   
> security-admin/src/main/java/org/apache/ranger/security/web/filter/RangerKrbFilter.java
>  223a991c76bae7d25f5ce89604d0a8a90d426fe5 
>   
> security-admin/src/main/java/org/apache/ranger/security/web/filter/RangerSSOAuthenticationFilter.java
>  abbf2d983beb30b59e5d3f6429d6fc226f735793 
>   security-admin/src/main/resources/conf.dist/ranger-admin-default-site.xml 
> 0a1128613dca50fe67ea3f891261f1ee449c46db 
> 
> 
> Diff: https://reviews.apache.org/r/72024/diff/2/
> 
> 
> Testing
> ---
> 
> Veriried kerberos ticket authentication is working on a kerberized browser.
> 
> 
> Steps to test for a kerberized browser:
> #1) For Kerberized browsers:
> #1> To open Chrome in kerberos enabled mode need to run below command:
>google-chrome --auth-server-whitelist="*ranger.testserver.com"
> #2> For Firefox, need to go to about:configs and then search for 
> negotiate and then add the host domain
> ranger.testserver.com to the property 
> "network.negotiate-auth.trusted-uris"
> #2) Perform kinit with the required user.
> #3) Open the Ranger Admin portal using FQDN of the server host.
> 
> 
> Known Issue: If there is no valid kerberos ticket, user lands on a blank page 
> and a short hack is to either append locallogin to the URL or refresh the 
> browser tab to redirect to the login page.
> P.S: this issue is not observed on Google Chrome browser
> 
> 
> File Attachments
> 
> 
> RANGER-2704.patch
>   
> https://reviews.apache.org/media/uploaded/files/2020/01/17/8c9682ca-1ade-4281-89e7-d43a8af09300__RANGER-2704.patch
> RANGER-2704.02.patch
>   
> https://reviews.apache.org/media/uploaded/files/2022/04/04/6e737bec-e640-4459-922c-353793172b12__RANGER-2704.02.patch
> RANGER-2704.03.patch
>   
> https://reviews.apache.org/media/uploaded/files/2022/04/05/31e52557-051e-40ba-bc34-5dc6418e06f8__RANGER-2704.03.patch
> 
> 
> Thanks,
> 
> Vishal Suvagia
> 
>

Re: Review Request 73935: RANGER-3669 : Connection to DB fails for MySQL version above 8.0

[Mehul Parikh]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73935/#review224292
---


Ship it!




Ship It!

- Mehul Parikh


On April 8, 2022, 10:57 a.m., Vishal Suvagia wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73935/
> ---
> 
> (Updated April 8, 2022, 10:57 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Dhaval Shah, Dineshkumar Yadav, 
> Gautam Borad, Jayendra Parab, Kishor Gollapalliwar, Abhay Kulkarni, Madhan 
> Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, 
> and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-3669
> https://issues.apache.org/jira/browse/RANGER-3669
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Ranger KMS db setup script needs to be updated to support MySql versions 
> greater than 8.0
> Made changes to allow non-ssl connection with DB for Mysql version greater 
> than 8.0
> made a fix to allow user to define the custom jdbc url which can be used in 
> db-setup.
> Added missing change for Ranger Admin db-setup in RANGER-3647
> 
> 
> Diffs
> -
> 
>   kms/scripts/db_setup.py 165e30d89443b7e8244ed965c34a5d7219e7d1f3 
>   kms/scripts/install.properties 780509dcdd06c13e84f1a860213eb28f3556fa26 
>   security-admin/scripts/db_setup.py eaae5c8990724d7ead703d747140a0c3c49289d7 
> 
> 
> Diff: https://reviews.apache.org/r/73935/diff/1/
> 
> 
> Testing
> ---
> 
> Validated changes locally with available Mysql-8.0 release.
> 
> 
> File Attachments
> 
> 
> RANGER-3669.01.patch
>   
> https://reviews.apache.org/media/uploaded/files/2022/04/08/48106a24-5c65-47d3-b971-7b69f5d7bb79__RANGER-3669.01.patch
> 
> 
> Thanks,
> 
> Vishal Suvagia
> 
>

[jira] [Commented] (RANGER-3188) HiveServer log showed Authentication Failed

[KaiXinXIaoLei (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520482#comment-17520482
 ] 

KaiXinXIaoLei commented on RANGER-3188:
---

The same question. Can you tell me how to solve this problem? Thanks.

> HiveServer log showed Authentication Failed
> ---
>
> Key: RANGER-3188
> URL: https://issues.apache.org/jira/browse/RANGER-3188
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 2.1.0
> Environment: Hive Version: 3.1.2
> Ranger: 2.1
> os: centos
>Reporter: Sekiro
>Priority: Major
>
> When I create a table on AWS EMR 6.2 which shows the following error message.
> But eventually create success.
> Although does not affect the use but I really want to know why.:)
>  
> 2021-02-24T06:14:41,059 ERROR [925310d9-d40a-437a-af54-eeec38b2c8d5 
> HiveServer2-Handler-Pool: Thread-103([])]: client.RangerAdminRESTClient 
> (RangerAdminRESTClient.java:getUserRoles(434)) - getUserRoles() failed: HTTP 
> status=401, message=Authentication Failed, isSecure=false
> 2021-02-24T06:14:41,078 ERROR [925310d9-d40a-437a-af54-eeec38b2c8d5 
> HiveServer2-Handler-Pool: Thread-103([])]: authorizer.RangerHiveAuthorizer 
> (RangerHiveAuthorizer.java:initUserRoles(322)) - Error while fetching roles 
> from ranger for user : hadoop
> org.apache.hadoop.hive.ql.security.authorization.plugin.HiveAuthzPluginException:
>  org.apache.hadoop.security.AccessControlException: Permission denied.
>  at 
> org.apache.ranger.authorization.hive.authorizer.RangerHiveAuthorizer.getCurrentRoleNamesFromRanger(RangerHiveAuthorizer.java:365)
>  ~[ranger-hive-plugin-2.1.0.jar:2.1.0]
>  at 
> org.apache.ranger.authorization.hive.authorizer.RangerHiveAuthorizer.initUserRoles(RangerHiveAuthorizer.java:320)
>  [ranger-hive-plugin-2.1.0.jar:2.1.0]
>  at 
> org.apache.ranger.authorization.hive.authorizer.RangerHiveAuthorizer.getCurrentRoles(RangerHiveAuthorizer.java:329)
>  [ranger-hive-plugin-2.1.0.jar:2.1.0]
>  at 
> org.apache.ranger.authorization.hive.authorizer.RangerHiveAuthorizer.checkPrivileges(RangerHiveAuthorizer.java:785)
>  [ranger-hive-plugin-2.1.0.jar:2.1.0]
>  at org.apache.hadoop.hive.ql.Driver.doAuthorizationV2(Driver.java:1307) 
> [hive-exec-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at org.apache.hadoop.hive.ql.Driver.doAuthorization(Driver.java:1071) 
> [hive-exec-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:698) 
> [hive-exec-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1826) 
> [hive-exec-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1773) 
> [hive-exec-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1768) 
> [hive-exec-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at 
> org.apache.hadoop.hive.ql.reexec.ReExecDriver.compileAndRespond(ReExecDriver.java:126)
>  [hive-exec-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at 
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:197)
>  [hive-service-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at 
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:260)
>  [hive-service-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at org.apache.hive.service.cli.operation.Operation.run(Operation.java:247) 
> [hive-service-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.java:541)
>  [hive-service-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at 
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatement(HiveSessionImpl.java:516)
>  [hive-service-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_272]
>  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[?:1.8.0_272]
>  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:1.8.0_272]
>  at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_272]
>  at 
> org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:78)
>  [hive-service-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at 
> org.apache.hive.service.cli.session.HiveSessionProxy.access$000(HiveSessionProxy.java:36)
>  [hive-service-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at 
> org.apache.hive.service.cli.session.HiveSessionProxy$1.run(HiveSessionProxy.java:63)
>  [hive-service-3.1.2-amzn-3.jar:3.1.2-amzn-3]
>  at java.security.AccessController.doPrivileged(Native Method) [?:1.8.0_272]
>  at javax.security.auth.Subject.doAs(Subject.java:422) [?:1.8.0_272]
>  at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1730)
>  [hadoop-common-3.2.1-amzn-2.jar:?]
>  at 
> 

[jira] [Commented] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520479#comment-17520479
 ] 

Binhua Hu commented on RANGER-3703:
---

Neither of them. Our ranger is in the container environment.Based on the Ranger 
image,every container instance invokes the setup.sh script before launching the 
RangerAdmin service.

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger database volume.png, ranger log.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !ranger log.png!
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=957,height=360!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

[ https://issues.apache.org/jira/browse/RANGER-3703 ]


Binhua Hu deleted comment on RANGER-3703:
---

was (Author: JIRAUSER286986):
Neither of them. Our ranger is in the container environment。Based on the Ranger 
image, every container instance invokes the setup.sh script before launching 
the RangerAdmin service.

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger database volume.png, ranger log.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !ranger log.png!
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=957,height=360!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520478#comment-17520478
 ] 

Binhua Hu commented on RANGER-3703:
---

Neither of them. Our ranger is in the container environment。Based on the Ranger 
image, every container instance invokes the setup.sh script before launching 
the RangerAdmin service.

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger database volume.png, ranger log.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !ranger log.png!
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=957,height=360!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: Review Request 73922: RANGER-3687: Password Policy Best Practices for Strong Security

[Kirby Zhou]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73922/#review224291
---




security-admin/src/main/java/org/apache/ranger/biz/UserMgr.java
Lines 122 (patched)


Should be limited as non-negatvie.



security-admin/src/main/java/org/apache/ranger/biz/UserMgr.java
Lines 167 (patched)


How about Timezone?



security-admin/src/main/java/org/apache/ranger/biz/UserMgr.java
Lines 398 (patched)


here should be limited by pwdHistoryStore.



security-admin/src/main/java/org/apache/ranger/biz/UserMgr.java
Lines 435 (patched)


If we change pwdHistoryStore from 10 to 5, it only remove 1 from a 9-size 
old one.


- Kirby Zhou


On 四月 9, 2022, 5:29 a.m., bhavik patel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73922/
> ---
> 
> (Updated 四月 9, 2022, 5:29 a.m.)
> 
> 
> Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Kirby Zhou, Abhay 
> Kulkarni, Madhan Neethiraj, Mateen Mansoori, Mehul Parikh, Pradeep Agrawal, 
> Ramesh Mani, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-3687
> https://issues.apache.org/jira/browse/RANGER-3687
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Password history should be configured to restrict users from reusing their 
> last 4 or 5 passwords.
> 
> 
> Diffs
> -
> 
>   security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql 
> 26282f770 
>   security-admin/db/mysql/patches/059-update-x-portal-user-table.sql 
> PRE-CREATION 
>   security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql 
> e2475cfbd 
>   security-admin/db/oracle/patches/059-update-x-portal-user-table..sql 
> PRE-CREATION 
>   security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 
> f5c6ed8f5 
>   security-admin/db/postgres/patches/059-update-x-portal-user-table.sql 
> PRE-CREATION 
>   
> security-admin/db/sqlanywhere/optimized/current/ranger_core_db_sqlanywhere.sql
>  1887d6da9 
>   security-admin/db/sqlanywhere/patches/059-update-x-portal-user-table.sql 
> PRE-CREATION 
>   security-admin/db/sqlserver/optimized/current/ranger_core_db_sqlserver.sql 
> 642e54cd5 
>   security-admin/db/sqlserver/patches/059-update-x-portal-user-table.sql 
> PRE-CREATION 
>   security-admin/src/main/java/org/apache/ranger/biz/UserMgr.java 0e61038d5 
>   security-admin/src/main/java/org/apache/ranger/entity/XXPortalUser.java 
> d0451b4d2 
>   security-admin/src/main/resources/conf.dist/ranger-admin-default-site.xml 
> e2bfc8fff 
>   security-admin/src/test/java/org/apache/ranger/biz/TestUserMgr.java 
> f43b30196 
> 
> 
> Diff: https://reviews.apache.org/r/73922/diff/5/
> 
> 
> Testing
> ---
> 
> 1. Verified the basic functionality of "/passwordchange" api
> 2. Verified "/secure/users" & "/secure/users/{id}" API’s
> 
> 3. Once the basic review/discussion is done will fix the Test-cases
> 
> 
> Thanks,
> 
> bhavik patel
> 
>

Re: Review Request 73937: RANGER-3697: Python3 migration of all ranger python scripts

[Kirby Zhou]

> On 四月 8, 2022, 2:12 p.m., Pradeep Agrawal wrote:
> > Currently python2 and python3 both are supported, why we want to remove 
> > python2 support ? Also What issues are you getting when you execute all 
> > these script in python3 ?
> 
> Abhishek  Kumar wrote:
> Article explaining the need to remove python2: 
> https://www.python.org/doc/sunset-python-2/#:~:text=We%20have%20decided%20that%20January,as%20soon%20as%20you%20can.
> Testing is pending.
> 
> Pradeep Agrawal wrote:
> is current script not running in python 3 ? if not please , then please 
> let me know only those lines and I shall fix that. Refer : 
> https://issues.apache.org/jira/browse/RANGER-2759 , we need to support both, 
> however default can be set to python3.

At least files in ./migration-util/ remains old-style code.

./migration-util/ambari2.1-hdp2.3-ranger0.50/bin/import_ranger_to_ambari.py

```
845 except Exception, e:
846 print "Error loading ranger-admin properties from xml files : 
", str(e)

```

Just remove it or ignore?


- Kirby


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/73937/#review224282
---


On 四月 7, 2022, 7:11 p.m., Abhishek  Kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73937/
> ---
> 
> (Updated 四月 7, 2022, 7:11 p.m.)
> 
> 
> Review request for ranger, Abhay Kulkarni, Madhan Neethiraj, Ramesh Mani, 
> Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-3697
> https://issues.apache.org/jira/browse/RANGER-3697
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Python 2 has sunset as of Jan 1, 2020. All scripts using python2 should 
> eventually move to python3.
> 
> Initial Review - will be updated to include all scripts.
> 
> Changes include:
> 1. Support only for Python3 and above.
> 2. Conformity with PEP 8 guidelines.
> 3. Code optimizations and performance improvements.
> 
> 
> Diffs
> -
> 
>   agents-common/scripts/upgrade-plugin.py d865ee366 
>   agents-common/scripts/upgrade_plugin.py PRE-CREATION 
>   ranger-util/src/scripts/saveVersion.py 51227542d 
>   ranger-util/src/scripts/save_version.py PRE-CREATION 
>   security-admin/scripts/change_password_util.py PRE-CREATION 
>   security-admin/scripts/change_username_util.py PRE-CREATION 
>   security-admin/scripts/changepasswordutil.py e45dab643 
>   security-admin/scripts/changeusernameutil.py 699f945f0 
>   security-admin/scripts/deleteUserGroupUtil.py 1c9f58385 
>   security-admin/scripts/delete_user_group_util.py PRE-CREATION 
>   security-admin/scripts/ranger_credential_helper.py 85f29ac43 
>   security-admin/scripts/restrict_permissions.py b19bafe9b 
>   security-admin/scripts/role_based_user_search_util.py PRE-CREATION 
>   security-admin/scripts/rolebasedusersearchutil.py 612db33df 
>   security-admin/scripts/updateUserAndGroupNamesInJson.py c40ec4406 
>   security-admin/scripts/upgrade_admin.py 85f57b8ce 
>   security-admin/src/bin/ranger_install.py 39b9d1f81 
>   security-admin/src/bin/ranger_usersync.py 4374896c7 
>   security-admin/src/bin/service_start.py ea13b85af 
> 
> 
> Diff: https://reviews.apache.org/r/73937/diff/1/
> 
> 
> Testing
> ---
> 
> Pending.
> 
> 
> Thanks,
> 
> Abhishek  Kumar
> 
>

[jira] [Commented] (RANGER-3703) Data loss during initialization

[Bhavik Patel (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520470#comment-17520470
 ] 

Bhavik Patel commented on RANGER-3703:
--

Are you installing the fresh setup(cluster) or upgrading the ranger version?

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger database volume.png, ranger log.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !ranger log.png!
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=957,height=360!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Description: 
In the docker container or distributed nodes, the initialization 
script(setup.sh) may be executed many times. Ranger controls the initialization 
process through database table（x_db_version_h）. However, when the number of 
database connections is too large or the network is abnormal, the 
initialization script will judge abnormally, the script will trigger 
reconstruction, and the data will be lost.So is it reasonable to drop tables in 
script(ranger_core_db_XX.sql).

The initialization log is as follows，

!ranger log.png!

The data volume in the Ranger database is as follows，

!ranger database volume.png|width=957,height=360!

 

  was:
In the docker container or distributed nodes, the initialization 
script(setup.sh) may be executed many times. Ranger controls the initialization 
process through database table（x_db_version_h）. However, when the number of 
database connections is too large or the network is abnormal, the 
initialization script will judge abnormally, the script will trigger 
reconstruction, and the data will be lost.So is it reasonable to drop tables in 
script(ranger_core_db_XX.sql).

The initialization log is as follows，

 

The data volume in the Ranger database is as follows，

!ranger database volume.png|width=959,height=361!

 


> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger database volume.png, ranger log.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !ranger log.png!
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=957,height=360!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: ranger database volume.png

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger database volume.png, ranger log.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
>  
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=959,height=361!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: ranger log.png

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger database volume.png, ranger log.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
>  
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=959,height=361!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: (was: ranger database volume.png)

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
>  
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=959,height=361!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: ranger log-2.png

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !ranger log.png!
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=959,height=361!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Description: 
In the docker container or distributed nodes, the initialization 
script(setup.sh) may be executed many times. Ranger controls the initialization 
process through database table（x_db_version_h）. However, when the number of 
database connections is too large or the network is abnormal, the 
initialization script will judge abnormally, the script will trigger 
reconstruction, and the data will be lost.So is it reasonable to drop tables in 
script(ranger_core_db_XX.sql).

The initialization log is as follows，

 

The data volume in the Ranger database is as follows，

!ranger database volume.png|width=959,height=361!

 

  was:
In the docker container or distributed nodes, the initialization 
script(setup.sh) may be executed many times. Ranger controls the initialization 
process through database table（x_db_version_h）. However, when the number of 
database connections is too large or the network is abnormal, the 
initialization script will judge abnormally, the script will trigger 
reconstruction, and the data will be lost.So is it reasonable to drop tables in 
script(ranger_core_db_XX.sql).

The initialization log is as follows，

!ranger log.png!

The data volume in the Ranger database is as follows，

!ranger database volume.png|width=959,height=361!

 


> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
>  
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=959,height=361!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: (was: ranger log.png)

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
>  
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=959,height=361!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: (was: ranger log-1.png)

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !ranger log.png!
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=959,height=361!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: (was: 异常1.png)

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !ranger log.png!
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=959,height=361!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: (was: ranger log-2.png)

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !ranger log.png!
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=959,height=361!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: (was: ranger丢数据异常2.png)

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !ranger log.png!
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=959,height=361!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: ranger database volume.png

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger database volume.png, ranger log-1.png, ranger 
> log.png, ranger丢数据异常2.png, 异常1.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !异常1.png|width=1157,height=218!
> The data volume in the Ranger database is as follows，
> !ranger丢数据异常2.png|width=973,height=366!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Description: 
In the docker container or distributed nodes, the initialization 
script(setup.sh) may be executed many times. Ranger controls the initialization 
process through database table（x_db_version_h）. However, when the number of 
database connections is too large or the network is abnormal, the 
initialization script will judge abnormally, the script will trigger 
reconstruction, and the data will be lost.So is it reasonable to drop tables in 
script(ranger_core_db_XX.sql).

The initialization log is as follows，

!ranger log.png!

The data volume in the Ranger database is as follows，

!ranger database volume.png|width=959,height=361!

 

  was:
In the docker container or distributed nodes, the initialization 
script(setup.sh) may be executed many times. Ranger controls the initialization 
process through database table（x_db_version_h）. However, when the number of 
database connections is too large or the network is abnormal, the 
initialization script will judge abnormally, the script will trigger 
reconstruction, and the data will be lost.So is it reasonable to drop tables in 
script(ranger_core_db_XX.sql).

The initialization log is as follows，

!异常1.png|width=1157,height=218!

The data volume in the Ranger database is as follows，

!ranger丢数据异常2.png|width=973,height=366!

 


> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger database volume.png, ranger log-1.png, ranger 
> log.png, ranger丢数据异常2.png, 异常1.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !ranger log.png!
> The data volume in the Ranger database is as follows，
> !ranger database volume.png|width=959,height=361!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: ranger log-1.png

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger log-1.png, ranger log.png, ranger丢数据异常2.png, 
> 异常1.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !异常1.png|width=1157,height=218!
> The data volume in the Ranger database is as follows，
> !ranger丢数据异常2.png|width=973,height=366!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: ranger log.png

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger log.png, ranger丢数据异常2.png, 异常1.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !异常1.png|width=1157,height=218!
> The data volume in the Ranger database is as follows，
> !ranger丢数据异常2.png|width=973,height=366!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Description: 
In the docker container or distributed nodes, the initialization 
script(setup.sh) may be executed many times. Ranger controls the initialization 
process through database table（x_db_version_h）. However, when the number of 
database connections is too large or the network is abnormal, the 
initialization script will judge abnormally, the script will trigger 
reconstruction, and the data will be lost.So is it reasonable to drop tables in 
script(ranger_core_db_XX.sql).

The initialization log is as follows，

!异常1.png|width=1157,height=218!

The data volume in the Ranger database is as follows，

!ranger丢数据异常2.png|width=973,height=366!

 

  was:
In the docker container or distributed nodes, the initialization 
script(setup.sh) may be executed many times. Ranger controls the initialization 
process through database table（x_db_version_h）. However, when the number of 
database connections is too large or the network is abnormal, the 
initialization script will judge abnormally, the script will trigger 
reconstruction, and the data will be lost.So is it reasonable to drop tables in 
script(ranger_core_db_XX.sql).

The initialization log is as follows，

!异常1.png|width=1277,height=241!


> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger丢数据异常2.png, 异常1.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !异常1.png|width=1157,height=218!
> The data volume in the Ranger database is as follows，
> !ranger丢数据异常2.png|width=973,height=366!
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: ranger丢数据异常2.png

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: ranger丢数据异常2.png, 异常1.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !异常1.png|width=1277,height=241!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Description: 
In the docker container or distributed nodes, the initialization 
script(setup.sh) may be executed many times. Ranger controls the initialization 
process through database table（x_db_version_h）. However, when the number of 
database connections is too large or the network is abnormal, the 
initialization script will judge abnormally, the script will trigger 
reconstruction, and the data will be lost.So is it reasonable to drop tables in 
script(ranger_core_db_XX.sql).

The initialization log is as follows，

!异常1.png|width=1277,height=241!

  was:In the docker container or distributed nodes, the initialization 
script(setup.sh) may be executed many times. Ranger controls the initialization 
process through database table（x_db_version_h）. However, when the number of 
database connections is too large or the network is abnormal, the 
initialization script will judge abnormally, the script will trigger 
reconstruction, and the data will be lost.So is it reasonable to drop tables in 
script(ranger_core_db_XX.sql)


> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: 异常1.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql).
> The initialization log is as follows，
> !异常1.png|width=1277,height=241!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: 异常1.png

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: 异常1.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: (was: 异常1.png)

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: 异常1.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3703) Data loss during initialization

[Binhua Hu (Jira)]

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

Binhua Hu updated RANGER-3703:
--
Attachment: 异常1.png

> Data loss  during initialization
> 
>
> Key: RANGER-3703
> URL: https://issues.apache.org/jira/browse/RANGER-3703
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 1.2.0, 2.2.0
>Reporter: Binhua Hu
>Priority: Major
> Attachments: 异常1.png
>
>
> In the docker container or distributed nodes, the initialization 
> script(setup.sh) may be executed many times. Ranger controls the 
> initialization process through database table（x_db_version_h）. However, when 
> the number of database connections is too large or the network is abnormal, 
> the initialization script will judge abnormally, the script will trigger 
> reconstruction, and the data will be lost.So is it reasonable to drop tables 
> in script(ranger_core_db_XX.sql)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)