You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mikhail Pochatkin (Jira)" <ji...@apache.org> on 2023/08/21 08:03:00 UTC

[jira] [Commented] (IGNITE-19631) No way to pass JVM options when using bin/ignite3db

    [ https://issues.apache.org/jira/browse/IGNITE-19631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756723#comment-17756723 ] 

Mikhail Pochatkin commented on IGNITE-19631:
--------------------------------------------

[~Artukhov] May you please review?

> No way to pass JVM options when using bin/ignite3db
> ---------------------------------------------------
>
>                 Key: IGNITE-19631
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19631
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Ivan Artiukhov
>            Assignee: Mikhail Pochatkin
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is no way to set custom JVM options when starting an Ignite node via `bin/ignite3db` script. 
> The {{${IGNITE_HOME}/etc/vars.env}} file contains the {{IGNITE3_EXTRA_JVM_ARGS}} parameter, but currently its value is placed after the {{IgniteRunner}} in the command-line which is wrong. See [bootstrap-functions.sh|https://github.com/apache/ignite-3/blob/ae3c4660ab9ae0be9a4f4bef84b002e9e392c243/packaging/common/bootstrap-functions.sh#L51]. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)