[jira] [Commented] (PHOENIX-4334) Unable to update stats on views that reside on separate regions before phoenix.stats.updateFrequency has elapsed

["Samarth Jain (JIRA)" <ji...@apache.org>]

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

Samarth Jain commented on PHOENIX-4334:
---------------------------------------

We store last_update_time at the physical table level. So if we end up collecting stats for view1, then we will have to wait for phoenix.stats.updateFrequency before update stats on view2 has any effect. An alternative would be set phoenix.stats.updateFrequency to 0. 

I will take a look at why view2 is reporting estimate time as current time.

> Unable to update stats on views that reside on separate regions before phoenix.stats.updateFrequency has elapsed
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4334
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4334
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.12.0
>            Reporter: Mujtaba Chohan
>            Assignee: Samarth Jain
>
> Consider multiple tenant views that all reside on unique region/region servers. Updating stats on any one of the view causes other views to report estimated stats last update time as current resulting in stats command getting ignored for other views till {{phoenix.stats.updateFrequency}} has elapsed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)