[ https://issues.apache.org/jira/browse/PHOENIX-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647000#comment-17647000 ]
ASF GitHub Bot commented on PHOENIX-6655: ----------------------------------------- gourabtaparia commented on code in PR #1534: URL: https://github.com/apache/phoenix/pull/1534#discussion_r1048174396 ########## phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java: ########## @@ -3540,11 +3540,18 @@ Collections.<Class<? extends Exception>> singletonList( if (!ConnectionQueryServicesImpl.this.upgradeRequired.get()) { if (!isDoNotUpgradePropSet) { createOtherSystemTables(metaConnection); + + // When creating the tables above, DDL statements are + // used. However, the CFD level properties are not set + // via DDL commands, hence we are explicitly setting + // few properties using the Admin API below. + updateSystemSequenceWithCacheOnWriteProps(metaConnection); Review Comment: @stoty Can you eyeball it ? > 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 > Assignee: Gourab Taparia > Priority: Major > Attachments: Screenshot 2022-11-25 at 4.38.38 PM.png > > > 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)