You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Chung En Lee (Jira)" <ji...@apache.org> on 2025/10/21 20:55:03 UTC
[jira] [Updated] (HDDS-4267) Ozone command always print warn message before execution
[ https://issues.apache.org/jira/browse/HDDS-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chung En Lee updated HDDS-4267:
-------------------------------
Target Version/s: 2.2.0 (was: 1.2.0)
2.2.0 (was: 2.1.0)
<<Bulk update>>
Apache Ozone 2.1.0 release is in progress. I'm updating all unresolved jiras targeting 2.1.0 to retarget 2.2.0.
> Ozone command always print warn message before execution
> --------------------------------------------------------
>
> Key: HDDS-4267
> URL: https://issues.apache.org/jira/browse/HDDS-4267
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone CLI
> Reporter: Yiqun Lin
> Priority: Minor
>
> Ozone command always print warn message before execution:
> {noformat}
> [hdfs@lyq yiqlin]$ ~/ozone/bin/ozone version
> /home/hdfs/releases/ozone-1.0.0/etc/hadoop/hadoop-env.sh: line 34: ulimit: core file size: cannot modify limit: Operation not permitted
> {noformat}
> {noformat}
> [hdfs@ yiqlin]$ ~/ozone/bin/ozone sh volume list
> /home/hdfs/releases/ozone-1.0.0/etc/hadoop/hadoop-env.sh: line 34: ulimit: core file size: cannot modify limit: Operation not permitted
> {noformat}
> This is because that hdfs in my cluster cannot execute below command in hadoop-en.sh
> {noformat}
> # # Enable core dump when crash in C++
> ulimit -c unlimited
> {noformat}
> ulimit -c was introduced in JIRA HDDS-3941. The root cause seems that ulimit -c requires root user to execute but hdfs user in my local is a non-root user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org