Details
Description
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.
Attachments
Attachments
Issue Links
- links to