phoenix-dev mailing list archives

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


James Taylor commented on PHOENIX-938:

[~jesse_yates] - looks like 0.98.3 is out. I'd appreciate if you could bump up the pom to
this version, commit this patch, and work with [~mujtaba] to ensure that we'll still run against
0.98.1 with this fix.

> Use higher priority queue for index updates to prevent deadlock
> ---------------------------------------------------------------
>                 Key: PHOENIX-938
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message