You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tajo.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/08/04 12:23:12 UTC

[jira] [Commented] (TAJO-704) TajoMaster HA

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

ASF GitHub Bot commented on TAJO-704:
-------------------------------------

Github user blrunner commented on the pull request:

    https://github.com/apache/tajo/pull/77#issuecomment-51043233
  
    Hi @jihoonson 
    
    I added a document for TajoMaster HA.
    And I'll implement shell script to launch masters after committing https://issues.apache.org/jira/browse/TAJO-990.


> 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)