[
https://issues.apache.org/jira/browse/PHOENIX-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047865#comment-15047865
]
Samarth Jain commented on PHOENIX-2408:
---------------------------------------
The timeout needs to be set at the HConnection level. Talked to [~jamestaylor]
offline and he suggested (and I verified) that we can accomplish this by using
a URL like
{code}
jdbc:phoenix:localhost:long-running:2181
{code}
which would force the PhoenixDriver to establish a new HConnection to the
cluster. Then overriding the rpc timeout like below will end up giving us a
connection that we can run long running operations like UPDATE STATS on.
{code}
Properties props = new Properties();
String customUrl = "jdbc:phoenix:localhost:long-running:2181";
props.put(HConstants.HBASE_RPC_TIMEOUT_KEY, Integer.toString(600000));
Connection conn = DriverManager.getConnection(customUrl, props);
conn.createStatement().executeQuery("UPDATE STATISTICS TABLENAME");
{code}
> 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)
