On Wed, Jan 7, 2015 at 6:32 AM, Muthukumaran Kothandaraman <
muthu.kmk2...@gmail.com> wrote:

> Thanks Patrik.
>
> By failure-zones, I mean to assign different dispatchers to different
> combinations of topic + subscribers.
>
> For example, Subscriber A and Subscriber B both handle messages from topic
> C and hence there would be two subscribers - actor sub_a_topic_c and actor
> sub_b_topic_c (I choose a convention to name actors with the combination to
> distinguish different subscribers for same topic).
>
> In above example, I could assign different dispatchers - one each  for two
> subscribers based on latencies of message-handling by subscribers, so that
> processing latencies by one actor does not affect the other for same topic.
> Is this approach fine in above context ?
>
>
Sounds good.


> Of course the decision to separate dispatchers would be taken only after
> thorough measurement of latencies
>
>
> - Muthu
>
>
>
> On Tuesday, 6 January 2015 20:31:54 UTC+5:30, Patrik Nordwall wrote:
>>
>> Hi Muthu,
>>
>> On Mon, Jan 5, 2015 at 7:00 AM, Muthukumaran Kothandaraman <
>> muthu....@gmail.com> 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 to
>>> more than one topic and each topic can be subscribed to by more than one
>>> module. So, I have created one subscriber actor per-module per-topic
>>> combination to avoid issues like head-of-line-blocking and to fairly
>>> distribute the processing across multiple actors
>>>
>>> 2. Subscriber actors likely to invoke some legacy code which may not be
>>> very finely tuned for latency and hence there could be different
>>> processing-latencies for the same message of same topic by different modules
>>>
>>> 3. Publish is invoked directly in the caller thread where message
>>> originates (ie. from within existing code which is not actor-based). Since
>>> 'tell' to mediator is non-blocking, I am assuming that this should be fine
>>> (pls correct me if I am making any wrong assumptions here)
>>>
>>
>> Yes, that is fine
>>
>>
>>>
>>> My topics-module combinations lead to upto max 100 actors running in
>>> each node of cluster.
>>>
>>> My thoughts on creating failure zone is now limited to only the
>>> subscribers part because I create only subscriber actors and publishing
>>> entirely happens in caller-thread.
>>> So, what are possible ways to create failure-zones
>>> a.  topic-wise and
>>> b. topic+subscriber combinationwise (somehow, this appears to be a more
>>> complex part)
>>>
>>
>> What do you mean by failure-zones? What do you want to achieve or protect
>> against?
>>
>> Regards,
>> Patrik
>>
>>
>>>
>>> Any experiences and/or recommendations ?
>>>
>>> Thanks in advance
>>>
>>> - Muthu
>>>
>>> --
>>> >>>>>>>>>> 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+...@googlegroups.com.
>>> To post to this group, send email to akka...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/akka-user.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>>
>> Patrik Nordwall
>> Typesafe <http://typesafe.com/> -  Reactive apps on the JVM
>> Twitter: @patriknw
>>
>>   --
> >>>>>>>>>> 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.
>



-- 

Patrik Nordwall
Typesafe <http://typesafe.com/> -  Reactive apps on the JVM
Twitter: @patriknw

-- 
>>>>>>>>>>      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