ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yury Gerzhedovich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10754) Query history statistics API
Date Fri, 18 Jan 2019 14:57:00 GMT

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

Yury Gerzhedovich commented on IGNITE-10754:
--------------------------------------------

[~vozerov], all mentioned issues have been fixed.

> Query history statistics API
> ----------------------------
>
>                 Key: IGNITE-10754
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10754
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>            Reporter: Yury Gerzhedovich
>            Assignee: Yury Gerzhedovich
>            Priority: Major
>              Labels: iep-29, monitoring
>             Fix For: 2.8
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> As of now we have query statistics (*_org.apache.ignite.IgniteCache#queryMetrics_*) ,
but have few issues.
>  1) Duration execution it just time between start execution and return cursor to client
and doesn't include all life time of query.
>  2) It doesn't know about multistatement queries. Such queries participate in statistics
as single query without splitting.
>  3) API to access the statistics expose as depend on cache, however query don't have
such dependency.
>   
>  Need to create parallel similar realization as we already have.
>  Use new infrastructure of tracking running queries developed under IGNITE-10621 and
update statistics on unregister phase.
>  Expose API on upper level then it placed now. Right place will be written later.
>   
>   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message