Dear group

I am quite new to Akka persistence, and very new to Cassandra. The 
combination is working fine, however, except one problem: Mass deletions 
and compaction.

It seems, if I understood Cassandra correctly, that my usage is an 
anti-pattern (*). I have actors that read a lot of messages, and persist a 
hash of them (for duplicate detection). Every hour I take a snapshot, and 
deletes old messages. It is about 20'000 messages each hour (for each 
actor, does not seem much to me). But I guess this way of using Akka 
Persistence is quite typical?

After a while, the deletes start to time out, and compaction is taking a 
really long time.

As I understood it, DTCS (Date-Tiered Compaction Strategy) (+) should be 
more suited, since data is inserted in order, and deleted from the end.

Is this correct? Has any of you problems with compactions, done some 
testing etc? Any experience on the matter?

Best regards,

Anders Båtstrand

Links:

* 
http://www.datastax.com/dev/blog/cassandra-anti-patterns-queues-and-queue-like-datasets
+ http://www.datastax.com/dev/blog/datetieredcompactionstrategy

-- 
>>>>>>>>>>      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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to