[
https://issues.apache.org/jira/browse/RATIS-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598399#comment-17598399
]
Neil Joshi commented on RATIS-1694:
-----------------------------------
[~szetszwo] , with this patch to revert the default from RECOVER to FORMAT,
does this affect the behavior we placed for the issue HDDS-7103 for potential
same ratis group over multiple volumes? We discussed RATIS to on fail to write
to a ratis group to throw an exception and not try another volume. Is this
still unchanged?
> Fix the compatibility issue of RATIS-1677
> -----------------------------------------
>
> Key: RATIS-1694
> URL: https://issues.apache.org/jira/browse/RATIS-1694
> Project: Ratis
> Issue Type: Bug
> Components: client, server
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The following was reported by [~micahzhao] in
> https://github.com/apache/ratis/pull/718#issuecomment-1231085803
>
> There are two possible problems here:
> # The interface compatibility issues, ozone is directly use
> GroupManagementRequest.newAdd, this method changes in the PR maybe not
> compatible.
> # Regardless of whether I set the format in newAdd to true or false, I will
> see many “Storage directory not found” exceptions in the UT of Ozone. These
> exceptions may be caused by this PR. ...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
