[jira] [Updated] (HDDS-2647) Ozone DataNode does not set raft.server.log.corruption.policy to the RaftServer implementation it uses

["Ethan Rose (Jira)" <ji...@apache.org>]

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

Ethan Rose updated HDDS-2647:
-----------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> 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: Apache Ozone
>          Issue Type: Improvement
>          Components: Ozone Datanode
>            Reporter: István 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: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org