You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2020/06/01 00:55:00 UTC
[jira] [Commented] (HDDS-118) Introduce datanode container command
dispatcher to syncronize various datanode commands
[ https://issues.apache.org/jira/browse/HDDS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120664#comment-17120664 ]
Arpit Agarwal commented on HDDS-118:
------------------------------------
[~msingh] do we still need this?
> Introduce datanode container command dispatcher to syncronize various datanode commands
> ---------------------------------------------------------------------------------------
>
> Key: HDDS-118
> URL: https://issues.apache.org/jira/browse/HDDS-118
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode
> Affects Versions: 0.2.1
> Reporter: Mukul Kumar Singh
> Assignee: Mukul Kumar Singh
> Priority: Major
>
> ContainerStateMachine provides mechanism to synchronize various container command operations. However with multiple protocol endpoints like. 1) Netty, 2) Grpc, 3) Ratis, 4) Heartbeat. It will be advisable to synchronize operations between multiple endpoints.
> This jira proposes to introduce a single command executor to which the protocol endpoints will enqueue the command for execution. All the synchronization can be enforced by this executor therefore.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org