Please answer these questions before submitting your issue.
Question
- What do you want to know?
How do I start skwalking up using h2 as the backend
Bug
-
Which version of SkyWalking, OS, and JRE?
Skywalking version: 8.7.0
OS: MacOs 10.13.6
JRE: 8
-
Which company or project?
QuadCorps Ltd
-
What happened?
If possible, provide a way to reproduce the error. e.g. demo application, component version.
I am trying to run skywalking on a local cluster (Docker Engine) using your helm chart to install it
This is the command that I ran
helm install "${SKYWALKING_RELEASE_NAME}" skywalking -n "${SKYWALKING_RELEASE_NAMESPACE}"
--set oap.image.tag=8.7.0-es7
--set oap.storageType=h2
--set ui.image.tag=8.7.0
--set elasticsearch.enabled=false
Requirement or improvement
- Please describe your requirements or improvement suggestions.
The UI pod comes up but the OAP does not, it moans about tables not being present.
By default it looks like OAP is started in no-init mode set by its env variables for the JAVA_OPTS
Looking at the OAP pod logs its moaning about tables not existing, which makes me think h2 needs to be initialized
How do I do that? Override the JAVA_OPTS with -Dmode=init or -Dmode=init-only
I cant find anything in your docs that describes how to get this to work using h2
Also is the OAP image tag *-es7 correct even when using h2 and not elastic search?
Please answer these questions before submitting your issue.
Question
How do I start skwalking up using h2 as the backend
Bug
Which version of SkyWalking, OS, and JRE?
Skywalking version: 8.7.0
OS: MacOs 10.13.6
JRE: 8
Which company or project?
QuadCorps Ltd
What happened?
If possible, provide a way to reproduce the error. e.g. demo application, component version.
I am trying to run skywalking on a local cluster (Docker Engine) using your helm chart to install it
This is the command that I ran
helm install "${SKYWALKING_RELEASE_NAME}" skywalking -n "${SKYWALKING_RELEASE_NAMESPACE}"
--set oap.image.tag=8.7.0-es7
--set oap.storageType=h2
--set ui.image.tag=8.7.0
--set elasticsearch.enabled=false
Requirement or improvement
The UI pod comes up but the OAP does not, it moans about tables not being present.
By default it looks like OAP is started in no-init mode set by its env variables for the JAVA_OPTS
Looking at the OAP pod logs its moaning about tables not existing, which makes me think h2 needs to be initialized
How do I do that? Override the JAVA_OPTS with -Dmode=init or -Dmode=init-only
I cant find anything in your docs that describes how to get this to work using h2
Also is the OAP image tag *-es7 correct even when using h2 and not elastic search?