[
https://issues.apache.org/jira/browse/PHOENIX-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain updated PHOENIX-1261:
----------------------------------
Attachment: 1261-wip.patch
Untested patch with existing tests passing. Need to do some manual tests around:
1) Making sure that only one stats collection is running on a region. This
would also take care of cases when a region corresponds to more than one
phoenix entity - for example UPDATE STATS on a view.
2) Stats collection running on a region via major compaction should prevent an
UPDATE STATISTICS command to run. Also, existing UPDATE STATISTICS command
running on a region should stop gracefully when major compaction is being
triggered for a region.
> Update stats table asynchronously
> ---------------------------------
>
> Key: PHOENIX-1261
> URL: https://issues.apache.org/jira/browse/PHOENIX-1261
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Samarth Jain
> Fix For: 4.7.0
>
> Attachments: 1261-wip.patch
>
>
> Instead of writing the the stats table directly in the thread performing
> major compaction, we should instead write to it asynchronously, perhaps using
> the same asynchronous mechanism used by tracing. Apparently HBase used to
> have a "custodian" table where they'd write as compaction and other
> background tasks were running, and this leads to bad things happening if the
> table being written to can't be reached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
