[jira] [Commented] (HDDS-3354) OM HA replay optimization

["Marton Elek (Jira)" <ji...@apache.org>]

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

Marton Elek commented on HDDS-3354:
-----------------------------------

Thanks to wok on this Bharat, I have a few questions to understand the problem:

 1. What is the performance impact of turning on sync of write. It seems that we make the restart faster but making the production run slower. Is it true? Do you have numbers of the additional cost of the sync write?

 2. It's not clear the structure of the new table. You wrote "For this, we can have a new table in rocks db with key as timestamp and value as largest transaction index in that batch flush to DB." But you mentioned a String->long table. And in the document you mentioned that only one key will be used. What will be the content of the table? 




> OM HA replay optimization
> -------------------------
>
>                 Key: HDDS-3354
>                 URL: https://issues.apache.org/jira/browse/HDDS-3354
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>         Attachments: OM HA Replay.pdf
>
>
> This Jira is to improve the OM HA replay scenario.
> Attached the design document which discusses about the proposal and issue in detail.



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