2021-01-20 08:30:01.054 ERROR akka.actor.OneForOneStrategy - db - Connection is not available, request timed out after 5000ms. java.sql.SQLTransientConnectionException: db - Connection is not available, request timed out after 5000ms.I guess I apply the wrong statefulstore config
apiVersion: cloudstate.io/v1alpha1 kind: StatefulStore metadata: name: postgres spec: postgres: host: postgres-demo.default.svc.cluster.local credentials: usernameKey: demopostgresadmin passwordKey: demopostgrespwd databaseKey: demopostgresdb
helm install postgres bitnami/postgresql --version 9.1.4 --set persistence.enabled=false --set postgresqlUsername=cloudstate --set postgresqlPassword=cloudstate --set postgresqlDatabase=cloudstate
I also tried to modify my statefulset
template: metadata: labels: app: postgres spec: containers: - name: postgres image: postgres:latest env: - name: POSTGRES_DATABASE value: postgredemo - name: POSTGRES_USERNAME value: postgredemo - name: POSTGRES_USERNAME value: postgredemo
but the env variables are not passed into the cloudstate sidecar, it still use "cloudstate" as user name
Hello CloudState and sorry @umar-nawaz for intrusion ^^ - I have specific question regarding transactions. Current documentation states that
there is no guarantee that the transactions either all succeeded or none
and atomic events are
future Cloudstate functionality
is it still true?
If I have an abstract
payment service which issues events
Bob spent 10$ to buy TeddyBear and another
storage service which supposed to receive
add TeddyBear to Bob's account - is there a way to currently build the CloudState solution that guarantees that there eventually will be
add TeddyBear event(command?) processed per every single
Bob spent 10$ event (keeping these as separate services)? Maybe some CQRS/ACID utilization I don't yet fully understand, or no way? Thanks in advance.
Hi @SlausB :)
Hi @umar-nawaz :)
I think its only fair to respond to your question, as you try out this project, and you got no response for two weeks so far. I'm no core maintainer but let you know, that the project is a bit frozen due to current non-participation.
The core maintainers probably should inform here about that, officially and not letting users or contributors without notice.
(I'm myself absorbed with other work at the moment and can't help with the issue you mentioned)
Hi all -- I am attempting to set up Cloudstate in an on-prem lab. In the docs, the "Installing Cloudstate" page doesn't really have any content so I'm attempting to follow the GKE instructions as best I can, adapted for an on-prem cluster that I manage myself.
I currently have a K8s cluster (1 master / 2 workers) provisioned and I have Cassandra running with an NFS store supporting the StatefulSet. I have run all of the subsequent YAML files to try and bring up the sample shopping cart application. However the Stateful Service is failing to initialize.
There are two containers in the pod spec -- user-container and akka-sidecar. The former appears to be up but the akka-sidecar is failing to pass its health check and so is never marked active, thus the pod is never initialized. I will include below the error and stack trace from the akka-sidecar logs in the hope that someone might point me to a resolution.
I do have a StatefulStore pointing to Cassandra and the shopping cart manifest is pointing to it, but I'm unsure what the error is referring to w/r/t "support event sourced journals".
2021-03-29 23:30:16.500 INFO io.cloudstate.proxy.EntityDiscoveryManager - Received EntitySpec from user function with info: ServiceInfo(js-shopping-cart,0.1.0,node v8.15.1,cloudstate,0.0.1,0,0,UnknownFieldSet(Map()))
2021-03-29 23:30:16.503 ERROR akka.actor.OneForOneStrategy - Service [com.example.shoppingcart.ShoppingCart] has declared an event sourced entity, however, this proxy does not have a configured store, or is using a store that doesn't support event sourced journals. A store that supports journals must be configured in this stateful services resource if event sourcing is to be used.
io.cloudstate.proxy.EntityDiscoveryException: Service [com.example.shoppingcart.ShoppingCart] has declared an event sourced entity, however, this proxy does not have a configured store, or is using a store that doesn't support event sourced journals. A store that supports journals must be configured in this stateful services resource if event sourcing is to be used.
There's a secondary error below which I believe proceeds from the one above:
2021-03-29 23:30:16.951 DEBUG io.cloudstate.proxy.HealthCheckReady - Error performing server manager readiness check
akka.actor.ActorNotFound: Actor not found for: ActorSelection[Anchor(akka://cloudstate-proxy/), Path(/user/server-manager-supervisor/server-manager)]
"Cloudstate is no longer actively developed"
Follow the "old" OSS-community around it on one of the OSS projects implementing and refine ideas of Cloudstate at https://eigr.io – we're friendly and we have cookies (I meant stickers).