[
https://issues.apache.org/jira/browse/PHOENIX-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102446#comment-15102446
]
Mujtaba Chohan commented on PHOENIX-1261:
-----------------------------------------
[~samarthjain] Using latest
[commit|https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=ad91debaaac29aa6c52cea7c678c5f9c406bd99c].
If I kill my client during _update statistics <table>_, stats are not updated
and on RS I get:
{code}
ERROR [4,queue=4,port=60020] coprocessor.UngroupedAggregateRegionObserver -
IOException in update stats:
org.apache.hadoop.hbase.ipc.CallerDisconnectedException: Aborting on region
<table>, call org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl
after 25938 ms, since caller disconnected
at
org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:4188)
{code}
> 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_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)
