PolarDB Stack is a DBaaS implementation for PolarDB-for-Postgres, as an operator creates and manages PolarDB/PostgreSQL clusters running in Kubernetes. It provides re-construct, failover swtich-over, scale up/out, high-available capabilities for each clusters.
License: Apache License 2.0
I create pvc by executing
curl -X POST "http://10.0.0.77:2002/pvcs" -H "accept: application/json" -H "Content-Type: application/json" -d "{ \"name\": \"pvc-32ze341nncwlczm47bsre\", \"namespace\": \"default\", \"need_format\": true, \"volume_id\": \"32ze341nncwlczm47bsre\", \"volume_type\": \"lun\"}"
but get error: {"error":"can not find lv for wwid 32ze341nncwlczm47bsre"}.
The ouput of multipah -ll is empty. How can I get correct volume_id?
I install polardb by install.sh and I have modify env.yaml according to my own configuration. However, pod created by polarstack-daemon can't work properly. Here is the log of the pod.
----------------------------------------------------------------------------------------------
| |
| polarbox cloud branch:master commitId:b3f3fde34f4e018cf8ca28625e8d9042ee7bb1f1
| polarbox repo https://github.com/ApsaraDB/PolarDB-Stack-Daemon.git
| polarbox commitDate Wed Oct 20 14:33:55 2021 +0800
| |
----------------------------------------------------------------------------------------------
start polarbox controller-manager cloud-provider
I0207 18:21:43.031321 1 main.go:48] --------------------------------------------------------------------------------------------
I0207 18:21:43.031391 1 main.go:49] | |
I0207 18:21:43.031398 1 main.go:50] | polarstack-daemon |
I0207 18:21:43.031404 1 main.go:51] | |
I0207 18:21:43.031410 1 main.go:52] --------------------------------------------------------------------------------------------
W0207 18:21:43.032072 1 client_config.go:541] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
[GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.
[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.
- using env: export GIN_MODE=release
- using code: gin.SetMode(gin.ReleaseMode)
[GIN-debug] GET /healthz --> github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager/bizapis.health (3 handlers)
[GIN-debug] GET /api/v1/TestConn --> github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager/bizapis.Handle.func1 (3 handlers)
[GIN-debug] GET /api/v1/GetStandByIp --> github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager/bizapis.Handle.func1 (3 handlers)
[GIN-debug] POST /api/v1/RequestCheckCoreVersion --> github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager/bizapis.Handle.func1 (3 handlers)
[GIN-debug] POST /api/v1/InnerCheckCoreVersion --> github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager/bizapis.Handle.func1 (3 handlers)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x12651a0]
goroutine 22 [running]:
golang.org/x/crypto/ssh.(*connection).clientAuthenticate(0xc0003e5e00, 0xc000327860, 0x0, 0xa)
/go/pkg/mod/golang.org/x/[email protected]/ssh/client_auth.go:63 +0x420
golang.org/x/crypto/ssh.(*connection).clientHandshake(0xc0003e5e00, 0xc000488e40, 0x9, 0xc000327860, 0x0, 0x0)
/go/pkg/mod/golang.org/x/[email protected]/ssh/client.go:113 +0x2b6
golang.org/x/crypto/ssh.NewClientConn(0x180c020, 0xc0000e1bb0, 0xc000488e40, 0x9, 0xc000327380, 0x180c020, 0xc0000e1bb0, 0x0, 0x0, 0xc000488e40, ...)
/go/pkg/mod/golang.org/x/[email protected]/ssh/client.go:83 +0xf8
golang.org/x/crypto/ssh.Dial(0x15d5acb, 0x3, 0xc000488e40, 0x9, 0xc000327380, 0xc000488e40, 0x9, 0x1)
/go/pkg/mod/golang.org/x/[email protected]/ssh/client.go:177 +0xb3
github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager.SSHConnect(0x15d6479, 0x4, 0xc000488dc8, 0x6, 0x16, 0x2, 0x2, 0xc00003ce00)
/go/src/github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager/sshutil.go:74 +0x26a
github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager.(*SSHConnection).Init(0xc0005cb7a0, 0x4, 0xc000488dc8)
/go/src/github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager/sshutil.go:119 +0x17b
github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager/node_net_status.(*PolarNodeNetworkProbe).__initSSH(0xc000529f80, 0x1b, 0xc0001184e0)
/go/src/github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager/node_net_status/node_network_probe.go:547 +0x36f
github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager/node_net_status.(*PolarNodeNetworkProbe).Init(0xc000529f80, 0x0, 0x0)
/go/src/github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager/node_net_status/node_network_probe.go:164 +0xc5
github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager/node_net_status.StartNodeNetworkProbe(0xc00042e000, 0xc000048540)
/go/src/github.com/ApsaraDB/PolarDB-Stack-Daemon/polar-controller-manager/node_net_status/node_network_probe.go:116 +0x208
created by github.com/ApsaraDB/PolarDB-Stack-Daemon/cmd/daemon/app.Run
/go/src/github.com/ApsaraDB/PolarDB-Stack-Daemon/cmd/daemon/app/contorllermanager.go:97 +0x1ae
k8s: v1.23, 3 machines
docker: v20.10.12
mysql: v8.0.26
Here is imformation of pods:
NAME READY STATUS RESTARTS AGE
calico-kube-controllers-85b5b5888d-rcpmx 1/1 Running 2 (6d3h ago) 10d
calico-node-9dcsb 1/1 Running 0 10d
calico-node-knnwv 1/1 Running 0 10d
calico-node-wgf4h 1/1 Running 2 (6d3h ago) 10d
coredns-64897985d-tphjz 1/1 Running 2 (6d3h ago) 10d
coredns-64897985d-vq2cq 1/1 Running 2 (6d3h ago) 10d
etcd-vm08-1 1/1 Running 7 (6d3h ago) 10d
kube-apiserver-vm08-1 1/1 Running 7 (6d3h ago) 10d
kube-controller-manager-vm08-1 1/1 Running 3 (6d3h ago) 10d
kube-proxy-ctc85 1/1 Running 0 10d
kube-proxy-gzpxg 1/1 Running 2 (6d3h ago) 10d
kube-proxy-vdxmm 1/1 Running 0 10d
kube-scheduler-vm08-1 1/1 Running 3 (6d3h ago) 10d
manager-65dcc96d8d-49d4z 1/1 Running 0 6m44s
manager-65dcc96d8d-6r6ql 1/1 Running 0 6m44s
manager-65dcc96d8d-l9rvp 1/1 Running 0 6m44s
polardb-sms-manager-66db8bbcbf-4dr7q 1/1 Running 0 6m44s
polardb-sms-manager-66db8bbcbf-6mhpc 1/1 Running 0 6m44s
polardb-sms-manager-66db8bbcbf-qzvwf 1/1 Running 0 6m44s
polarstack-daemon-2fpcg 0/1 CrashLoopBackOff 6 (48s ago) 6m44s
polarstack-daemon-knpxs 0/1 CrashLoopBackOff 6 (47s ago) 6m44s
polarstack-daemon-mthf7 0/1 CrashLoopBackOff 6 (59s ago) 6m44s
Here is imformation of cm:
NAME DATA AGE
calico-config 4 10d
ccm-config 6 24m
cloud-provider-port-usage-vm08-1 0 2d5h
cloud-provider-port-usage-vm08-2 0 2d5h
cloud-provider-port-usage-vm08-3 0 2d5h
cloud-provider-wwid-usage-vm08-2 0 4h51m
cloud-provider-wwid-usage-vm08-3 0 4h51m
controller-config 27 24m
coredns 1 10d
extension-apiserver-authentication 6 10d
instance-system-resources 3 24m
kube-proxy 2 10d
kube-root-ca.crt 1 10d
kubeadm-config 1 10d
kubelet-config-1.23 1 10d
metabase-config 1 24m
mpd.polardb.aliyun.com 0 6d2h
polardb-sms-manager 1 24m
polardb4mpd-controller 5 24m
polarstack-daemon-version-availability-vm08-1 2 2d5h
polarstack-daemon-version-availability-vm08-2 2 2d5h
polarstack-daemon-version-availability-vm08-3 2 2d5h
postgresql-1-0-level-polar-o-x4-large-config-rwo 17 24m
postgresql-1-0-level-polar-o-x4-large-resource-rwo 12 24m
postgresql-1-0-level-polar-o-x4-medium-config-rwo 17 24m
postgresql-1-0-level-polar-o-x4-medium-resource-rwo 12 24m
postgresql-1-0-level-polar-o-x4-xlarge-config-rwo 17 24m
postgresql-1-0-level-polar-o-x4-xlarge-resource-rwo 12 24m
postgresql-1-0-level-polar-o-x8-12xlarge-config-rwo 17 24m
postgresql-1-0-level-polar-o-x8-12xlarge-exclusive-config-rwo 17 24m
postgresql-1-0-level-polar-o-x8-12xlarge-exclusive-resource-rwo 13 24m
postgresql-1-0-level-polar-o-x8-12xlarge-resource-rwo 14 24m
postgresql-1-0-level-polar-o-x8-2xlarge-config-rwo 17 24m
postgresql-1-0-level-polar-o-x8-2xlarge-exclusive-config-rwo 17 24m
postgresql-1-0-level-polar-o-x8-2xlarge-exclusive-resource-rwo 13 24m
postgresql-1-0-level-polar-o-x8-2xlarge-resource-rwo 12 24m
postgresql-1-0-level-polar-o-x8-4xlarge-config-rwo 17 24m
postgresql-1-0-level-polar-o-x8-4xlarge-exclusive-config-rwo 17 24m
postgresql-1-0-level-polar-o-x8-4xlarge-exclusive-resource-rwo 13 24m
postgresql-1-0-level-polar-o-x8-4xlarge-resource-rwo 12 24m
postgresql-1-0-level-polar-o-x8-xlarge-config-rwo 17 24m
postgresql-1-0-level-polar-o-x8-xlarge-resource-rwo 12 24m
postgresql-1-0-minor-version-info-rwo-image-open 6 24m
postgresql-1-0-mycnf-template-rwo 1 24m
When I try to apply config.all.yaml, I get following error:
Error from server (Invalid): error when creating "config/all.yaml": Deployment.apps "manager" is invalid: spec.template.spec.containers[0].volumeMounts[2].name: Not found: "config-etcd"
I read all.yaml and find no volumes named config-etcd. How can I fix it?
k8s: v1.23
docker: v20.10.12
I plan to install polardb by install.sh. However I get the following error:
install.go:178: [debug] Original chart version: ""
install.go:195: [debug] CHART PATH: /home/vm08-1/PolarDB-Stack-Operator/polardb-stack-chart
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
helm.go:84: [debug] unable to recognize "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
unable to build kubernetes objects from release manifest
I check config/all.yaml of this repo and kubernetes official website. I find the yaml file's syntax is not suitable for the version 1.23 of k8s. I want to know if the development team will update chart to fit the latest k8s in the feature?
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.