You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2023/02/06 19:05:00 UTC

[jira] [Updated] (PHOENIX-6052) Include syscat time in mutation time

     [ https://issues.apache.org/jira/browse/PHOENIX-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Viraj Jasani updated PHOENIX-6052:
----------------------------------
    Summary: Include syscat time in mutation time  (was: GLOBAL_MUTATION_COMMIT_TIME metric doesn't include the time spent in syscat rpc's)

> Include syscat time in mutation time
> ------------------------------------
>
>                 Key: PHOENIX-6052
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6052
>             Project: Phoenix
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 4.14.3
>            Reporter: Rushabh Shah
>            Assignee: Aman Poonia
>            Priority: Major
>
> Currently we measure the metric GLOBAL_MUTATION_COMMIT_TIME as the time spent just in htable.batch rpc for base and index tables. https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/execute/MutationState.java#L1029-L1136
> We don't measure the time spent in MutationState#validateAndGetServerTimestamp which makes rpc to SYSTEM.CATALOG table and which is a part of commit phase.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)