Persist of [akka.persistence.journal.Tagged] failed in […Entity] with id [790B7CC207A1000], caused by: {Circuit Breaker Timed out


(Aman Sharma) #1

I am running my service on Lagom cluster , for the very first API Request I hit to any of the node in the Cluster gives me this issue :->

2019-02-13 12:32:34,693 …service application-akka.actor.default-dispatcher-17 ERROR BookingService - Exception in RestCallId{method=POST, pathPattern=’/external/v1/provisional_bookings’}

java.lang.RuntimeException: java.util.concurrent.CompletionException: com.lightbend.lagom.javadsl.persistence.PersistentEntity$PersistException: Persist of [akka.persistence.journal.Tagged] failed in […ProvisionalBookingEntity] with id [790B7CC207A1000], caused by: {Circuit Breaker Timed out.

at …ServiceImpl.lambda$createProvisionalBooking$9(BookingServiceImpl.java:195)

at java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:870)

at java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:852)

at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)

at java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:561)

at java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:929)

at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:442)

at java.lang.Thread.run(Thread.java:748)

Caused by: java.util.concurrent.CompletionException: com.lightbend.lagom.javadsl.persistence.PersistentEntity$PersistException: Persist of [akka.persistence.journal.Tagged] failed in […ProvisionalBookingEntity] with id [790B7CC207A1000], caused by: {Circuit Breaker Timed out.

at java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:326)

at java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:338)

at java.util.concurrent.CompletableFuture.uniRelay(CompletableFuture.java:911)

at java.util.concurrent.CompletableFuture.uniCompose(CompletableFuture.java:953)

at java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:926)

… 2 common frames omitted

Caused by: com.lightbend.lagom.javadsl.persistence.PersistentEntity$PersistException: Persist of [akka.persistence.journal.Tagged] failed in […ProvisionalBookingEntity] with id [790B7CC207A1000], caused by: {Circuit Breaker Timed out.

=======================================================================

conf file configurations : -

cassandra.default {
contact-points = [“192.168.25.3”, “192.168.25.4”, “192.168.25.5”]
session-provider = akka.persistence.cassandra.ConfigSessionProvider
}

cassandra-journal {
contact-points = {cassandra.default.contact-points} session-provider = {cassandra.default.session-provider}
}

cassandra-snapshot-store {
contact-points = {cassandra.default.contact-points} session-provider = {cassandra.default.session-provider}
}

lagom.persistence.read-side.cassandra {
contact-points = {cassandra.default.contact-points} session-provider = {cassandra.default.session-provider}
write-consistency = “QUORUM”
read-consistency = “QUORUM”
replication-strategy = “SimpleStrategy”
replication-factor = 3
max-result-size = 50001
reconnect-max-delay = 30s
keyspace-autocreate = true
}

akka.cluster.sharding.state-store-mode = ddata

akka.remote.artery.enabled = on

akka.remote.artery.canonical.port = 2551

akka.cluster.seed-nodes = [“akka://application@192.168.23.4:2551”]

akka.extensions=[“akka.cluster.metrics.ClusterMetricsExtension”]

akka.cluster.metrics.native-library-extract-folder= ${user.dir}/target/native

akka.cluster.downing-provider-class = “…”

akka.cluster.min-nr-of-members = ${akka.reasonable.downing.quorum-size}

akka.reasonable.downing.stable-after = 3 seconds

akka.reasonable.downing.quorum-size = 2

akka.cluster.roles = [“booking”]

akka.reasonable.downing.quorum-roles = [“booking”]

akka.cluster.sharding.role=“booking”

akka.cluster.singleton.role = “booking”



(Tim Moore) #2

That looks like a time out when trying to write to the database. Double check the database configuration. There might be some additional details elsewhere in the service logs, or in the database logs.