SCDF流仍处于“部署”状态

Question

我们在库伯内特斯部署了自卫队。从SCDF UI中，我们可以使用基于Docker的源处理器创建流

应用程序日志显示Tomcat没有初始化，因为没有暴露哪些/执行器endpoint

对问题可能是什么以及如何解决有什么想法吗？

SCDF日志

2019-12-04 06:14:18.264  INFO 1 --- [p-nio-80-exec-7] .s.c.d.s.s.i.AppDeploymentRequestCreator : Creating resource with [docker:215135100958.dkr.ecr.eu-west-1.amazonaws.com/scdf/gce-batch-task-sink:0.0.2-SNAPSHOT] for application [tasklauncherV2]
2019-12-04 06:14:18.266  INFO 1 --- [p-nio-80-exec-7] .s.c.d.s.s.i.AppDeploymentRequestCreator : Creating resource with [docker:215135100958.dkr.ecr.eu-west-1.amazonaws.com/scdf/gce-batch-task-processor:0.0.3-SNAPSHOT] for application [taskprocessorV3]
2019-12-04 06:14:18.268  INFO 1 --- [p-nio-80-exec-7] o.s.c.d.s.stream.SkipperStreamDeployer   : Deploying Stream batchstreamV1 using skipper.
2019-12-04 06:14:18.274  INFO 1 --- [p-nio-80-exec-7] o.s.c.d.s.stream.SkipperStreamDeployer   : Using platform 'default'

Skipper日志

2019-12-04 06:14:18.307  INFO 1 --- [nio-7577-exec-2] o.s.s.s.DefaultStateMachineService       : Acquiring machine with id batchstreamV1
2019-12-04 06:14:18.307  INFO 1 --- [nio-7577-exec-2] o.s.s.s.DefaultStateMachineService       : Getting new machine from factory with id batchstreamV1
2019-12-04 06:14:18.311  INFO 1 --- [nio-7577-exec-2] o.s.s.support.LifecycleObjectSupport     : started org.springframework.statemachine.trigger.TimerTrigger@76ca974a
2019-12-04 06:14:18.311  INFO 1 --- [nio-7577-exec-2] o.s.s.support.LifecycleObjectSupport     : started org.springframework.statemachine.support.DefaultStateMachineExecutor@1a44aa85
2019-12-04 06:14:18.311  INFO 1 --- [nio-7577-exec-2] o.s.s.support.LifecycleObjectSupport     : started INITIAL UPGRADE UPGRADE_DEPLOY_TARGET_APPS_SUCCEED UPGRADE_DEPLOY_TARGET_APPS_FAILED UPGRADE_DEPLOY_TARGET_APPS UPGRADE_START UPGRADE_DELETE_SOURCE_APPS UPGRADE_CHECK_TARGET_APPS UPGRADE_WAIT_TARGET_APPS UPGRADE_CANCEL UPGRADE_EXIT UPGRADE_CHECK_CHOICE DELETE DELETE_DELETE DELETE_EXIT ROLLBACK ROLLBACK_START ROLLBACK_EXIT_UPGRADE ROLLBACK_CHOICE ROLLBACK_EXIT ROLLBACK_EXIT_INSTALL INSTALL INSTALL_INSTALL INSTALL_EXIT ERROR ERROR_JUNCTION  /  / uuid=581f43a4-02bc-4275-b76e-afc7822c45df / id=batchstreamV1
2019-12-04 06:14:18.329  INFO 1 --- [eTaskExecutor-3] o.s.c.s.s.s.StateMachineConfiguration    : Entering state ObjectState [getIds()=[INITIAL], getClass()=class org.springframework.statemachine.state.ObjectState, hashCode()=1676784192, toString()=AbstractState [id=INITIAL, pseudoState=org.springframework.statemachine.state.DefaultPseudoState@2332ab0f, deferred=[], entryActions=[], exitActions=[org.springframework.cloud.skipper.server.statemachine.ResetVariablesAction@1dbd580], stateActions=[], regions=[], submachine=null]]
2019-12-04 06:14:18.350  INFO 1 --- [eTaskExecutor-4] o.s.c.s.s.s.StateMachineConfiguration    : Entering state StateMachineState [getIds()=[INSTALL], toString()=AbstractState [id=INSTALL, pseudoState=null, deferred=[], entryActions=[], exitActions=[], stateActions=[], regions=[], submachine=INSTALL_INSTALL INSTALL_EXIT  /  / uuid=263e446f-15f4-4913-8ee0-037f17c49ad3 / id=batchstreamV1], getClass()=class org.springframework.statemachine.state.StateMachineState]
2019-12-04 06:14:18.367  INFO 1 --- [eTaskExecutor-4] o.s.c.s.s.s.StateMachineConfiguration    : Entering state ObjectState [getIds()=[INSTALL_INSTALL], getClass()=class org.springframework.statemachine.state.ObjectState, hashCode()=1390837147, toString()=AbstractState [id=INSTALL_INSTALL, pseudoState=org.springframework.statemachine.state.DefaultPseudoState@799fbe4c, deferred=[], entryActions=[org.springframework.cloud.skipper.server.statemachine.InstallInstallAction@6732726], exitActions=[], stateActions=[], regions=[], submachine=null]]
2019-12-04 06:14:18.415  INFO 1 --- [eTaskExecutor-4] o.s.c.d.s.k.KubernetesAppDeployer        : Preparing to run a container from  Docker Resource [docker:215135100958.dkr.ecr.eu-west-1.amazonaws.com/scdf/gce-batch-task-sink:0.0.2-SNAPSHOT]. This may take some time if the image must be downloaded from a remote container registry.
2019-12-04 06:14:18.431  INFO 1 --- [eTaskExecutor-4] o.s.c.d.s.k.DefaultContainerFactory      : Using Docker image: 215135100958.dkr.ecr.eu-west-1.amazonaws.com/scdf/gce-batch-task-sink:0.0.2-SNAPSHOT
2019-12-04 06:14:18.431  INFO 1 --- [eTaskExecutor-4] o.s.c.d.s.k.DefaultContainerFactory      : Using Docker entry point style: exec
2019-12-04 06:14:18.457  INFO 1 --- [eTaskExecutor-4] o.s.c.d.s.k.KubernetesAppDeployer        : Preparing to run a container from  Docker Resource [docker:215135100958.dkr.ecr.eu-west-1.amazonaws.com/scdf/gce-batch-task-processor:0.0.3-SNAPSHOT]. This may take some time if the image must be downloaded from a remote container registry.
2019-12-04 06:14:18.473  INFO 1 --- [eTaskExecutor-4] o.s.c.d.s.k.DefaultContainerFactory      : Using Docker image: 215135100958.dkr.ecr.eu-west-1.amazonaws.com/scdf/gce-batch-task-processor:0.0.3-SNAPSHOT
2019-12-04 06:14:18.473  INFO 1 --- [eTaskExecutor-4] o.s.c.d.s.k.DefaultContainerFactory      : Using Docker entry point style: exec
2019-12-04 06:14:18.579  INFO 1 --- [eTaskExecutor-4] o.s.s.support.LifecycleObjectSupport     : stopped org.springframework.statemachine.support.DefaultStateMachineExecutor@149d3f32
2019-12-04 06:14:18.579  INFO 1 --- [eTaskExecutor-4] o.s.s.support.LifecycleObjectSupport     : stopped INSTALL_INSTALL INSTALL_EXIT  /  / uuid=263e446f-15f4-4913-8ee0-037f17c49ad3 / id=batchstreamV1
2019-12-04 06:14:18.579  INFO 1 --- [eTaskExecutor-4] o.s.c.s.s.s.StateMachineConfiguration    : Entering state ObjectState [getIds()=[INITIAL], getClass()=class org.springframework.statemachine.state.ObjectState, hashCode()=1676784192, toString()=AbstractState [id=INITIAL, pseudoState=org.springframework.statemachine.state.DefaultPseudoState@2332ab0f, deferred=[], entryActions=[], exitActions=[org.springframework.cloud.skipper.server.statemachine.ResetVariablesAction@1dbd580], stateActions=[], regions=[], submachine=null]]
2019-12-04 06:14:18.579  INFO 1 --- [eTaskExecutor-4] o.s.c.s.s.s.SkipperStateMachineService   : setting future value org.springframework.cloud.skipper.domain.Release@4348eec0
2019-12-04 06:14:18.579  INFO 1 --- [eTaskExecutor-4] o.s.s.support.LifecycleObjectSupport     : started org.springframework.statemachine.support.DefaultStateMachineExecutor@149d3f32
2019-12-04 06:14:18.579  INFO 1 --- [eTaskExecutor-4] o.s.s.support.LifecycleObjectSupport     : started INSTALL_INSTALL INSTALL_EXIT  /  / uuid=263e446f-15f4-4913-8ee0-037f17c49ad3 / id=batchstreamV1

Answer 1

SCDF/Skipper日志实际上并不包含太多信息。也没有关于失败的报道。

这里有一些标准的东西要检查。

1） 如果您在Minikube或真正的K8s集群中运行SCDF，请确保集群中有足够的可用资源容量。您可以通过描述K8s节点或使用Octant之类的工具来确认是否有足够的CPU或内存可用。

2）请注意，您通过SCDF部署的服务和流/任务应用程序的数量越多，您在K8s集群中需要的资源就越多。例如，如果您配置Prometheus Grafana来监控SCDF中的流/任务应用程序，它们作为一个组合至少需要3G的内存。再次，资源限制错误将显示在集群节点中。

3） 查看流/任务吊舱日志。还请描述K8s中的流/任务吊舱，以了解就绪性/活性探测失败的原因-错误将在输出的最后显示。