[akka-user] Akka Persistence Cassandra Plugin - Tombstone handling

Hi, In context of Cassandra plugin, I have following queries 1) As I understand, as consequence of snaphotting, there would be implicit pruning of entries in journal - is this correct ? 2) If yes, then we are facing typical Cassandra tombstones pruned entries - now, before the tombstones

Re: [akka-user] Re: Seed nodes behavior in 3 node scenario in version 2.5.0

consider using the partition info to take actions like isolation of nodes We are using Opendaylight RAFT consensus cluster built atop Akka. Regards Muthu On Tuesday, 5 December 2017 22:35:05 UTC+5:30, Patrik Nordwall wrote: > > > > On Mon, Dec 4, 2017 at 5:32 PM, Muthukumaran K

[akka-user] Re: Seed nodes behavior in 3 node scenario in version 2.5.0

December 2017 14:34:15 UTC+5:30, Muthukumaran Kothandaraman wrote: > > Hi, > > I am trying to validate below statements in Akka Docs with slight twist in > the scenario. After first seed node is brought down and before restarting > the first seed-node, I try to restart anot

[akka-user] Seed nodes behavior in 3 node scenario in version 2.5.0

Hi, I am trying to validate below statements in Akka Docs with slight twist in the scenario. After first seed node is brought down and before restarting the first seed-node, I try to restart another surviving node of cluster "*When a new node is started it sends a message to all seed nodes

[akka-user] Basic Troubleshooting of AskTimeoutException in local and remote contexts

Hi, I am using a relatively large codebase ( distributed Raft protocol Stack and Datastore built atop basic Akka clustering) which uses Ask pattern for some of the key messages exchanged across the nodes . We frequently hit AskTimeout Exceptions (typically we have 3 ms timeout)

[akka-user] Re: Full network partition and healing in combination with auto-down disabled

Tested with 2.4.7 (well, I am constrained to use that version). Works correctly as expected. Thanks Muthu -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the

[akka-user] DistributedPubSub sending messages to DeadLetter

If the behavior has to avoid deadletter when there are no subscribers, we are mainly talking about 'store and forward' behavior. Now, that paradigm brings additional requirements like persistence of messages, managing topic wise messages in distributed manner, resultant consistency needs etc.

[akka-user] Re: Full network partition and healing in combination with auto-down disabled

ough... It's not an "official" answer) > > Tal > > > On Monday, July 17, 2017 at 10:29:36 AM UTC+3, Muthukumaran Kothandaraman > wrote: >> >> Hi, >> >> I searched around the mailing list and forums for my specific >> clarifications. I got

[akka-user] Full network partition and healing in combination with auto-down disabled

Hi, I searched around the mailing list and forums for my specific clarifications. I got partial answers via below discussion https://groups.google.com/forum/#!searchin/akka-user/network$20partition$20auto$20down|sort:relevance/akka-user/9SR1vyVqChM/619tpI2XAAAJ But, in my case, its a full

[akka-user] Re: Supervision for persistent actors

not a good idea to have mixed strategies among siblings correct ? Regards Muthu On Thursday, 22 June 2017 10:53:40 UTC+5:30, Muthukumaran Kothandaraman wrote: > > Hi, > > *Context* : I have a hierarchy wherein a parent (few levels below root) > is a persistent-actor (let us call

[akka-user] Supervision for persistent actors

Hi, *Context* : I have a hierarchy wherein a parent (few levels below root) is a persistent-actor (let us call this as partition-manager (this Id is ensured to be unique). It starts few child actors which are again persistent (let us call them as partition-handler-X where X is some unique

[akka-user] Any form of first-try / first-peek at Artery Akka remoting ?

Hi, Is Artery still a work in progress or any snapshots are available for trying out ? Regards Muthu -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archives:

[akka-user] Re: Cluster actors an parallelism

Hi Cosmin, Are these what you are looking for http://doc.akka.io/docs/akka/snapshot/scala/routing.html#ConsistentHashingPool_and_ConsistentHashingGroup OR http://doc.akka.io/docs/akka/snapshot/scala/routing.html#BroadcastPool_and_BroadcastGroup Regards Muthu On Thursday, 25 August 2016

[akka-user] Re: Consistent Hashing Group and routee death-watch / recreation

ext().watch(r); router = router.addRoutee(new ActorRefRoutee(r)); } Regards Muthu On Monday, 15 August 2016 18:04:14 UTC+5:30, Muthukumaran Kothandaraman wrote: > > Hi, > > I am using akka 2.4.8 and creating CH Group as following (with my custom > HashMapper) >

Re: [akka-user] Hot Standby Persistent Actor - https://github.com/akka/akka/issues/13938

e for community contibution. Queries are there > now. > > /Patrik > ons 10 aug. 2016 kl. 07:04 skrev Muthukumaran Kothandaraman < > muthu@gmail.com >: > >> Hi, >> >> Is this still targeted for 2.5 or it has moved further ? As I understand, >&g

[akka-user] Consistent Hashing Group and routee death-watch / recreation

Hi, I am using akka 2.4.8 and creating CH Group as following (with my custom HashMapper) Set actorPaths = new HashSet(); for (int i=0;i

[akka-user] Hot Standby Persistent Actor - https://github.com/akka/akka/issues/13938

Hi, Is this still targeted for 2.5 or it has moved further ? As I understand, this required some query-side improvements before this could be addressed. Regards Muthu -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >>

[akka-user] Re: Cassandra persistence with Kryo-serialization - recovery and persistence performance issue

Thanks for detailed explanation Justin. The main objective of my exercise is to bechmark performance of Kryo + Cassandra-persistence combination for my event objects without any complex inheritance structure. In my case, types of message types are pretty much limited - max - 5 types. Would

[akka-user] Cassandra persistence with Kryo-serialization - recovery and persistence performance issue

Hi, I am using following combination for a basic persistence actor Version combination : Cassandra 3.7 + akka-persistence-cassandra-0.7 + akka 2.4.8 + akka-kryo-serialization_2.11 version-0.4.1 I am using following conf to serialize using kryo-serialization kryo { type = "graph"

[akka-user] Re: Cassandra persistence - with Cassandra 2.2.7 + akka-persistence-cassandra-0.7 + akka 2.4.8 - not working

Just to unblock myself I had moved ahead with Cassandra 3.7. I do have some constraints in not moving to 3.x yet and have to stick to 2.x for an upcoming work. Will definitely try out the compat flag. Regards Muthu -- >> Read the docs: http://akka.io/docs/ >>

[akka-user] Re: Cassandra persistence - with Cassandra 2.2.7 + akka-persistence-cassandra-0.7 + akka 2.4.8 - not working [SOLVED]

, Muthukumaran Kothandaraman wrote: > > Hi, > > With above combination I am getting following error while running a simple > PersistentActor. Checked compatibility on page - > https://github.com/akka/akka-persistence-cassandra > > Will give a try with > > >

[akka-user] Cassandra persistence - with Cassandra 2.2.7 + akka-persistence-cassandra-0.7 + akka 2.4.8 - not working

Hi, With above combination I am getting following error while running a simple PersistentActor. Checked compatibility on page - https://github.com/akka/akka-persistence-cassandra Will give a try with [WARN] [07/30/2016 08:13:20.699] [example-cassandra-journal.default-dispatcher-6]

[akka-user] Cassandra journal persistence - query on parallelism across persistenceIds

Hi, I would like to understand the possible degree of parallelism in Cassandra persistence plugin with Cassandra 3.4.0. For my usecase, I would be having around 3K distinct peristent actors using event-sourced pattern with Akka 2.4.1. I am not using any other capabilities like sharding. But

Re: [akka-user] Akka persistence - compatibility of file-persistence journals and snapshots

with default persistence using LevelDB Anyway, I will test this and provide the full verification details Regards Muthu On Tuesday, 22 September 2015 13:13:17 UTC+5:30, Patrik Nordwall wrote: > > > > On Fri, Sep 18, 2015 at 11:59 AM, Muthukumaran Kothandaraman < > muthu

[akka-user] Akka persistence - compatibility of file-persistence journals and snapshots

Following are the aspects of my usage - Using same app code which uses same akka version and its dependencies on more than 1 node - All nodes are symmetric and use their individual disks to persist their own snapshots and journals (default LevelDB persistence is used) Query - When I add a

Re: [akka-user] Re: Send message from netty code to actor system

Few things to take care of using a router at InboundHandler - ensuring that routees are available before the connections are being accepted - ensuring that ChannelContextHandler - passed in message, is not stored by routee actor internally for any purposes. This should be sufficient for pure

Re: [akka-user] Customizing failure-zones in distributed publish subscribe

, 2015 at 7:00 AM, Muthukumaran Kothandaraman muthu@gmail.com javascript: wrote: I have following requirements for designing a clusterwide messaging system 1. There can be many to many relationship between topics and subscribers. ie. one module (OSGi) in each cluster node can subscribe

[akka-user] Customizing failure-zones in distributed publish subscribe

I have following requirements for designing a clusterwide messaging system 1. There can be many to many relationship between topics and subscribers. ie. one module (OSGi) in each cluster node can subscribe to more than one topic and each topic can be subscribed to by more than one module. So,

[akka-user] Creating regular actors and lookup (actorselection) actors with specific role

As I understand ActorSystem : (is to) Role is *1:MANY* cardinality - this I infer from confg injected into ActorSystem during the startup. Does that mean that I can create multiple actors with multiple roles within same actorsystem ? For instance, can I - start up an ActorSystem - AS1 and

Re: [akka-user] Bind exception with multiple Akka cluster nodes on same machine

multiple nodes on port 1551 next to the nodes with changed port. Do you change remote.netty.tcp.port in code? Check if you do not start ActorSystem before the change. On Sat, Oct 4, 2014 at 10:53 PM, Muthukumaran Kothandaraman muthu@gmail.com javascript: wrote: Hi, I am starting a 3

[akka-user] Separate ports for Cluster Mgmt messages and Application Messages

Hi, Is it possible to isolate the cluster management messages (such as Member messages and other system-level messages) could be configured to use a separate port for application messages (messages defined by user-apps) through configuration ? In-banding and out-of-band system messaging

[akka-user] Bind exception with multiple Akka cluster nodes on same machine

Hi, I am starting a 3 node cluster on same machine with following conf (one copy each for 3 nodes with changed netty.tcp.port values. *Though I see the exception pasted below during startup, Cluster actually comes up and I am able to see all nodes via JMX and all other cluster-listener