[
https://issues.apache.org/jira/browse/HDDS-11597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891252#comment-17891252
]
Denis Krivenko commented on HDDS-11597:
---------------------------------------
[~pyttel], thank you for testing and reporting the issue!
Unfortunately current persistence approach is incorrect. You are right,
{{accessModes}} config and multiple {{{}PVC{}}}s support need be added.
I think the issue can be solved in the following way:
* drop {{PersistentVolumeClaim}} templates and use {{volumeClaimTemplates}} in
{{StatefulSet}} templates
* drop {{.Values.<component>.persistence.existingClaim }}configs
* add {{{}.Values.{}}}{{{}<component>.persistence.accessModes{}}} configs
Please, let me know if you have time and willing create a PR.
> Invalid accessModes for ozone helm chart in persistent mode
> -----------------------------------------------------------
>
> Key: HDDS-11597
> URL: https://issues.apache.org/jira/browse/HDDS-11597
> Project: Apache Ozone
> Issue Type: Bug
> Components: Helm, kubernetes, OM HA, SCM HA
> Affects Versions: helm-0.1.0
> Environment: I used Rancher kubernetes cluster to deploy the helm
> chart.
> Reporter: Pyttel
> Assignee: Denis Krivenko
> Priority: Major
>
> I tried to install the chart with persistence switched on. I get the
> following error:
>
> {code:java}
> PersistentVolumeClaim "YXZ-datanode" is invalid: spec.accessModes: Required
> value: at least 1 access mode is required{code}
>
> It would be fixed if accessModes could be set by values.yaml? (Tested it
> locally) If this is really the fix I can create a pull request :)
> Another problem I see is that one PVC for 3 instances of OM,SCM,DATANODE and
> S3G is created. Maybe I'm wrong, but I assume that each replica gets its own
> PVC.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
