You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2021/03/28 14:39:07 UTC

[GitHub] [incubator-dolphinscheduler] CalvinKirs opened a new issue #5164: [Feature][Common] Configuration coverage

CalvinKirs opened a new issue #5164:
URL: https://github.com/apache/incubator-dolphinscheduler/issues/5164


   Configuration coverage
   
   At present, our parameter configuration is mainly based on configuration files: you can refer to PropertiesUtils,
   
   But usually important parameters will be injected through the form of Java runtime virtual machine parameters, so we need to support this way of parameter injection. At the same time, because different ways of parameter injection have different priorities, we need to achieve configuration coverage. There are two main situations at present, SystemProperties and LocalFile. The priority of SystemProperties should be the highest, followed by LocalFile (that is, our various configuration files, such as master.properties).
   
   for example:
   1: Configure master.max.cpuload.avg=-1 in master.prperties
   
   2: Java runtime virtual machine parameters -Dmaster.max.cpuload.avg=1
   
   3:PropertiesUtils.get("master.max.cpuload.avg") = 1


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org