[ https://issues.apache.org/jira/browse/PHOENIX-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058288#comment-14058288 ]
Andrew Purtell commented on PHOENIX-938: ---------------------------------------- bq. Unfortunately, requires release of 0.98.4 to use the RpcExecutor that comes in 0.98.4 (to compile) There is only HBASE-11118 as blocker for the 0.98.4 release, I'm going to try to resolve it in time to roll a release candidate next Monday, 7/14. > 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, phoenix-938-master-v2.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)