title: Could Elasticsearch hot reload log4j2.properties?
body: <p>I have a production elasticsearch used log4j that is vulnerable</p>
  <pre><code>./lib/log4j-api-2.11.1.jar
  ./lib/log4j-core-2.11.1.jar
  </code></pre>
  <p>because it's a production environment, I do not want to reboot it, I saw somebody said could hot reload it in the below manner</p>
  <pre><code> you can still mitigate it in those cases by replacing %m, %msg, and %message in log4j2.xml with %m{nolookups} instead
  </code></pre>
  <p>In my case it uses log4j2.properties, there is one line as below</p>
  <pre><code>appender.console.layout.pattern = [%d{ISO8601}][%-5p][%-25c{1.}] [%node_name]%marker %m%n
  </code></pre>
  <p>whether modify this line like below</p>
  <pre><code>appender.console.layout.pattern = [%d{ISO8601}][%-5p][%-25c{1.}] [%node_name]%marker %m{nolookups}%n
  </code></pre>
  <p>and it can take effect automatically without the need to reboot explicitly?</p>