[
https://issues.apache.org/jira/browse/PHOENIX-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081268#comment-16081268
]
Vincent Poon commented on PHOENIX-3948:
---------------------------------------
[~gjacoby] Yea an operator would need to add this new config. I originally put
a new default , but wasn't sure if that was right, as some people may have
tweaked their hbase.client.retries.number, or the real culprit,
hbase.client.serverside.retries.multiplier , which takes the first number and
multiplies it by 10. In HBase Master there is even a note
"// TODO: Fix this. Not all connections from server side should have 10 times
the retries."
So presumably if they fixed that up there, then that would get inherited in the
Indexer. But otherwise, folks will need to add this property override.
> Enable shorter time outs for server-side index writes
> -----------------------------------------------------
>
> Key: PHOENIX-3948
> URL: https://issues.apache.org/jira/browse/PHOENIX-3948
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Vincent Poon
> Labels: globalMutableSecondaryIndex
> Attachments: PHOENIX-3948.master.v1.patch
>
>
> The default timeouts are far too high for a RS->RS global index update as
> we're holding on to a handler thread when the retries occur. We should be
> able to set them to be inline with the client-side timeouts.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
