You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2025/06/24 11:59:00 UTC
[jira] [Updated] (IGNITE-25752) Add environment variable configuration mechanism
[ https://issues.apache.org/jira/browse/IGNITE-25752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-25752:
------------------------------------
Description:
As a user, I'd like to set Ignite *node configuration* with *environment variables*. This is very useful in containerized environments (Docker, k8s), cloud-native deployments, and also for demos and POCs.
Example:
{code}
docker run -p 10300:10300 -p 10800:10800 -e IGNITE_CLIENTCONNECTOR_IDLETIMEOUTMILLIS=9000 -e IGNITE_SQL_EXECUTION_THREADCOUNT=8 apacheignite/ignite:3.1.0
{code}
was:As a user, I'd like to set Ignite *node configuration* with *environment variables*. This is very useful in containerized environments (Docker, k8s), cloud-native deployments, and also for demos and POCs.
> Add environment variable configuration mechanism
> ------------------------------------------------
>
> Key: IGNITE-25752
> URL: https://issues.apache.org/jira/browse/IGNITE-25752
> Project: Ignite
> Issue Type: Improvement
> Components: configuration ai3
> Reporter: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
> Fix For: 3.1
>
>
> As a user, I'd like to set Ignite *node configuration* with *environment variables*. This is very useful in containerized environments (Docker, k8s), cloud-native deployments, and also for demos and POCs.
> Example:
> {code}
> docker run -p 10300:10300 -p 10800:10800 -e IGNITE_CLIENTCONNECTOR_IDLETIMEOUTMILLIS=9000 -e IGNITE_SQL_EXECUTION_THREADCOUNT=8 apacheignite/ignite:3.1.0
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)