[
https://issues.apache.org/jira/browse/HDDS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468694#comment-16468694
]
Mukul Kumar Singh commented on HDDS-25:
---------------------------------------
Thanks for the patch [~elek]. The process looks good to me.
1) the package name is *org.apache.hadoop.hdds.server.org.apache.hdds.events* I
feel this should be changed to *org.apache.hadoop.hdds.server.events*
2) EventExecutor.java:20, unused import
3) EventQueue.java is missing ASF license header.
4) EventQueue.java:8, Please expand the import to include specific packages.
Also for the question discussed earlier I feel a fireEvent should return an
eventID so that a particular event can be tracked.
> 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]
