<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Environment-Variables on Solo</title><link>https://solo.hiero.org/tags/environment-variables/</link><description>Recent content in Environment-Variables on Solo</description><generator>Hugo</generator><language>en</language><atom:link href="https://solo.hiero.org/tags/environment-variables/index.xml" rel="self" type="application/rss+xml"/><item><title>Consensus Node Environment Variables</title><link>https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/consensus-node-environment-variables/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://solo.hiero.org/docs/advanced-solo-setup/network-deployments/consensus-node-environment-variables/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;a class="td-heading-self-link" href="#overview" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Solo lets you define environment variables for consensus nodes with an&#10;&lt;code&gt;application.env&lt;/code&gt; file, passed through the &lt;code&gt;--application-env&lt;/code&gt; flag. The&#10;consensus node start script loads this file when it launches the JVM, so every&#10;variable defined in it is visible to the Java process.&lt;/p&gt;&#10;&lt;p&gt;Variables that are only set on the node container, for example through custom&#10;Helm chart values, are not forwarded to the Java process. If you need a variable&#10;such as &lt;code&gt;MALLOC_ARENA_MAX&lt;/code&gt; to be present in the running JVM environment, define&#10;it in &lt;code&gt;application.env&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>