You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (Jira)" <ji...@apache.org> on 2020/05/13 18:13:00 UTC

[jira] [Comment Edited] (HBASE-24365) MetricsTableWrapperAggregateImpl runnable fails due to exception and never runs

    [ https://issues.apache.org/jira/browse/HBASE-24365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17106369#comment-17106369 ] 

ramkrishna.s.vasudevan edited comment on HBASE-24365 at 5/13/20, 6:12 PM:
--------------------------------------------------------------------------

So no new tables or data is updated except for the values that comes out of MetricsTableSourceImpl and this starts happening after the first flush happens for that table. Though this happens, the periodically updating values from the MetricsTableWrapperAggregateImpl  never happens hence it was not seen all these days that it was failing.


was (Author: ram_krish):
So no new tables or data is updated except for the values that comes out of MetricsTableSourceImpl and this start happening after the first flush happens for that table. Though this happens the periodically updating values from the MetricsTableWrapperAggregateImpl  never happens hence it was not seen all these days.

> MetricsTableWrapperAggregateImpl runnable fails due to exception and never runs
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-24365
>                 URL: https://issues.apache.org/jira/browse/HBASE-24365
>             Project: HBase
>          Issue Type: Bug
>          Components: metrics
>    Affects Versions: 3.0.0-alpha-1, 2.1.9, 2.2.4
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Minor
>
> MetricsTableWrapperAggregateImpl has a thread that periodically updates the values.
> It seems that once the region server is online and the meta is assigned if there are no store files the Optional values  here
> {code}
>             mt.maxStoreFileAge = Math.max(mt.maxStoreFileAge, store.getMaxStoreFileAge().getAsLong());
>             mt.minStoreFileAge = Math.min(mt.minStoreFileAge, store.getMinStoreFileAge().getAsLong());
> {code}
> is not available and thus throwing NoSuchElementException and the thread dies. It never updates the values till the RS is alive. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)