[
https://issues.apache.org/jira/browse/HDDS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472503#comment-16472503
]
Hudson commented on HDDS-25:
----------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14175 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14175/])
HDDS-25. Simple async event processing for SCM. Contributed by Elek,
(aengineer: rev ba12e8805e2ae6f125042bfb1d6b3cfc10faf9ed)
* (add)
hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/server/events/SingleThreadExecutor.java
* (add)
hadoop-hdds/framework/src/test/java/org/apache/hadoop/hdds/server/events/TestEventQueueChain.java
* (add)
hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/server/events/TypedEvent.java
* (add)
hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/server/events/EventQueue.java
* (add)
hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/server/events/package-info.java
* (add)
hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/server/events/Event.java
* (add)
hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/server/events/EventPublisher.java
* (add)
hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/server/events/EventHandler.java
* (add)
hadoop-hdds/framework/src/test/java/org/apache/hadoop/hdds/server/events/TestEventQueue.java
* (add)
hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/server/events/EventExecutor.java
> 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]
