You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "UENISHI Kota (Jira)" <ji...@apache.org> on 2021/05/10 08:32:00 UTC
[jira] [Commented] (HDDS-5197) OZONE_*_OPTS in ozone-env.sh are
ignored in startup script
[ https://issues.apache.org/jira/browse/HDDS-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17341774#comment-17341774 ]
UENISHI Kota commented on HDDS-5197:
------------------------------------
Identified the issue, that before ozone_subcommand_opts being processed, due to the lack of GC options in OZONE_OPTS, default GC options are added and conflicting GC options prevented JVM from started.
The right fix would be calling ozone_subcommand_opts before ozone_add_default_gc_opts (currently they are in reverse order).
> OZONE_*_OPTS in ozone-env.sh are ignored in startup script
> ----------------------------------------------------------
>
> Key: HDDS-5197
> URL: https://issues.apache.org/jira/browse/HDDS-5197
> Project: Apache Ozone
> Issue Type: Bug
> Components: dist
> Affects Versions: 1.1.0
> Reporter: UENISHI Kota
> Assignee: UENISHI Kota
> Priority: Major
> Labels: pull-request-available
>
> I thought I carefully migrated variables in hadoop-env.sh to ozone-env.sh on upgrading Ozone 1.0 to 1.1, but it ended up empty GC setting and failed to restart.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org