You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Amitanand Aiyer (JIRA)" <ji...@apache.org> on 2011/09/07 21:01:09 UTC
[jira] [Commented] (HBASE-4346) Optimise the storage that we use
for storing MVCC information.
[ https://issues.apache.org/jira/browse/HBASE-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099215#comment-13099215 ]
Amitanand Aiyer commented on HBASE-4346:
----------------------------------------
This task is a nice-to-have. Not really required for addressing the "correctness" issue with 2856.
Will work on this as the next step. Putting a place holder here.
> Optimise the storage that we use for storing MVCC information.
> --------------------------------------------------------------
>
> Key: HBASE-4346
> URL: https://issues.apache.org/jira/browse/HBASE-4346
> Project: HBase
> Issue Type: Sub-task
> Environment: Writing the memstoreTS information is critical to ensuring Atomic semantics. However, it adds a storage overhead to the disk files.
> This information is useful only when there is a "concurrent" read operation that needs to ignore a particular key-value.
> Once it is known that a key-value is going to be included in all current and future read operations, MVCC memstoreTS information is
> of no use anymore.
> We can optimize for storage on disk, by getting rid of these values during later compactions.
> Reporter: Amitanand Aiyer
> Priority: Minor
> Fix For: 0.94.0
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira