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

Anu Engineer commented on HDDS-25:
----------------------------------

[~elek] Thanks for posting the draft. It looks good to me. some questions.

 
 # Nit: The {{EventExecutor Interface}} some functions have the comments 
swapped. You might want to fix them later.
 # {EventPublisher#fireEvent }-- ? Does it have an error interface ? or should 
we use exceptions ? 
 # Do we need a executor per event type ? or just have a thread  pool ?
 # Suppose, I have to get a respose for an Event that I have queued, does it 
make sense to support a future interface – or is that mute ? Should we have an 
Event ID – for the same purpose if we want to indicate this is in response to 
that command.

[~msingh], [~nandakumar131] Please share your thoughts too.

 

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