[
https://issues.apache.org/jira/browse/HBASE-19806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347002#comment-16347002
]
Anoop Sam John commented on HBASE-19806:
----------------------------------------
Sorry Ted, I did not get fully.. The versions are kept as configured in each
CF. Its CF specific data maintain. There is no concept of corresponding data in
other CFs. Ya when configured value is more than 10, these missing CFs still
have hard coded versions as 10 and so we may have lesser versions been kept.
But chances? IMHO very less.. Then about maintaining more data, ya it depends
on how many times the table state changes. So even if we keep more data for
this CF (more abt the state transitions) , the other CF data not affected by
that. Good that we fixed this. No doubt for me.
> Lower max versions for table column family of hbase:meta
> --------------------------------------------------------
>
> Key: HBASE-19806
> URL: https://issues.apache.org/jira/browse/HBASE-19806
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Trivial
> Fix For: 2.0.0-beta-2
>
> Attachments: 19806.v1.txt, lower-namespace-max-vers.txt
>
>
> On an hbase 2 cluster, I got the description of hbase:meta table:
> {code}
> {NAME => 'info', VERSIONS => '3', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS => 'FALSE',
> CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL =>
> 'FOREVER', MIN_VERSIONS => '0',
> REPLICATION_SCOPE => '0', BLOOMFILTER => 'NONE', CACHE_INDEX_ON_WRITE =>
> 'false', IN_MEMORY => 'true', CACHE_BLOOMS_ON_WRITE => 'false',
> PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '81
> 92'}
> ...
> {NAME => 'table', VERSIONS => '10', EVICT_BLOCKS_ON_CLOSE => 'false',
> NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS => 'FALSE',
> CACHE_DATA_ON_WRITE => 'false', DATA_BLOCK_ENCODING => 'NONE', TTL =>
> 'FOREVER', MIN_VERSIONS => '0'
> , REPLICATION_SCOPE => '0', BLOOMFILTER => 'NONE', CACHE_INDEX_ON_WRITE =>
> 'false', IN_MEMORY => 'true', CACHE_BLOOMS_ON_WRITE => 'false',
> PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE =>
> 'true', BLOCKSIZE => '
> 8192'}
> {code}
> You can see that 'table' family has MAX VERSIONS much higher than the other
> families.
> The MAX VERSIONS value should be brought in sync with the other families.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
