start benchmark issue
Opened this issue · 2 comments
s083r commented
running:
#cat config/benchmark.finality.local.sample.json
{
"name": "bm1",
"type": "local",
"benchmark": "finality",
"startNodes": 1,
"endNodes": 10,
"blocks": {
"offset": 10,
"measure": 10
},
"reuseCluster": true
#node --trace-warnings --unhandled-rejections=warn . benchmark -c config/benchmark.finality.local.sample.json --verbose
returns:
Creating cluster 'bm1'...
Creating cluster "bm1" ...
• Ensuring node image (kindest/node:v1.17.0) 🖼 ...
✓ Ensuring node image (kindest/node:v1.17.0) 🖼
• Preparing nodes 📦 ...
✓ Preparing nodes 📦
• Writing configuration 📜 ...
✓ Writing configuration 📜
• Starting control-plane 🕹️ ...
✓ Starting control-plane 🕹️
• Installing CNI 🔌 ...
✓ Installing CNI 🔌
• Installing StorageClass 💾 ...
✓ Installing StorageClass 💾
Set kubectl context to "kind-bm1"
You can now use your cluster with:
kubectl cluster-info --context kind-bm1
Not sure what to do next? 😅 Check out https://kind.sigs.k8s.io/docs/user/quick-start/
Done
Installing dependencies...
"w3f" has been added to your repositories
"jetstack" has been added to your repositories
"loki" has been added to your repositories
"ingress-nginx" has been added to your repositories
"bitnami" has been added to your repositories
"prometheus-community" has been added to your repositories
"grafana" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ingress-nginx" chart repository
...Successfully got an update from the "loki" chart repository
...Successfully got an update from the "jetstack" chart repository
...Successfully got an update from the "w3f" chart repository
...Successfully got an update from the "grafana" chart repository
...Successfully got an update from the "prometheus-community" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈ Happy Helming!⎈
Installing dependencies
NAME STATUS AGE
default Active 11s
kube-node-lease Active 12s
kube-public Active 12s
kube-system Active 12s
local-path-storage Active 8s
found namespaces: NAME STATUS AGE
default Active 11s
kube-node-lease Active 12s
kube-public Active 12s
kube-system Active 12s
local-path-storage Active 8s
namespace/cert-manager created
NAME STATUS AGE
cert-manager Active 0s
default Active 11s
kube-node-lease Active 12s
kube-public Active 12s
kube-system Active 12s
local-path-storage Active 8s
found namespaces: NAME STATUS AGE
cert-manager Active 0s
default Active 11s
kube-node-lease Active 12s
kube-public Active 12s
kube-system Active 12s
local-path-storage Active 8s
namespace/monitoring created
NAME
STATUS
AGE
cert-manager Active 0s
default Active 11s
kube-node-lease Active
12s
kube-public Active 12s
kube-system Active 12s
local-path-storage Active 8s
monitoring Active 0s
found namespaces: NAME STATUS AGE
cert-manager Active 0s
default Active 11s
kube-node-lease Active 12s
kube-public Active 12s
kube-system Active 12s
local-path-storage Active 8s
monitoring Active 0s
namespace/ingress created
NAME STATUS AGE
cert-manager Active 1s
default Active 12s
ingress Active 0s
kube-node-lease Active 13s
kube-public Active 13s
kube-system Active
local-path-storage Active 9s
monitoring Active 1s
found namespaces: NAME STATUS AGE
cert-manager Active 1s
default Active 12s
ingress Active 0s
kube-node-lease Active 13s
kube-public Active 13s
kube-system Active 13s
local-path-storage Active 9s
monitoring Active 1s
namespace/bm1 created
upgrade --install polkadot-base-services -f ../deployments/bm1/values/node-base.yaml --version v0.34.1 --namespace bm1 w3f/polkadot-base-services
Release "polkadot-base-services" does not exist. Installing it now.
NAME: polkadot-base-services
LAST DEPLOYED: Fri Oct 29 16:57:59 2021
NAMESPACE: bm1
STATUS: deployed
REVISION: 1
TEST SUITE: None
Done
Initializing nodes...
Could not initialize nodes: Cannot read property 'custom' of undefined
Any suggestions would be appreciated!
Thank you!
danila-zubkov commented
Solved by:
{
"name": "bm1",
"type": "local",
"benchmark": "finality",
"chainspec": {
"custom": "false"
},
"startNodes": 2,
"endNodes": 4,
"blocks": {
"offset": 10,
"measure": 10
},
"reuseCluster": true
}```
Nexus2k commented
I also suggest to bump the kindest/node:v1.17.0 version to 1.21 or newer.