You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Mai Hai Thanh (JIRA)" <ji...@apache.org> on 2014/09/24 10:59:33 UTC
[jira] [Commented] (TAJO-1069) Add document to explain High
Availability support
[ https://issues.apache.org/jira/browse/TAJO-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146093#comment-14146093 ]
Mai Hai Thanh commented on TAJO-1069:
-------------------------------------
[~blrunner], I see a recent svn commit that adds a great document for TajoMaster HA by you. I will be nice if you will also write another one for TajoWorker. Until now, in the documentation, it is not clear what will happen if a TajoWorker crashes or fails, especially when that worker is participating in the processing of a query.
> Add document to explain High Availability support
> -------------------------------------------------
>
> Key: TAJO-1069
> URL: https://issues.apache.org/jira/browse/TAJO-1069
> Project: Tajo
> Issue Type: Sub-task
> Components: documentation
> Affects Versions: 0.9.0
> Reporter: Mai Hai Thanh
> Fix For: 0.9.0
>
>
> High Availability (HA) support is important for large-scale and distributed systems like Tajo. As I know, Tajo at least supports HA for TajoMaster (TAJO-704). However, it is not clear how HA is supported for other components and how Tajo reacts in different situations. In the documentation, we should talk about it. For example, we can provide the answers for the following (or more) questions.
> + What happen if TajoMaster crashes ? for both cases,
> - When there is no query running.
> - When there is one (or more) query running
>
> + What happen if a TajoWorker crashes ? for both cases,
> - When there is no query running.
> - When there is one (or more) query running
> For the above questions, the case when there is a running query is very important because we say "... Tajo is designed for both interactive and *batch* queries ... Tajo provides fault-tolerance ... for *long-running queries* ...".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)