phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Soldatov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3974) Create index may issue a distributed dead lock due lack of handlers
Date Thu, 22 Jun 2017 22:16:00 GMT

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

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

[~samarthjain] 1.3.1, but this behavior is the same for 1.1.x.
[~lhofhansl] Yes, only index updates. Anything else that we should be aware in UngroupedAggregateRegionObserver?
 

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

Mime
View raw message