phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3948) Enable shorter time outs for server-side index writes
Date Mon, 10 Jul 2017 23:38:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081359#comment-16081359
] 

Andrew Purtell commented on PHOENIX-3948:
-----------------------------------------

Be careful not to set these too low or we'll put an index into a failed state even though
it would otherwise ride over the issue. Consider settings that add up to 60 seconds at least.
120 would be better. This would cover transient network issues and knock-on effects like stalled
flushes, closes, and the like. 

> 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)

Mime
View raw message