You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2020/04/27 17:22:04 UTC

[GitHub] [hadoop-ozone] bharatviswa504 commented on pull request #855: HDDS-3474. Create transactionInfo Table in OmMetadataManager.

bharatviswa504 commented on pull request #855:
URL: https://github.com/apache/hadoop-ozone/pull/855#issuecomment-620121969


   > Thanks @bharatviswa504 to work on this. I am trying to understand the problem to help with the code review but still not clear the proposal. I added my comments to the parent JIRA.
   > 
   > Especially as this patch introduced `String`->`String` table.
   > 
   > It's also not clear the performance degradation caused by this problem. Can you please help me to understand?
   
   For the questions posted in jira, replied over there.
   
   The main intention of this Jira is
   1. Avoid additional DB looks up, which impact perf. One such jira. HDDS-3129
    2. To not handle replay code in actual request execution which was done in previous jiras. This has caused additional complexity in the code.
   3. Optimize restart time.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org