You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Sergey Soldatov (JIRA)" <ji...@apache.org> on 2017/06/22 18:01:00 UTC

[jira] [Commented] (PHOENIX-3974) Create index may issue a distributed dead lock due lack of handlers

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

Sergey Soldatov commented on PHOENIX-3974:
------------------------------------------

There is a small note. The documentation still says to configure the controller in hbase-site.xml (which leads that all client side communication can go through Index rpc and may cause problems with lack of Index handlers and following dead lock).  

> Create index may issue a distributed dead lock due lack of handlers
> -------------------------------------------------------------------
>
>                 Key: PHOENIX-3974
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3974
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.11.0
>            Reporter: Sergey Soldatov
>            Assignee: Sergey Soldatov
>         Attachments: PHOENIX-3974.patch
>
>
> In PHOENIX-3360 we were trying to avoid using index rpc on client side, setting controller manually in Indexer.  But after we moved index creating to server side there is another set of RS-RS communication that comes from UngroupedAggregateRegionObserver with regular priority. That may cause distributed dead lock when all handlers are occupied by index create scanners for user table and inside they are trying to send index updates. To prevent it we need to set controller in UngroupedAggregateRegionObserver in the similar way like we did in Indexer. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)