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

Josh Elser commented on PHOENIX-5826:
-------------------------------------

I'm not aware of anyone who is actually using this load balancer. [~gjacoby], 
[~swaroopa], do y'all know if SFDC is using this load balancer? If so, maybe we 
could ask them to test out whatever István puts together.

I'm going off of memory, but I think this was only embedding host:port into 
ZooKeeper and then clients were expected to write their own logic to pull it 
from there and convert it to a URL. If that's the case, we should be able to 
serialize our own host:port into ZK by hand (like you say). I think the risk is 
low to just make the change.

> Remove guava from queryserver
> -----------------------------
>
>                 Key: PHOENIX-5826
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5826
>             Project: Phoenix
>          Issue Type: Improvement
>          Components: queryserver
>    Affects Versions: queryserver-1.0.0
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Major
>
> The queryserver repo has to work with multiple phoenix branches.
> HBase and Hadoop master has already migrated to guava27/28.
> Queryserver has to work both with the 4.x branch, which will probably have to 
> stay on the old guava version, and master, which will have to be upgraded to 
> 28.
> The queryserver codebase does not work with Guava 28.
> The simplest way to solve this problem is to remove guava from the 
> queryserver modules.
> Most of the guava uses are trivial to replace -, but unfortunately changing 
> the host information that load-balancer stores in zookeeper is a non backward 
> compatible change- . The HostAndPort object would have to be replaced by 
> something like InetSocketAddress .
> Since we are before the first release of the unbundled queryserver, I think 
> that this a great time to get this done with minimal disruption to the users.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to