[
https://issues.apache.org/jira/browse/HBASE-24499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124640#comment-17124640
]
Viraj Jasani commented on HBASE-24499:
--------------------------------------
[~rvaleti] ACK. Agree, this should be configurable.
> Use a client property for SaslConnection MAX_ATTEMPTS (currently hardcoded to
> 5)
> --------------------------------------------------------------------------------
>
> Key: HBASE-24499
> URL: https://issues.apache.org/jira/browse/HBASE-24499
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 1.3.2
> Reporter: Ravi Kishore Valeti
> Assignee: Ravi Kishore Valeti
> Priority: Minor
> Fix For: 2.3.0, master, 1.7.0
>
>
> The no.of retries for Sasl handshake is hardcoded to 5 (MAX_ATTEMPTS). Use
> cases which have strict SLAs on their operation timeouts need this to be
> configurable to meet their SLAs.
> Sample Scenario:
> * RS is slow in accepting connections but is slow in responding to requests.
> * Client makes a Sasl Connection attempt but times out on read (can be
> configurable via hbase.ipc.client.socket.timeout.read) and retries 5 times at
> this time (this is not configurable) and eventually bails out.
> Make this configurable by a new client property (say
> *hbase.security.relogin.maxretries)* so that clients/usecases can override
> and meet their timeout SLAs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
