GitHub user lvdongr opened a pull request:

    https://github.com/apache/spark/pull/16879

    [SPARK-19541][SQL] High Availability support for ThriftServer

    JIRA Issue:  https://issues.apache.org/jira/browse/SPARK-19541
    
    ## What changes were proposed in this pull request?
    
    Currently, We use the spark ThriftServer frequently, and there are many 
connects between the client and only ThriftServer.When the ThriftServer is down 
,we cannot get the service again.So we need to consider the ThriftServer HA as 
well as master HA. 
    For ThriftServer, we want to import the pattern of HiveServer HA to provide 
ThriftServer HA. Therefore, we need to start multiple thrift server which 
register on the zookeeper. Then the client  can find the thrift server by just 
connecting to the zookeeper.So the beeline can get the service from other 
thrift server when one is down.
    
    ## How was this patch tested?
    
    manual tests
    
    
    


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

    $ git pull https://github.com/lvdongr/spark spark-issue

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

    https://github.com/apache/spark/pull/16879.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 #16879
    
----
commit cf4b67f20922c3df494ad68db75c4ace18494116
Author: lvdongr <lv.dongd...@zte.com.cn>
Date:   2017-02-10T01:46:51Z

    [SPARK-19541] - High Availability support for ThriftServer

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to