[
https://issues.apache.org/jira/browse/PHOENIX-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103003#comment-15103003
]
Hudson commented on PHOENIX-1261:
---------------------------------
FAILURE: Integrated in Phoenix-master #1082 (See
[https://builds.apache.org/job/Phoenix-master/1082/])
PHOENIX-1261 Addendum to fix test failures (samarth: rev
c2ee4f7fd7dc80b511ba23e0431a3b8ffeae26a3)
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/BaseScannerRegionObserver.java
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java
> 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_addendum2.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)
