Yeah, was testing on my own, pre-release 0.98 version :) I *think* it would just be a compile time dependency, but I don't think it would be a runtime dependency - the class won't be loaded if its not specified, letting you get away with not having to run the 0.98.3 bits. Buuuut we should check that.
On Fri, May 23, 2014 at 10:57 PM, James Taylor (JIRA) <j...@apache.org>wrote: > > [ > https://issues.apache.org/jira/browse/PHOENIX-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008054#comment-14008054] > > James Taylor commented on PHOENIX-938: > -------------------------------------- > > I'm getting compiler errors with our current pom. Does this require the > pom to be updated to 0.98.3, and if so, does it introduce a runtime > dependency too, [~jesse_yates]? > > > 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-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) >
