[
https://issues.apache.org/jira/browse/HDDS-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110342#comment-17110342
]
Marton Elek commented on HDDS-3354:
-----------------------------------
Thanks to explain, and also thanks the offline updates about this plan. It was
not clear for me why was it decided to solve the problem in this way (there are
1-2 other ways to do the same, which was not mentioned as considered
alternatives. For example: use RocksDB checkpoints and snapshot db together
with Ratis log. Or keep the list of the active keys always in the memory and
store only the values in the database.)
But I am fine with this approach, unless it causes significant performance
degradation. And If I understood well this is the case: it introduce some new
IO pressure but also removes a lot of unnecessary queries which can make the
overall picture even better than before.
As I know, you have some initial numbers about the performance. I would propose
to share the here.
Thanks again to explain it to me offline, multiple times.
> 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: [email protected]
For additional commands, e-mail: [email protected]
