phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mujtaba Chohan (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 18:01:12 GMT

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

Mujtaba Chohan commented on PHOENIX-4334:
-----------------------------------------

So shouldn't we just disallow collection of stats at tenant/view level since this will mean
that stats for all other views are invalid apart from the one that originated the stats collection
call as they will report inaccurate byte/row count while stats update timestamp for all views
will report last updated time being current.

FYI [~cody.marcel@gmail.com]

> 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