[
https://issues.apache.org/jira/browse/PHOENIX-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059039#comment-14059039
]
James Taylor commented on PHOENIX-1072:
---------------------------------------
One question on this, though: if the client can't reach the master, does the
error message still show up (as it appears you're just killing the client)?
It'd be nice if hbase had the ability to specify retry info when making a
connection, as a parameter rather than just globally through the Config. If you
agree, maybe you could file a JIRA?
> Fast fail sqlline.py when pass wrong quorum string or hbase cluster hasnt'
> started yet
> ---------------------------------------------------------------------------------------
>
> Key: PHOENIX-1072
> URL: https://issues.apache.org/jira/browse/PHOENIX-1072
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Jeffrey Zhong
> Assignee: Jeffrey Zhong
> Fix For: 5.0.0, 3.1, 4.1
>
> Attachments: phoenix-1072-v1.patch, phoenix-1072.patch
>
>
> Currently sqlline.py will retry 35 times to talk to HBase master when the
> passed in quorum string is wrong or the underlying HBase isn't running.
> In that situation, Sqlline will stuck there forever. The JIRA is aiming to
> fast fail sqlline.py.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
