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

Rumesh commented on COMDEV-412:
-------------------------------

[~kirs] Can you please review my proposal - 
https://docs.google.com/document/d/1R9-fjoP168mIevHCl5oZsvmtnQXsA9UH4fgXmumH_RM/edit?usp=sharing

> Apache DolphinScheduler-Parameter coverage
> ------------------------------------------
>
>                 Key: COMDEV-412
>                 URL: https://issues.apache.org/jira/browse/COMDEV-412
>             Project: Community Development
>          Issue Type: Improvement
>          Components: GSoC/Mentoring ideas
>            Reporter: Calvin Kirs
>            Priority: Major
>              Labels: DolphinScheduler, gsoc2021, mentor
>
> *Apache DolphinScheduler*
> Apache DolphinScheduler is a distributed and extensible workflow scheduler 
> platform with powerful DAG visual interfaces, dedicated to solving complex 
> job dependencies in the data pipeline and providing various types of jobs 
> available out of the box.
> Page:https://dolphinscheduler.apache.org
> GitHub: https://github.com/apache/incubator-dolphinscheduler
> *Background:*
> Configuration parameter override
> 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).
> issue:
> https://github.com/apache/incubator-dolphinscheduler/issues/5164
> 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
> *Task*: realize configuration parameter coverage
> *Mentor*: CalvinKirs k...@apache.org



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Reply via email to