[ 
https://issues.apache.org/jira/browse/HDDS-17515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HDDS-17515:
----------------------------------
    Labels: pull-request-available  (was: )

> Move KeyLifecycleService configuration from OMConfigKeys to a dedicated 
> KeyLifecycleServiceConfig
> -------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-17515
>                 URL: https://issues.apache.org/jira/browse/HDDS-17515
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: OM
>            Reporter: Priyesh Karatha
>            Assignee: Priyesh Karatha
>            Priority: Major
>              Labels: pull-request-available
>
> h3. Background
> HDDS-16640 made the KeyLifecycleService properties reconfigurable at runtime. 
> Doing that needed several pieces of hand-written plumbing:
>  - {{{}KeyLifecycleService.OZONE_KEY_LIFECYCLE_PROPERTIES{}}}, a 
> hand-maintained set of property keys used to register reconfiguration 
> handlers in {{{}OzoneManager{}}}.
>  - {{{}KeyLifecycleService.ReconfigurableSettings{}}}, which reads every 
> property from {{ConfigurationSource}} and checks it.
>  - Per-property handlers ({{{}validateKeyLifecycleProperty{}}}) that only 
> validate, plus a complete callback that re-reads the full configuration.
> The keys and defaults are also defined separately: as constants in 
> {{{}OMConfigKeys{}}}, with descriptions in {{{}ozone-default.xml{}}}. Adding 
> or changing a lifecycle property means updating all of these places.
> h3. Proposal
> Move all {{ozone.lifecycle.service.*}} properties into a new {{@ConfigGroup}} 
> class, {{{}KeyLifecycleServiceConfig{}}}, that extends 
> {{{}ReconfigurableConfig{}}}, following the existing {{OmConfig}} pattern.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to