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

Bharat Viswanadham commented on HDDS-2647:
------------------------------------------

This can be solved with the prefix group for all ratis properties, and setup 
all the config properties that match with the prefix.

 

A similar approach was used in Hadoop for setting HTTP headers.

Example:

hadoop.hdds.ozone.datanode.ratis.<<ratis-config>>=<<value>>

 

> Ozone DataNode does not set raft.server.log.corruption.policy to the 
> RaftServer implementation it uses
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-2647
>                 URL: https://issues.apache.org/jira/browse/HDDS-2647
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: Ozone Datanode
>            Reporter: Istvan Fajth
>            Priority: Critical
>
> In the XceiverServerRatis class which is used by the DataNode as well to 
> create the RaftServer implementation that is used, there is a method called 
> newRaftProperties() which is there to set up the RaftProperties object 
> specified for the RaftServer it starts.
> This method is pretty hard to keep in sync with all the ratis properties, and 
> due to an issue where I was turned to RATIS-677 which introduced a new 
> configuration, I was not able to set this new property via the DataNode's 
> ozone-site.xml, as it was not forwarded to the Ratis server.
> On the long run we would need a better implementation that does not need 
> tuning and follow up for every new Ratis property, however at the moment as a 
> wuick fix we can just provide the property. Depending on the implementor, if 
> we go with the easy way, then please create a new JIRA for a better solution 
> after finishing this one. Also if I am wrong, and Ratis properties can be 
> defined for the DN properly elsewhere, please let me know.
> As OM is also using Ratis in HA configuration, this one should be checked 
> there as well, however this one is not really important until RATIS-762 is 
> fixed.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org

Reply via email to