[
https://issues.apache.org/jira/browse/PHOENIX-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509345#comment-17509345
]
ASF GitHub Bot commented on PHOENIX-6671:
-----------------------------------------
lhofhansl edited a comment on pull request #1405:
URL: https://github.com/apache/phoenix/pull/1405#issuecomment-1073067481
Seems that I cannot look at the output of the test run...?
Update: I can now. Time out in BasePermissionsIT:812 (Where it creates an
index), so it might be related.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> Avoid ShortCirtuation Coprocessor Connection with HBase 2.x
> -----------------------------------------------------------
>
> Key: PHOENIX-6671
> URL: https://issues.apache.org/jira/browse/PHOENIX-6671
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Major
> Fix For: 5.2.0, 5.1.3
>
> Attachments: 6671-5.1.txt
>
>
> See PHOENIX-6501, PHOENIX-6458, and HBASE-26812.
> HBase's ShortCircuit Connection are fundamentally broken in HBase 2. We might
> be able to fix it there, but with all the work the RPC handlers perform now
> (closing scanning, resolving current user, etc), I doubt we'll get that 100%
> right. HBase 3 has removed this functionality.
> Even with HBase 2, which does not have the async protobuf code, I could
> hardly see any performance improvement from circumventing the RPC stack in
> case the target of a Get or Scan is local. Even in the most ideal conditions
> where everything is local, there was improvement outside of noise.
> I suggest we do not use ShortCircuited Connections in Phoenix 5+.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
