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

Jesse Yates edited comment on PHOENIX-938 at 7/14/14 7:04 PM:
--------------------------------------------------------------

Well, as its a new addition, support 0.98.4 as the first version doesn't seem 
like that big of an issue - basically, "add these configs and roll your cluster 
with the new hbase + phoenix". 

And it would be nice to drop all the 0.98.3 specific code of out of the patch 
(which creates its own RpcExecutor, reflection, etc). Not worth all the extra 
work to make it work with the inheritance heirarchy



was (Author: jesse_yates):
Well, as its a new addition, support 0.98.4 as the first version doesn't seem 
like that big of an issue - basically, "add these configs and roll your cluster 
with the new hbase + phoenix". 

And it would be nice to drop all the 0.98.3 specific code of out of the patch 
(which creates its own RpcExecutor*, reflection, etc). Not worth all the extra 
work to make it work with the inheritance heirarchy

> 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-master-v3.patch, 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)

Reply via email to