You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Samarth Jain (JIRA)" <ji...@apache.org> on 2016/01/16 01:13:39 UTC

[jira] [Updated] (PHOENIX-1261) Update stats table asynchronously

     [ https://issues.apache.org/jira/browse/PHOENIX-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Samarth Jain updated PHOENIX-1261:
----------------------------------
    Attachment: PHOENIX-1261_addendum.patch

Looks like I ended up missing the async attribute on the scan. 

[~jamestaylor], please review. 

[~mujtabachohan] - let us know if the UPDATE STATS call finished successfully with the patch that I provided.

> 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, PHOENIX-1261_1.0.patch, PHOENIX-1261_98_v2.patch, PHOENIX-1261_addendum.patch, PHOENIX-1261_master.patch, PHOENIX-1261_master_v2.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)