phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-938) Use higher priority queue for index updates to prevent deadlock
Date Sun, 08 Jun 2014 18:44:02 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Taylor updated PHOENIX-938:
---------------------------------

    Fix Version/s: 4.1
                   5.0.0

> Use higher priority queue for index updates to prevent deadlock
> ---------------------------------------------------------------
>
>                 Key: PHOENIX-938
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-938
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.0.0, 4.1
>            Reporter: James Taylor
>            Assignee: Jesse Yates
>             Fix For: 5.0.0, 4.1
>
>         Attachments: phoenix-938-4.0-v0.patch, phoenix-938-master-v0.patch, phoenix-938-master-v1.patch
>
>
> With our current global secondary indexing solution, a batched Put of table data causes
a RS to do a batch Put to other RSs. This has the potential to lead to a deadlock if all RS
are overloaded and unable to process the pending batched Put. To prevent this, we should use
a higher priority queue to submit these Puts so that they're always processed before other
Puts. This will prevent the potential for a deadlock under high load. Note that this will
likely require some HBase 0.98 code changes and would not be feasible to implement for HBase
0.94.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message