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

Tajo QA commented on TAJO-611:
------------------------------

{color:red}*-1 overall.*{color}  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12652538/TAJO-611_2.patch
  against master revision 7510f88.

      {color:red}-1 patch.{color}  The patch command could not apply the patch.

    {color:red}-1 patch.{color}  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/503//console

This message is automatically generated.

> (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
>         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.3.4#6332)

Reply via email to