[
https://issues.apache.org/jira/browse/IGNITE-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545239#comment-16545239
]
Ilya Murchenko commented on IGNITE-8994:
----------------------------------------
Here are steps which I used to deploy Ignite StatefulSet with dedicated volumes
for WAL and Data:
{code:java}
##Create Ignite StatefulSet deployment with dedicated volumes for WAL and Data
1. Specify a Volume Type in storage-class-wal-<aws|gke>.yaml and
storage-class-persistence-<aws|gke>.yaml configuration templates.
2. Create a StorageClass for AWS or GKE
#AWS:
$ kubectl create -f storage-class-wal-aws.yaml
#GKE:
$ kubectl create -f storage-class-wal-gke.yaml
3. Create a PersistentVolumeClaim for AWS or GKE
#AWS:
$ kubectl create -f storage-class-persistence-aws.yaml
#GKE:
$ kubectl create -f storage-class-persistence-gke.yaml
4. Deploy Ignite StatefulSet with dedicated volumes for WAL and Data
$ kubectl create -f ignite-statefulset.yaml
{code}
Configuration templates (YAML) are attached.
> Configuring dedicated volumes for WAL and data with Kuberenetes
> ---------------------------------------------------------------
>
> Key: IGNITE-8994
> URL: https://issues.apache.org/jira/browse/IGNITE-8994
> Project: Ignite
> Issue Type: Task
> Components: documentation
> Reporter: Denis Magda
> Assignee: Ilya Murchenko
> Priority: Major
> Fix For: 2.7
>
> Attachments: yaml.zip
>
>
> The current StatefulSet documentation request only one persistent volume for
> both WAL and data/index files:
> https://apacheignite.readme.io/docs/stateful-deployment#section-statefulset-deployment
> However, according to Ignite performance guide the WAL has to be located on a
> dedicated volume:
> https://apacheignite.readme.io/docs/durable-memory-tuning#section-separate-disk-device-for-wal
> Provide StatefulSet configuration that shows how to request separate volumes
> for the WAL and data/index files. If needed, provide YAML configs for
> StorageClass and volume claims.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
