[
https://issues.apache.org/jira/browse/PHOENIX-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226350#comment-16226350
]
Samarth Jain commented on PHOENIX-4334:
---------------------------------------
[~jamestaylor] - any other ideas on how we can prevent update stats on view2 to
not block itself from running when update stats on view1 has already run? We
could possibly store last_update_stats_time at the logical table level too. But
that would be a non-trivial change.
> 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)
