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

Hudson commented on HDDS-191:
-----------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14477 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/14477/])
HDDS-191. Queue SCMCommands via EventQueue in SCM. Contributed by Elek, 
(aengineer: rev a55d6bba71c81c1c4e9d8cd11f55c78f10a548b0)
* (edit) 
hadoop-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/node/TestNodeManager.java
* (add) 
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/protocol/commands/CommandForDatanode.java
* (edit) 
hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/server/StorageContainerManager.java
* (edit) 
hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/node/SCMNodeManager.java


> Queue SCMCommands via EventQueue in SCM
> ---------------------------------------
>
>                 Key: HDDS-191
>                 URL: https://issues.apache.org/jira/browse/HDDS-191
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>             Fix For: 0.2.1
>
>         Attachments: HDDS-191.001.patch, HDDS-191.002.patch
>
>
> As a first step towards to a ReplicationManager I propose to introduce the 
> EventQueue to the StorageContainerManager and enable to send SCMCommands via 
> EventQueue.
> With this separation the ReplicationManager could easily send the appropriate 
> SCMCommand (eg. CopyContainer) to the EventQueue without hard dependency to 
> the SCMNodeManager. (And later we can introduce the CommandWatchers without 
> modifying the ReplicationManager part)



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