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

Posted to issues@phoenix.apache.org by "Gourab (Jira)" <ji...@apache.org> on 2022/11/02 09:27:00 UTC

[jira] [Commented] (PHOENIX-6655) SYSTEM.SEQUENCE should have CACHE_DATA_ON_WRITE set to true

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

Gourab commented on PHOENIX-6655:
---------------------------------

[~tkhurana] [~kadir] Can you please assign this Jira to me ?

> SYSTEM.SEQUENCE should have CACHE_DATA_ON_WRITE set to true
> -----------------------------------------------------------
>
>                 Key: PHOENIX-6655
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6655
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Geoffrey Jacoby
>            Priority: Major
>
> High volume use cases of Phoenix sequences need to write to the same row of SYSTEM.SEQUENCE very frequently, but each time we write, the block cache that row is in is invalidated and has to be loaded again. 
> [~rushabh.shah] was looking at a case in our environment where a sequence was being used heavily and found lots of time spent reading the HFiles for the same Get of the sequence row within the SequenceRegionObserver increment coproc. 
> [~apurtell] pointed out offline that HColumnDescriptor has a property, CACHE_DATA_ON_WRITE that keeps caches updated when a value is flushed. This should help improve contention on sequence increments. 



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