Question

我想在我的环境中执行回滚部署。

命令：

11:47:10,206 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 72) MSC000001: Failed to start service org.camunda.bpm.platform.process-engine.default: org.jboss.msc.service.StartException in service org.camunda.bpm.platform.process-engine.default: org.camunda.bpm.engine.ProcessEngineException: ENGINE-03018 Could not check if tables are already present using metadata.
    at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.11.0//org.camunda.bpm.container.impl.jboss.service.MscManagedProcessEngineController$1.run(MscManagedProcessEngineController.java:98)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
    at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
    at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
    at java.base/java.lang.Thread.run(Thread.java:834)
    at org.jboss.threads@2.3.2.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
Caused by: org.camunda.bpm.engine.ProcessEngineException: ENGINE-03018 Could not check if tables are already present using metadata.
    at org.camunda.bpm.camunda-engine@7.11.0//org.camunda.bpm.engine.impl.db.EnginePersistenceLogger.checkDatabaseTableException(EnginePersistenceLogger.java:241)
    at org.camunda.bpm.camunda-engine@7.11.0//org.camunda.bpm.engine.impl.db.sql.DbSqlSession.isTablePresent(DbSqlSession.java:494)
    at org.camunda.bpm.camunda-engine@7.11.0//org.camunda.bpm.engine.impl.db.sql.DbSqlSession.isEngineTablePresent(DbSqlSession.java:434)
    at org.camunda.bpm.camunda-engine@7.11.0//org.camunda.bpm.engine.impl.db.AbstractPersistenceSession.dbSchemaUpdate(AbstractPersistenceSession.java:218)
    at org.camunda.bpm.camunda-engine@7.11.0//org.camunda.bpm.engine.impl.SchemaOperationsProcessEngineBuild.execute(SchemaOperationsProcessEngineBuild.java:56)
    at org.camunda.bpm.camunda-engine@7.11.0//org.camunda.bpm.engine.impl.SchemaOperationsProcessEngineBuild.execute(SchemaOperationsProcessEngineBuild.java:34)
    at org.camunda.bpm.camunda-engine@7.11.0//org.camunda.bpm.engine.impl.interceptor.CommandExecutorImpl.execute(CommandExecutorImpl.java:28)
    at org.camunda.bpm.camunda-engine@7.11.0//org.camunda.bpm.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:107)
    at org.camunda.bpm.camunda-engine@7.11.0//org.camunda.bpm.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:33)
    at org.camunda.bpm.camunda-engine@7.11.0//org.camunda.bpm.engine.impl.ProcessEngineImpl.executeSchemaOperations(ProcessEngineImpl.java:120)
    at org.camunda.bpm.camunda-engine@7.11.0//org.camunda.bpm.engine.impl.ProcessEngineImpl.<init>(ProcessEngineImpl.java:93)
    at org.camunda.bpm.camunda-engine@7.11.0//org.camunda.bpm.engine.impl.cfg.ProcessEngineConfigurationImpl.buildProcessEngine(ProcessEngineConfigurationImpl.java:798)
    at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.11.0//org.camunda.bpm.container.impl.jboss.service.MscManagedProcessEngineController.startProcessEngine(MscManagedProcessEngineController.java:178)
    at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.11.0//org.camunda.bpm.container.impl.jboss.service.MscManagedProcessEngineController$2.run(MscManagedProcessEngineController.java:132)
    at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.11.0//org.camunda.bpm.container.impl.jboss.service.MscManagedProcessEngineController$2.run(MscManagedProcessEngineController.java:130)
    at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.11.0//org.camunda.bpm.container.impl.jboss.util.Tccl.runWithTccl(Tccl.java:54)
    at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.11.0//org.camunda.bpm.container.impl.jboss.util.Tccl.runUnderClassloader(Tccl.java:46)
    at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.11.0//org.camunda.bpm.container.impl.jboss.service.MscManagedProcessEngineController.startInternal(MscManagedProcessEngineController.java:130)
    at org.camunda.bpm.wildfly.camunda-wildfly-subsystem@7.11.0//org.camunda.bpm.container.impl.jboss.service.MscManagedProcessEngineController$1.run(MscManagedProcessEngineController.java:91)
    ... 8 more
Caused by: org.apache.ibatis.exceptions.PersistenceException:

正在执行的步骤：

使用旧配置创建容器
删除旧豆荚

是否有一种不执行最后一步的方法-例如，开发人员想检查为什么init命令失败并进行调试。

我没有在文档中找到有关此信息。

Answer 1

是的，有可能在进行推广之前，首先需要从不健康的吊舱中删除标签（对应于控制该吊舱的副本集）。这样，pod将不再属于部署，即使您进行部署，它也仍然存在。示例：

$kubectl get deployment
NAME      READY   UP-TO-DATE   AVAILABLE   AGE 
sleeper   1/1     1            1           47h 
$kubectl get pod --show-labels
NAME                      READY   STATUS    RESTARTS   AGE     LABELS
sleeper-d75b55fc9-87k5k   1/1     Running   0          5m46s   pod-template-hash=d75b55fc9,run=sleeper
$kubectl label pod sleeper-d75b55fc9-87k5k  pod-template-hash- run-
pod/sleeper-d75b55fc9-87k5k labeled
$kubectl get pod --show-labels
NAME                      READY   STATUS    RESTARTS   AGE     LABELS
sleeper-d75b55fc9-87k5k   1/1     Running   0          6m34s   <none>
sleeper-d75b55fc9-swkj9   1/1     Running   0          3s      pod-template-hash=d75b55fc9,run=sleeper

所以这里发生了什么，我们有一个sleeper-d75b55fc9-87k5k部署的pod sleeper，我们从其中删除了所有标签，部署检测到pod已“消失”，因此创建了一个新{{ 1}}，但是旧的仍然存在并且可以调试了。仅有卷sleeper-d75b55fc9-swkj9受发布影响。

在回滚部署中不要删除Pod

1 个答案: