nicknezis commented on pull request #3725:
URL: https://github.com/apache/incubator-heron/pull/3725#issuecomment-967791007
Apologies for the delay in testing. Now that the other Python issue is
resolved, I'm again able to submit and kill topologies. It seems that the
scheduler is always attempting to create new PVCs.
I created the following PVC:
```
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: nez-big-storage
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 5Gi
storageClassName: standard
volumeMode: Filesystem
```
And then submitted the following:
```
heron submit heronkube \
--config-property
heron.kubernetes.volumes.persistentVolumeClaim.nez-volume-name.readOnly=true \
--config-property
heron.kubernetes.volumes.persistentVolumeClaim.nez-volume-name.path=/tmp/nez \
--config-property
heron.kubernetes.volumes.persistentVolumeClaim.nez-volume-name.subPath=was/here
\
--config-property
heron.kubernetes.volumes.persistentVolumeClaim.nez-volume-name.claimname=nez-big-storage
\
/heron/examples/heron-api-examples.jar
org.apache.heron.examples.api.AckingTopology acking
```
The pre-provisioned PVC would be mounted at the above path `/tmp/nez` with a
`volumeMount` named `nez-volume-name`. Not this is the volume name, as opposed
to the volume claim name.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
