[
https://issues.apache.org/jira/browse/PHOENIX-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated PHOENIX-938:
--------------------------------
Attachment: phoenix-938-master-v0.patch
Initial patch to support custom queue usage on both the client and server for
phoenix mutable indexes. This patch has to be used in conjunction with
HBASE-11048 to support client-side write priority.
The code to support server-side is already there, you just need to specify it
in the conf by:
{code}
<property>
<name>hbase.region.server.rpc.scheduler.factory.class</name
<value>
org.apache.hadoop.hbase.regionserver.PhoenixIndexRpcSchedulerFactory</value>
</property>
{code}
> 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
> Attachments: phoenix-938-master-v0.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)
