You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Min Zhou (JIRA)" <ji...@apache.org> on 2014/02/20 04:35:21 UTC

[jira] [Created] (TAJO-611) (Umbrella) Service Discovery

Min Zhou created TAJO-611:
-----------------------------

             Summary: (Umbrella) Service Discovery 
                 Key: TAJO-611
                 URL: https://issues.apache.org/jira/browse/TAJO-611
             Project: Tajo
          Issue Type: New Feature
    Affects Versions: 1.0-incubating
            Reporter: Min Zhou


As we talked offline, high availability is one of our next goal.  I'd like to add a new feature, service discovery,  to Tajo. Service discovery can help us maintain health statuses for all daemons ( master and workers) . Meanwhile, those daemons can find each other easily. Meanwhile, it's very useful for my current work TAJO-540 cuz it can randomly select nodes for tajo scheduler.  

One of the best candidates is Netflix Curator.  http://curator.apache.org/curator-x-discovery/index.html

I'd like to introduce Xuhui to help us with this issue.  Xuhui was my colleague at Alibaba group. He was active in Hive community, one of his job is adding multi-distinct aggregation feature to Hive. Currently, he is a researcher work at Microsoft.

[~mafish]

Below is comment on this issue from Xuhui

To my understanding, this feature is for high availability as well as high scalability. We don't need to provide all machine info for every service when tajo starts. Instead, we can dynamically register services to service discovery if necessary. Also, if some machine fails, it can be easily detected and replaced.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)