[
https://issues.apache.org/jira/browse/PHOENIX-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16399778#comment-16399778
]
Jepson commented on PHOENIX-4649:
---------------------------------
*hdfs-site.xml:*
{code:java}
<property><name>dfs.client.socket-timeout</name><value>1800000</value></property>
<property><name>dfs.socket.timeout</name><value>1800000</value></property>
<property><name>dfs.datanode.socket.write.timeout</name><value>1800000</value></property>
{code}
Try it.
> Phoenix Upsert..Select query is not working for long running query.But while
> we ran same query with limit clause then it works fine
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-4649
> URL: https://issues.apache.org/jira/browse/PHOENIX-4649
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.11.0
> Reporter: Nitin D Chunke
> Priority: Major
> Labels: patch
> Fix For: 5.0.0-alpha
>
> Attachments: image-2018-03-11-00-16-14-968.png,
> image-2018-03-11-00-22-32-613.png
>
>
> We have data in table A which is around 3 Million Records. and from this
> table we have upsert data in to table B with out limit clause.
> (Note : Here we already export the hbase conf path and set all phoenix
> properties to mentioned value and both the tables are salted)
> Please find following hbase-site.xml screen shot.
> !image-2018-03-11-00-22-32-613.png!
> But hbase conf was not picked up when we launch sqlline/psql.
> Please refer following screenshot
> !image-2018-03-11-00-16-14-968.png!
> And when we ran same query with setting limit clause which is higher than
> total number record present in table A,it runs absolutely fine with out
> giving any error.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
