[
https://issues.apache.org/jira/browse/PHOENIX-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346014#comment-14346014
]
James Taylor commented on PHOENIX-1694:
---------------------------------------
I suppose it depends on the client workload. If the UPDATE STATISTICS command
is only queued on the client, and the client disconnects, the work would be
canceled. If the command has started on the server, then it should just keep
chugging along until finished (regardless of what the client does, as the
updates to the STATS table occur within the coprocessor). Does this match what
you observe? Also, note that upon completion on the server, the
phoenix.stats.updateFrequency time would need to expire before the server (and
subsequently, the client) sees the stats. I believe you could short-circuit
this wait time by running another UPDATE STATISTICS command (once the STATS
table is populated).
We should support the ASYNC keyword perhaps for UPDATE STATISTICS.
> Update statistics fail to complete when client disconnects
> ----------------------------------------------------------
>
> Key: PHOENIX-1694
> URL: https://issues.apache.org/jira/browse/PHOENIX-1694
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.3
> Environment: HBase 0.98.10, Phoenix 4.3 branch
> Reporter: Mujtaba Chohan
> Assignee: James Taylor
> Priority: Minor
>
> [~jamestaylor] You mentioned that after initiating _update statistics_
> command even if client disconnects, statistics would still get generated by
> server side process.
> Just checked it this. As soon as client disconnects stats table population
> halts if client disconnects any time after update statistics command is
> issued.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
