Has anyone decided to split their Persistent actors so they write to separate Cassandra tables for journal message?
We tried to split the journal messages into separate tables to prevent overloading one table. But it appears that while the actors journal to the separate tables when the actor is recovered and CassandraReadJournal.eventsByPersistentId is called I look at the queries the table referenced isn't the split table, it's using the same table that the cluster uses for messages which is the first instance of the Cassandra plug in created. Anyone else seen this behavior when providing separate journal plug settings for different actor types? 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.
