k8s restart skywalking-oap error #12118
Replies: 1 comment 4 replies
-
|
Which database are you running? Did you wipe the storage then restart OAP? |
Beta Was this translation helpful? Give feedback.
-
|
I deployed using the default elasticsearch for helm, and I didn't wipe the storage before restart. |
Beta Was this translation helpful? Give feedback.
-
|
The error shows you did. Maybe you don't setup persistent storage for elasticsearch somehow, or it is unhealthy. |
Beta Was this translation helpful? Give feedback.
-
|
Well, when there was a problem at first, when I tried the recovery steps searched on the network, I mistakenly deleted the previous replica set of elasticsearch, resulting in data loss. Is there any good way I can restore skywalking now? the loss of the previous monitoring data has little impact on me. |
Beta Was this translation helpful? Give feedback.
-
|
Follow the doc and run reinit, https://github.com/apache/skywalking-helm?tab=readme-ov-file#rerun-oap-init-job |
Beta Was this translation helpful? Give feedback.
-
I am trying to restart skywalking-oap. I found that the initialization of the container failed. The following error is reported. Please help me solve it.
skywalking oap version:9.7.0
2024-04-16 12:57:39,176 org.apache.skywalking.oap.server.core.storage.model.ModelInstaller 43 [main] INFO [] - table: alarm_record does not exist. OAP is running in 'no-init' mode, waiting... retry 3s later.Beta Was this translation helpful? Give feedback.
All reactions