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

ASF GitHub Bot commented on PHOENIX-4892:
-----------------------------------------

GitHub user MrSandmanRUS opened a pull request:

    https://github.com/apache/phoenix/pull/343

    PHOENIX-4892 Unable to start load balancer with queryserver

    Added phoenix_loadbalancer_jar path to phoenix_utils.py,
    added phoenix_loadbalancer_jar to classpath in queryserver.py,
    added service for registry in meta-inf

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/MrSandmanRUS/phoenix PHOENIX-4892

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/phoenix/pull/343.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #343
    
----
commit b906e545eeaf6787192f5952a19506d379361c40
Author: Vitaliy <vit34-95@...>
Date:   2018-09-06T21:20:12Z

    PHOENIX-4892 Unable to start load balancer with queryserver
    Added phoenix_loadbalancer_jar path to phoenix_utils.py,
    added phoenix_loadbalancer_jar to classpath in queryserver.py,
    added service for registry in meta-inf

----


> Unable to start load balancer with queryserver
> ----------------------------------------------
>
>                 Key: PHOENIX-4892
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4892
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.12.0, 4.13.0, 4.13.1, 5.0.0
>            Reporter: Vitaliy
>            Assignee: Vitaliy
>            Priority: Minor
>
> Load balancer can not be started with queryserver, because:
>  # Do not specified the path to the load balancer.jar in phoenix_utils.py and 
> queryserver.py.
>  # Do not specified service for Registry (for ServiceLoader).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to