Pavel Piankov created RANGER-4941:
-------------------------------------
Summary: Unable to compile Ranger 2.5.0 with Ozone 1.4.1 due to
missing artifacts; Ozone enters restart loop with Ozone 1.4.0 dependency.
Key: RANGER-4941
URL: https://issues.apache.org/jira/browse/RANGER-4941
Project: Ranger
Issue Type: Bug
Components: Ranger
Affects Versions: 2.5.0
Environment: cat /etc/os-release
NAME="Rocky Linux"
VERSION="8.7 (Green Obsidian)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="8.7"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Rocky Linux 8.7 (Green Obsidian)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:8:GA"
HOME_URL="https://rockylinux.org/";
BUG_REPORT_URL="https://bugs.rockylinux.org/";
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-8"
ROCKY_SUPPORT_PRODUCT_VERSION="8.7"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.7"
Reporter: Pavel Piankov
I am experiencing issues when trying to integrate Apache Ranger 2.5.0 with
Apache Ozone 1.4.1.
Steps to Reproduce:
1.Attempted to Compile Ranger with Ozone 1.4.1:
•Edited the Ranger build configuration to include Apache Ozone 1.4.1 as a
dependency.
•Ran the Maven build for ranger-ozone-plugin.
2.Encountered Maven Dependency Resolution Error:
[ERROR] Failed to execute goal on project ranger-ozone-plugin: Could not
resolve dependencies for project
org.apache.ranger:ranger-ozone-plugin:jar:2.5.0: The following artifacts could
not be resolved: org.apache.ozone:ozone-common:jar:1.4.1,
org.apache.ozone:hdds-common:jar:1.4.1,
org.apache.ozone:ozone-client:jar:1.4.1: Could not find artifact
org.apache.ozone:ozone-common:jar:1.4.1 in apache.snapshots.https
(https://repository.apache.org/content/repositories/snapshots) -> [Help 1]
3.Compiled Ranger with Ozone 1.4.0 Dependency:
•Changed the dependency to Ozone 1.4.0 in the Ranger build configuration.
•Successfully compiled the ranger-ozone-plugin.
4.Deployed Ranger and Started Ozone Manager (OM):
•Deployed the compiled Ranger plugin with Ozone 1.4.1.
•Started the Ozone Manager service.
5.Ozone Manager Enters Restart Loop:
•Observed that OM continuously restarts with the following logs:
2024-09-25 10:40:28,388 INFO org.apache.hadoop.ozone.om.OzoneManager: S3
Multi-Tenancy is enabled
2024-09-25 10:40:28,399 INFO
org.apache.hadoop.ozone.om.OMMultiTenantManagerImpl: Loaded 27 tenants and 14
tenant users from the database
2024-09-25 10:40:28,414 INFO org.apache.hadoop.ozone.om.OzoneManagerStarter:
SHUTDOWN_MSG:
/************************************************************
6.Attempted with Fresh OM Database:
•Started OM with a completely fresh database (zero tenants and zero users).
•The restart loop issue persists even without any tenants or users.
Expected Behavior:
•Apache Ranger 2.5.0 should compile successfully with Apache Ozone 1.4.1 as a
dependency.
•Ozone Manager should start normally and remain stable when integrated with
Ranger.
Actual Behavior:
•Unable to compile Ranger with Ozone 1.4.1 due to missing artifacts in Maven
repositories.
•When using Ozone 1.4.0 as a dependency, Ozone Manager enters a continuous
restart loop upon startup, even with a fresh database.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
