[
https://issues.apache.org/jira/browse/PHOENIX-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049696#comment-15049696
]
Samarth Jain commented on PHOENIX-2408:
---------------------------------------
Thanks for verifying [~mujtabachohan].
I also did a test in which I ended up killing the client while UPDATE STATS was
in progress. The scanners on the server side fail with the same exception as
above because the client got disconnected. So ideally, such long running
operations, should be executed via some other asynchronous mechanism
(map-reduce?/message queue?) to make sure the operation completes even though
the requesting client dies.
> Update statistics fails to complete
> -----------------------------------
>
> Key: PHOENIX-2408
> URL: https://issues.apache.org/jira/browse/PHOENIX-2408
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Samarth Jain
> Fix For: 4.7.0
>
>
> On a production cluster, when UPDATE STATISTICS is run, it fails to complete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
