phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4334) Unable to update stats on views that reside on separate regions before phoenix.stats.updateFrequency has elapsed
Date Wed, 01 Nov 2017 20:06:00 GMT

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

James Taylor commented on PHOENIX-4334:
---------------------------------------

I thought the last updated time was based on the guideposts, not the global setting in the
physical table? Do we have a test case for this (or can we outline one)? Is the info in the
explain plan wrong?

> 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
>            Priority: Major
>
> 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)

Mime
View raw message