[
https://issues.apache.org/jira/browse/HDDS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594066#comment-16594066
]
Anu Engineer commented on HDDS-359:
-----------------------------------
[~elek] Thanks for the comments. Patch v5 addresses all comments.
{quote}Would be great to get some log output about initializing the
table/columnfamiliy with a specific file/profile
{quote}
Done DbStoreBuilder will write all that information to Log at info level now.
{quote} I would use HddsConfigKeys instead of OzoneConfigKeys. The
functionality is part of the core hdds and long term we need to separated the
ozone specific and hdds specific configuration
{quote}
Very good catch. Thanks for noticing that issue. I have moved the key to a
better location. Please take a look at patch v5 when you get a chance.
> RocksDB Profiles support
> ------------------------
>
> Key: HDDS-359
> URL: https://issues.apache.org/jira/browse/HDDS-359
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Xiaoyu Yao
> Assignee: Anu Engineer
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-359.001.patch, HDDS-359.002.patch,
> HDDS-359.003.patch, HDDS-359.004.patch, HDDS-359.005.patch
>
>
> This allows us to tune the OM/SCM DB for different machine configurations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
