我们在Kubernetes中部署了SCDF。通过SCDF UI,我们可以使用基于Docker的Source,Processor和Sink应用程序创建流。但是,在部署流时,状态不会从“正在部署”更改,并且最终会失败。我们尝试设置“ CPU和请求”属性的限制,但这无济于事。
应用程序日志显示Tomcat尚未初始化,因为未激活“活动性和就绪性”探针的结果导致未公开哪些/ actuator端点。
对这个问题可能是什么以及如何解决这个问题有任何想法吗?
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'
船长日志
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
答案 0 :(得分:0)
SCDF / Skipper日志实际上并没有包含太多信息。也没有任何关于失败的报道。
这里有一些标准要检查的东西。
1)如果您在Minikube或真实的K8s集群中运行SCDF,请确保集群中有足够的可用资源容量。您可以通过描述K8s节点或使用诸如Octant之类的工具来确认是否有足够的CPU或内存可用。
2)请注意,通过SCDF部署的服务以及流/任务应用程序数量越多,您在K8s集群中所需的资源就越多。例如,如果您要配置Prometheus + Grafana来监视SCDF中的流/任务应用程序,则它们两者的组合至少需要3G内存。再次,资源限制错误将出现在群集节点中。
3)查看流/任务窗格日志。还描述K8中的流/任务窗格,以查看准备就绪/活动性探针为何失败-错误将在输出的最后显示。