[
https://issues.apache.org/jira/browse/TAJO-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096490#comment-14096490
]
ASF GitHub Bot commented on TAJO-704:
-------------------------------------
Github user jihoonson commented on a diff in the pull request:
https://github.com/apache/tajo/pull/77#discussion_r16219222
--- Diff:
tajo-core/src/main/java/org/apache/tajo/webapp/QueryExecutorServlet.java ---
@@ -271,6 +272,17 @@ public void setStop() {
public void run() {
startTime = System.currentTimeMillis();
try {
+ // In TajoMaster HA mode, if this servlet can't connect existing
active master,
+ // this should try to connect new active master.
+ TajoConf conf = tajoClient.getConf();
--- End diff --
This is also same with TajoAdmin.checkMasterStatus(). If you move
checkMasterStatus() to any other util classes, please update this code, too.
> 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)
