[
https://issues.apache.org/jira/browse/APEXCORE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147741#comment-16147741
]
Sanjay M Pujare commented on APEXCORE-781:
------------------------------------------
I think the problem could be reporting of partial metrics: some partitions of
an operator can be delayed and reporting their metrics late for a certain
window boundary. However when a user queries auto-metrics using something like
http://host:port/ws/v2/applications/<appid>/logicalPlan/operators/QueryResult
the app-master just gets the current latest metrics for the operator without
waiting for all partitions to report. What the app-master should do is to
report the latest complete metric. There are cases where users expect their
auto-metrics (such as counts/aggregates) to be monotonically increasing.
> Autometric values of an operator is showing wrongly in App master
> ------------------------------------------------------------------
>
> Key: APEXCORE-781
> URL: https://issues.apache.org/jira/browse/APEXCORE-781
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Chaitanya
>
> Observation:
> - This was happening only if the operator has more than one partition.
> - In StreamingContainerManager, sometimes the size of collection of metric
> values and # of physical partitions of an operator is not matching. Due to
> this reason, the auto-metrics value is showing wrongly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
