2019-09-27 10:35:21.379 INFO 832 --- [nio-7577-exec-4] o.s.s.support.LifecycleObjectSupport : started INSTALL INSTALL_INSTALL INSTALL_EXIT INITIAL DELETE DELETE_DELETE DELETE_EXIT ERROR ROLLBACK ROLLBACK_START ROLLBACK_EXIT_INSTALL ROLLBACK_EXIT ROLLBACK_CHOICE ROLLBACK_EXIT_UPGRADE UPGRADE UPGRADE_CANCEL UPGRADE_DEPLOY_TARGET_APPS UPGRADE_CHECK_TARGET_APPS UPGRADE_WAIT_TARGET_APPS UPGRADE_DEPLOY_TARGET_APPS_SUCCEED UPGRADE_DEPLOY_TARGET_APPS_FAILED UPGRADE_START UPGRADE_DELETE_SOURCE_APPS UPGRADE_CHECK_CHOICE UPGRADE_EXIT ERROR_JUNCTION / / uuid=8168f913-2cb0-4399-978a-fb247bf5dae9 / id=demo
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.esotericsoftware.kryo.util.UnsafeUtil (jar:file:/Users/eigenaar/Workspace/spring-cloud-skipper-server-2.1.1.RELEASE.jar!/BOOT-INF/lib/kryo-shaded-4.0.2.jar!/) to constructor java.nio.DirectByteBuffer(long,int,java.lang.Object)
WARNING: Please consider reporting this to the maintainers of com.esotericsoftware.kryo.util.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
2019-09-27 10:35:21.435 INFO 832 --- [eTaskExecutor-1] o.s.c.s.s.s.StateMachineConfiguration : Entering state ObjectState [getIds()=[INITIAL], getClass()=class org.springframework.statemachine.state.ObjectState, hashCode()=202613345, toString()=AbstractState [id=INITIAL, pseudoState=org.springframework.statemachine.state.DefaultPseudoState@5aeb6e2d, deferred=, entryActions=, exitActions=[org.springframework.cloud.skipper.server.statemachine.ResetVariablesAction@312f3050], stateActions=, regions=, submachine=null]]
2019-09-27 10:35:21.451 INFO 832 --- [eTaskExecutor-3] 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=97f8a63d-ade3-4783-89db-68c0c89efc2e / id=demo], getClass()=class org.springframework.statemachine.state.StateMachineState]
2019-09-27 10:35:21.466 INFO 832 --- [eTaskExecutor-3] o.s.c.s.s.s.StateMachineConfiguration : Entering state ObjectState [getIds()=[INSTALL_INSTALL], getClass()=class org.springframework.statemachine.state.ObjectState, hashCode()=128166963, toString()=AbstractState [id=INSTALL_INSTALL, pseudoState=org.springframework.statemachine.state.DefaultPseudoState@11277a82, deferred=, entryActions=[org.springframework.cloud.skipper.server.statemachine.InstallInstallAction@33f349ae], exitActions=, stateActions=, regions=, submachine=null]]
2019-09-27 10:35:21.579 ERROR 832 --- [eTaskExecutor-3] o.s.c.s.s.statemachine.AbstractAction : Action execution failed class=[class org.springframework.cloud.skipper.server.statemachine.InstallInstallAction]
org.springframework.cloud.skipper.SkipperException: No release manager available for 'null'
at org.springframework.cloud.skipper.server.deployer.DefaultReleaseManagerFactory.getReleaseManager(DefaultReleaseManagerFactory.java:51) ~[spring-cloud-skipper-server-core-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
at org.springframework.cloud.skipper.server.service.ReleaseService.install(ReleaseService.java:196) ~[spring-cloud-skipper-server-core-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
Hi, @satheesh-subramani. A PR on this topic was recently merged. See docs.
Though it includes both SCDF and Skipper in the recipe, if you're using Skipper standalone, you would still be able to get an idea on how to configure multiple platform accounts.
You'd manually edit the deployment YAMLs that we ship to include all the desired platform accounts and then
kubectl create apply ... to provision things on K8s. And, that procedure is described in length in this receipe.
You cannot do this when using the helm-chart, however. You could fork the chart to make the necessary customizations also.
@saket88: The most likely cause would be that you don't have enough memory/CPU allocated in your Docker daemon. Check Docker preferences in your machine, and bump it up to at least 8G memory and 6 CPU. If you're using Prometheus + Grafna, they both alone require at least 3G memory.
If you continue to see issues, post the logs at
spring-cloud-dataflow channel, and please also include more details about what you did, and where you are trying to run etc.
EnableSkipperServerand pretty much follow the same steps.
There's a sample to generate a custom SCDF build also: https://github.com/spring-cloud/spring-cloud-dataflow-samples/tree/master/custom-dataflow-builds — this should give you some ideas.
Curious why you're creating your own custom builds, though. DB driver perhaps?
I have an issue with Spring cloud stream url. I am launching my spring cloud tasks from spring cloud stream. Stream contains http-kafka as source and taskLauncerKafka as sink. I used http-kafka service url to launch tasks. kubernetes service url changes after each deployment. First deployment the service name be like sample-stream-v1 after second deployment it will be sample-stream-v2. I am using kubernetes platform. So I have used kubernetes service urls to launch the tasks. The changes in the service name after each stream deployment is difficult to manage. I have tried enabling loadbalacer also. In that case also external ip address changed after each stream rollout. Any solutions ?