[ 
https://issues.apache.org/jira/browse/HDDS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472012#comment-16472012
 ] 

Elek, Marton commented on HDDS-25:
----------------------------------

Thanks a lot [~shashikant] to check the comments. I fixed the comments in tthe 
last patch.

Regarding the tracing: Yes, it's a good question. I think some kind of timeout 
could be added to the EventExecutor if needed and it could be transparent to 
the EventHandlers. But the promise of the Actor based architecture is that you 
can't create a deadlock. If there is no Future and every actor (=handler) has 
an own threadpool/mailbox, it's very hard to do a deadlock. Even we don't need 
synchronization in the EventHandlers if the EventExecutor could guarantee that 
every handler will be executed only on one thread. 

> Simple async event processing for SCM
> -------------------------------------
>
>                 Key: HDDS-25
>                 URL: https://issues.apache.org/jira/browse/HDDS-25
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: SCM
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>             Fix For: 0.2.1
>
>         Attachments: HDDS-25.001.patch, HDDS-25.003.patch, HDDS-25.004.patch, 
> HDDS-25.005.patch
>
>
> For implementing all the SCM status changes we need a simple async event 
> processing. 
> Our use-case is very similar to an actor based system: we would like to 
> communicate with full asny event/messages, process the different events on 
> different threads, ...
> But a full Actor framework (such as Akka) would be overkill for this use 
> case. We don't need distributed actor systems, actor hierarchy or complex 
> resiliency.
> As a first approach we can use a very simple system where a common EventQueue 
> entry point could route events to the async event handlers



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to