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

["Jaehwa Jung (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAJO-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jaehwa Jung updated TAJO-611:
-----------------------------

    Attachment: TAJO-611_2.patch

Hi [~mafish]

Fist of all, I'd like to ask your understanding regarding my work. I updated your patch because you look really busy.

I updated the patch as follows:
- Unified all discovery functions to one class.
- Apply ProtocolBuffer instead of POJO.
- Adding more unit test cases

For reference, this patch just implements basic functions for a Service Discovery. We need to create more sub-tasks for this service to apply a product.

Cheers
Jaehwa

> (Umbrella) Service Discovery 
> -----------------------------
>
>                 Key: TAJO-611
>                 URL: https://issues.apache.org/jira/browse/TAJO-611
>             Project: Tajo
>          Issue Type: New Feature
>    Affects Versions: 0.9.0
>            Reporter: Min Zhou
>            Assignee: Mafish
>             Fix For: 0.9.0
>
>         Attachments: TAJO-611.patch, TAJO-611_2.patch, tajo-611-servicediscovery-20140420.patch
>
>
> As we talked offline, high availability is one of our next goal.  Service discovery can help us maintain health statuses for all daemons ( master and workers) . Meanwhile, those daemons can find each other easily. Furthermore, 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.2#6252)