My team is in pre-production and were chasing some odd behaviors that we believe are contributing to stability issues with our application and our Cassandra cluster.
First some environment information: Akka version - 2.4.11 Cassandra Version - 3.3 - 3 node Cassandra in 2 DC Now based on my understanding of Akka persistence in a health system I'd expect my writes to far outpace my reads in the journal since the persistent actor should only execute a journal read on creation to see if there is any journal to playback. After my actor receives RecoverCompleted I'd expect no more reads and for writes to dominate my journal transactions. Based on our datadog graphs we're seeing our reads being constant and often outpacing our writes. I also encountered similar behavior when I did a simple test with the DynamoDB journal plugin. I provisioned 15 for both reads and writes per second. When I ran my simple developer test I looked at my cloudwatch graphs and saw my reads exceeded provisioned readers but the writes were within expected parameters. So am I missing something in the Akka infrastructure that is constantly reading from the journal table? Regards, Richard -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
