[
https://issues.apache.org/jira/browse/PHOENIX-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057198#comment-15057198
]
James Taylor commented on PHOENIX-1261:
---------------------------------------
One other functional item that'd be nice to add - expose the <fullTableName>
plus start/stop key of the running jobs and reject any attempt to add another
job that overlaps. We do have a client-side check that prevents an UPDATE
STATISTICS before a certain configurable time period has elapsed, but this
would be a backup mechanism to prevent overlapping stats jobs.
Somewhat related would be if a major compaction starts - might want to just
dump the update stats job into the same thread pool as that'd make sure that
two overlapping stats jobs aren't started.
> 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)
