readonly db notworking
clcc2019 opened this issue · comments
```yaml
apiVersion: polardbx.aliyun.com/v1
kind: XStore
metadata:
name: polardb-readonly
spec:
config:
controller:
RPCProtocolVersion: 1
engine: {}
readonly: true
primaryXStore: polardb-master # 主实例名
topology:
nodeSets:
- name: readonly
replicas: 1
role: Learner
template:
spec:
image: image
resources:
limits:
cpu: "2"
memory: 8Gi
requests:
cpu: "2"
memory: 4Gi
affinity:
podAntiAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- podAffinityTerm:
labelSelector:
matchLabels:
xstore/node-role: candidate
topologyKey: kubernetes.io/hostname
weight: 1
nodeAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- preference:
matchExpressions:
- key: mks.components
operator: In
values:
- "enable"
weight: 1
hostNetwork: false
parameterTemplate:
name: product-8032
serviceType: ClusterIP
@clcc2019 Even though we haven't declared support for this feature in our documentation yet, I'm really excited to see you are trying to create a read-only instance for XStore.
For help, please provide the following info:
kubectl get podskubectl get xstore- polardb-readonly yaml file
@clcc2019 Even though we haven't declared support for this feature in our documentation yet, I'm really excited to see you are trying to create a read-only instance for XStore.
For help, please provide the following info:
kubectl get podskubectl get xstore- polardb-readonly yaml file
apiVersion: polardbx.aliyun.com/v1
kind: XStore
metadata:
creationTimestamp: "2024-04-29T06:50:26Z"
finalizers:
- xstore/finalizer
generation: 2
name: polardb-readonly
namespace: my-gpaas
resourceVersion: "4060697"
uid: c3e7edfb-4a36-4f17-8aa6-697c912d28ae
spec:
config:
controller:
RPCProtocolVersion: 1
engine: {}
engine: galaxy
parameterTemplate:
name: product-8032
primaryXStore: polardb-master
readonly: true
serviceName: polardb-readonly
serviceType: ClusterIP
tde:
enable: false
keyringPath: /data/mysql/mysql-keyring/keyring
topology:
nodeSets:
- name: readonly
replicas: 1
role: Learner
template:
metadata: {}
spec:
affinity:
nodeAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- preference:
matchExpressions:
- key: mks.components
operator: In
values:
- enable
weight: 1
podAntiAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- podAffinityTerm:
labelSelector:
matchLabels:
xstore/node-role: candidate
topologyKey: kubernetes.io/hostname
weight: 1
hostNetwork: false
image: polardbx/polardbx-engine-2.0:80-8.0.18-202404091343
resources:
limits:
cpu: "4"
memory: 8Gi
requests:
cpu: "2"
memory: 4Gi
template:
metadata: {}
spec:
hostNetwork: false
upgradeStrategy: BestEffortI have a little doubt, I have the same deployment cr. The version deployed on the x86 architecture is v8.0.30, and the read-only instance runs normally after restarting multiple times. The version deployed on the arm64 architecture is 8.0.18, and the read-only instance cannot run.
have a little doubt, I have the same deployment cr. The version deployed on the x86 architecture is v8.0.30, and the read-only instance runs normally after restarting multiple times. The version deployed on the arm64 architecture is 8.0.18, and the read-only instance cannot run.
Do you set the same image tag in x86 and arm64 environment?
have a little doubt, I have the same deployment cr. The version deployed on the x86 architecture is v8.0.30, and the read-only instance runs normally after restarting multiple times. The version deployed on the arm64 architecture is 8.0.18, and the read-only instance cannot run.
Do you set the same image tag in x86 and arm64 environment?
yes