[
https://issues.apache.org/jira/browse/TAJO-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100326#comment-14100326
]
ASF GitHub Bot commented on TAJO-704:
-------------------------------------
Github user blrunner commented on the pull request:
https://github.com/apache/tajo/pull/77#issuecomment-52456134
Hi @jihoonson.
I updated the patch with your ideas. For reference, I implemented another
utility class for client. Because I couldn't implement in tajo common module by
dependency issue.
I found some client side bugs when I had tested the patch on testing
cluster (consists of 10 nodes). So, I fixed it and committed it to my private
branch.
If you can review it again, I will be really glad for you. :)
> TajoMaster HA
> -------------
>
> Key: TAJO-704
> URL: https://issues.apache.org/jira/browse/TAJO-704
> Project: Tajo
> Issue Type: New Feature
> Components: tajo master
> Affects Versions: 0.9.0
> Reporter: Jaehwa Jung
> Assignee: Jaehwa Jung
> Fix For: 0.9.0
>
> Attachments: TAJO-704.Henrick.01.patch.txt, TajoMasterHAdraft.pdf
>
>
> TajoMaster is a Single Point of Failure in a Tajo Cluster because TajoMaster
> is the central controlling entity for all components of the Tajo system.
> TajoMaster failure prevents clients from submitting new queries to the
> cluster, and results in the disruption of the ability to run insert overwrite
> queries because the TajoWorker can’t apply its statistical information to
> CatalogStore. Therefore, the high-availability (HA) of TajoMaster is
> essential for the high-availability of Tajo generally.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
