[
https://issues.apache.org/jira/browse/TAJO-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064521#comment-14064521
]
Tajo QA commented on TAJO-704:
------------------------------
{color:red}*-1 overall.*{color} Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12638124/TAJO-704.Henrick.01.patch.txt
against master revision 1867c53.
{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/467//console
This message is automatically generated.
> 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)
