Open lgy1027 opened 10 months ago
@lgy1027 Could you please provide the yaml for the dataset and runtime ?
@lgy1027 Could you please provide the yaml for the dataset and runtime ?
dataset.yaml apiVersion: data.fluid.io/v1alpha1 kind: Dataset metadata: name: all namespace: test spec: sharedOptions: alluxio.underfs.s3.disable.dns.buckets: "true" alluxio.underfs.s3.endpoint: xxxxxxxxxx alluxio.underfs.s3.inherit.acl: "false" s3a.accessKeyId: xxxxxxxxx s3a.secretKey: xxxxxxxxxxxxxxx mounts:
apiVersion: data.fluid.io/v1alpha1 kind: AlluxioRuntime metadata: name: all namespace: test spec: replicas: 1 tieredstore: levels:
subdateset.yaml apiVersion: data.fluid.io/v1alpha1 kind: Dataset metadata: name: test01 spec: mounts:
apiVersion: data.fluid.io/v1alpha1 kind: Dataset metadata: name: test02 spec: mounts:
nginx.yaml apiVersion: v1 kind: Pod metadata: labels: sidecar.istio.io/inject: "false" name: nginx spec: containers:
@cheyang This bug is caused because sub-dataset' pv use the same volumeHandle
name as referenced dataset's pv, therefore k8s think the pod have two same pv resulting in mount timeout. Do we have a plan to fix this or just state in the document that a pod can not use multiple sub datasets pointing to the same dataset?
k8s: 1.25.4 fluid: 0.9.1
When I try to mount two subsets in one pod, it shows timeout
dataset:
subdataset:
pod event: