[jira] [Updated] (RANGER-3703) Data loss during initialization
[ 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
[ 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] [Updated] (RANGER-3703) Data loss during initialization
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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) (was: In the 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 > > 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)
