[
https://issues.apache.org/jira/browse/HDDS-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505024#comment-16505024
]
Bharat Viswanadham edited comment on HDDS-133 at 6/7/18 6:10 PM:
-----------------------------------------------------------------
Hi [~xyao]
Yaml is mainly chosen for making the container files in human readable format.
And also it will help during debugging, where we can directly read the
.container files.
And also profiling is done, to figure out the time to read .container files and
build container map. With cold start (clearing cache, inode entries) to read
50,000 containers, it has taken around 35 seconds. With warm start(cache is not
cleared), it has taken around 5 seconds.
was (Author: bharatviswa):
Hi [~xyao]
Yaml is mainly chosen for making the container files in human readable format.
And also it will help during debugging, where I can directly read the
.container files.
And also profiling is done, to figure out the time to read .container files and
build container map. With cold start (clearing cache, inode entries) to read
50,000 containers, it has taken around 35 seconds. With warm start(cache is not
cleared), it has taken around 5 seconds.
> Change format of .container files to Yaml
> -----------------------------------------
>
> Key: HDDS-133
> URL: https://issues.apache.org/jira/browse/HDDS-133
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-133-HDDS-48.00.patch, HDDS-133-HDDS-48.01.patch
>
>
> This Jira changes .container file format to yaml.
> Following fields are serialized into .container file:
> containerType, containerId, layOutVersion, state, metadata, dbPath,
> containerFilePath, containerDBType
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
