[
https://issues.apache.org/jira/browse/HDDS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470311#comment-16470311
]
Elek, Marton commented on HDDS-25:
----------------------------------
Thanks [~msingh] and [~anu] the review. I fixed the issue (flipped javadoc,
package name, unused imports, missing licence, wildcard import, + a few small
fixes suggested by intellij like using final when possible)
[~msingh]: I don't know how an eventId could be used. Please share if you have
suggestion. My only idea is to use an implicit tracking with
https://opencensus.io/ or http://opentracing.io/. If a thread local tracing ID
is not avaiable: generate it and propagate it in eventqueue over the different
thread pools. But (IMHO) it could be done in diferent Jira.
> 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-HDDS-25.002.patch, 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]
