[
https://issues.apache.org/jira/browse/PHOENIX-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081236#comment-16081236
]
Geoffrey Jacoby commented on PHOENIX-3948:
------------------------------------------
Patch generally looks good, [~vincentpoon], but I'm a little concerned about
the default logic. If we're defaulting to the HBase default retries, which we
know are problematic for index updates, does that mean that only operators who
know about this new config knob will get a benefit from this change?
Also note that the JIRA refers to timeouts but the patch is to retries. If we
go with this approach it's probably a good idea to tweak the JIRA name.
> 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)
