[
https://issues.apache.org/jira/browse/HDDS-11415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904367#comment-17904367
]
Ivan Andika commented on HDDS-11415:
------------------------------------
[~ritesh] Thank you. Will take a look.
cc: [~Symious] [~XiChen] [~ferhui]
> Leader Execution at Leader
> --------------------------
>
> Key: HDDS-11415
> URL: https://issues.apache.org/jira/browse/HDDS-11415
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Sumit Agrawal
> Assignee: Sumit Agrawal
> Priority: Major
>
> Leader execution at leader provides various control capability and
> performance improvement and handling other challenges as faced. Few of
> problem focused to resolve:
> # Only execution at leader reduces {*}failure scenarios{*}, due to
> environment impacts like security token expiry, logic issues failure.
> Response is quick.
> # *Parallel execution* of request in controlled manner is possible
> (performance / throughput can be improved)
> # *Batching of DB updates* (as request handling output) will improve the
> number of Raft logs synch to all nodes.
> # Some code complexity as induced via *DoubleBuffer* can be reduced by
> handling transaction Index update.
> # Many code having *cache handling* is very complex and keeps on reporting
> issues for cache over various operations, and new issues keep induced with
> new features.
> # Ranger can be offloaded by 2/3 times, as Ranger authentication will happen
> only on leader node. This will help further improvement of performance in
> end-to-end scenarios.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
