[
https://issues.apache.org/jira/browse/HBASE-22836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905810#comment-16905810
]
HBase QA commented on HBASE-22836:
----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s{color}
| {color:red} HBASE-22836 does not apply to master. Rebase required? Wrong
Branch? See
https://yetus.apache.org/documentation/in-progress/precommit-patchnames for
help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-22836 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12977439/HBASE-22836.branch1.0001.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/763/console |
| Powered by | Apache Yetus 0.9.0 http://yetus.apache.org |
This message was automatically generated.
> MemcachedBlockCache parameter error
> -----------------------------------
>
> Key: HBASE-22836
> URL: https://issues.apache.org/jira/browse/HBASE-22836
> Project: HBase
> Issue Type: Bug
> Components: BlockCache
> Affects Versions: 1.4.9, 1.4.10
> Reporter: Zhao
> Priority: Major
> Attachments: HBASE-22836.branch1.0001.patch
>
>
> When cache a blockļ¼the expiration is always set MAX_SIZE (which is a static
> final field).
> MAX_SIZE was mistakenly thought to be the max size of block. In fact, this
> parameter represents the expiration of the cached block. MAX_SIZE should be
> set 0 which means forever.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
