[
https://issues.apache.org/jira/browse/HBASE-30492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18134233#comment-18134233
]
Hudson commented on HBASE-30492:
--------------------------------
Results for branch master
[build #210 on
builds.a.o|https://ci-hbase.apache.org/job/HBase-Integration-Test/job/master/210/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.5 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.3.6 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.0 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.1 {color}
(/) {color:green}+1 client integration test for 3.4.1 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.2 {color}
(/) {color:green}+1 client integration test for 3.4.2 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.3 {color}
(/) {color:green}+1 client integration test for 3.4.3 with shaded hadoop
client{color}
> BucketCachePersister ignores dynamic persistence interval changes
> -----------------------------------------------------------------
>
> Key: HBASE-30492
> URL: https://issues.apache.org/jira/browse/HBASE-30492
> Project: HBase
> Issue Type: Bug
> Components: BucketCache
> Reporter: Xiao Liu
> Assignee: Xiao Liu
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1, 2.7.0, 3.1.0, 3.0.1, 2.6.8
>
>
> HBASE-29249 documents \{{hbase.bucketcache.persist.intervalinmillis}} as
> dynamically configurable. However, \{{BucketCachePersister}} keeps using the
> interval captured at construction, even after the configuration is updated.
> The persister should use the updated interval for subsequent waits.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
