Details
-
New Feature
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
0.9.0
-
None
-
None
-
None
Description
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.
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.
Attachments
Attachments
Issue Links
- relates to
-
-
- Resolved
-